Win2K: Route command

[Chris Swann]

Guys,

I'm trying to get a dial up service sorted on our LAN. I
have a 3com Dual 56k modem attached to the LAN. I think
I've narrowed the problem down to the routing table on the
dialing machine.

The address range of the LAN is 192.168.1.X with a subnet
of 255.255.255.0. The 3com modem is IP 192.168.1.6

I have a remote computer with a modem which I wish to dial
into the network. I cant seem to get the routing right tho
so I've been lookin up the route command on MS's Technet
site - but its not making much sense to me.

I want to add a route on the remote computer to be able to
route to the network 192.168.1.* which has a subnet of
255.255.255.0 through the default gateway, which is the
modem, with an IP of 192.168.1.51.

According to:

http://www.microsoft.com/windowsxp/...oc/en/route.asp

It seems that the command (to create a persistant route)
should be:

route -p add 192.168.1.* MASK 255.255.255.0 192.168.1.51
METRIC 1

I've dialed up and the modem has allowed my username and
password. I've openned a dos shell and added the above
line, and it accepts it.

The think is it still doesnt want to allow me to ping the
rest of the network at all (192.168.1.*)

Can anyone offer any advice?

 

[Gary Fose [MSFT]]

Hi Chris,

All the IP's you mentioned are on the local subnet. So there should not be a need for a route
added to the routing table. But there are some pieces of info missing from your message. Like
what address does the client get when it makes a connection to the LAN? How is the address
assigned? DHCP through RRAS? A static IP range in RRAS?

300434 HOW TO: Allow Remote Users to Access Your Network in Windows 2000
http://kb/article.asp?id=Q300434

This will provide the info you need.

Thanks,
Gary


--------------------
'--'Content-Class: urn:content-classes:message
'--'From: "Chris Swann" <[email protected]>
'--'Sender: "Chris Swann" <[email protected]>
'--'Subject: Win2K: Route command
'--'Date: Wed, 11 Feb 2004 06:58:36 -0800
'--'Lines: 39
'--'Message-ID: <[email protected]>
'--'MIME-Version: 1.0
'--'Content-Type: text/plain;
'--' charset="iso-8859-1"
'--'Content-Transfer-Encoding: 7bit
'--'X-Newsreader: Microsoft CDO for Windows 2000
'--'Thread-Index: AcPwr4aDin7qb5gbSumjprpwHcpChg==
'--'X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
'--'Newsgroups: microsoft.public.win2000.networking
'--'Path: cpmsftngxa07.phx.gbl
'--'Xref: cpmsftngxa07.phx.gbl microsoft.public.win2000.networking:54402
'--'NNTP-Posting-Host: tk2msftngxa12.phx.gbl 10.40.1.164
'--'X-Tomcat-NG: microsoft.public.win2000.networking
'--'
'--'Guys,
'--'
'--'I'm trying to get a dial up service sorted on our LAN. I
'--'have a 3com Dual 56k modem attached to the LAN. I think
'--'I've narrowed the problem down to the routing table on the
'--'dialing machine.
'--'
'--'The address range of the LAN is 192.168.1.X with a subnet
'--'of 255.255.255.0. The 3com modem is IP 192.168.1.6
'--'
'--'I have a remote computer with a modem which I wish to dial
'--'into the network. I cant seem to get the routing right tho
'--'so I've been lookin up the route command on MS's Technet
'--'site - but its not making much sense to me.
'--'
'--'I want to add a route on the remote computer to be able to
'--'route to the network 192.168.1.* which has a subnet of
'--'255.255.255.0 through the default gateway, which is the
'--'modem, with an IP of 192.168.1.51.
'--'
'--'According to:
'--'
'--'http://www.microsoft.com/windowsxp/...oc/en/route.asp
'--'
'--'It seems that the command (to create a persistant route)
'--'should be:
'--'
'--'route -p add 192.168.1.* MASK 255.255.255.0 192.168.1.51
'--'METRIC 1
'--'
'--'I've dialed up and the modem has allowed my username and
'--'password. I've openned a dos shell and added the above
'--'line, and it accepts it.
'--'
'--'The think is it still doesnt want to allow me to ping the
'--'rest of the network at all (192.168.1.*)
'--'
'--'Can anyone offer any advice?
'--'
'--'


--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included
script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best
directed to the newsgroup/thread from which they originated.