Re: TCP/IP routing - which is the correct behaviour
From: JF Mezei (jfmezei.spamnot_at_teksavvy.com)
Date: 05/13/04
- Next message: Larry Kilgallen: "Re: LIB$INITIALIZE: simple example?"
- Previous message: Karsten Nyblad: "Re: You'll never guess what HP advertised"
- In reply to: Andrew Rycroft: "TCP/IP routing - which is the correct behaviour"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 13 May 2004 04:13:10 GMT
Andrew Rycroft wrote:
> From my PC I can connect to the internal network address as one would
> expect. I CANNOT connect to the external interface. I believe this
> also to be correct since the static route to the PC subnet is defined
> as being via the internal network interface. Dynamic routing is
> disabled.
If you have the VMS server's intranet at 10.0.0.10 and your PC at 10.0.0.11,
with subnet mask fo 10.*.*.*
Your PC can communicate directly with any 10.*.*.* host since it is assumed to
be on the same (logical) ethernet.
However, to communicate with a host outside the 10.* subnet, the PC must be
given a default route (in PC parlange, "gateway".
You PC should have as a gateway yoru VMS server's internal address of 10.0.0.10
How you set this depends on whether your PC is manually configured, or
configured via DHCP. In the first case, you ise the Windows menus. For DHCP,
you need to update the DHCP server's configuration so that it supplies your PC
with a gateway (default route).
- Next message: Larry Kilgallen: "Re: LIB$INITIALIZE: simple example?"
- Previous message: Karsten Nyblad: "Re: You'll never guess what HP advertised"
- In reply to: Andrew Rycroft: "TCP/IP routing - which is the correct behaviour"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
