Windows Route command
We are trying to use the route command, within a VPN connection, to change the local clients route. Microsoft says to use the command as:
192.168.0.0 mask 255.255.0.0 default METRIC default IF default
with the first default being the gateway to use
the second default being the default metric for that gateway
and the third default being the interface that the gateway you are using is on.
The problem is that whether I type this in manually, or use the client to try to do it, it continually comes back with the message
"bad gateway address default"
Any idea?
Thanks in advance
tayloric
Junior Poster in Training
63 posts since Apr 2004
Reputation Points: 14
Solved Threads: 1
Let me be the first to completely misunderstand this problem
Should the subnet mask not be 255.255.255.0 with the Class C address specified.
CAN YOU NOT JUST USE THE TCP IP PROPERTIES OF YOU CONNECTION TO ADD IP AND SUBNET AND THE IP OF YOUR ROUTER TO DEFAULT GATEWAY
APOLOGIES FOR CAPS _ STICKY KEYS THE GIT
MartyMcFly
Practically a Master Poster
678 posts since Feb 2005
Reputation Points: 16
Solved Threads: 17
We have a subnetted network using the 192.168.x.x address space. We have to use the 255.255.0.0 to be able to access all the various subnets.
I can personally use TCP/IP properties, or Route ADD, etc. to setup my connection, however, our end users are not technical enough to be able to do that. We are trying to automate their connection to the VPN server. We have tried using the CMAK to do this with an included file, and also tried a URL, etc. Our problem continues to be the 'default' wording that Microsoft says to use. All of Microsoft's documentation, as well as documentation on other sites says to use the 'defalut' wording and all that does is generate erros.
thanks
tayloric
Junior Poster in Training
63 posts since Apr 2004
Reputation Points: 14
Solved Threads: 1
as I said, completely misunderstood, and bad advise at that :(
MartyMcFly
Practically a Master Poster
678 posts since Feb 2005
Reputation Points: 16
Solved Threads: 17
Our problem is that Microsoft CMAK does not use the standard route command. When we go into the client and manually configure it, it works great. Our users are just that, users. They wouldn't understand route commands, etc. Trying to use the Micorsoft CMAK, and following all of Microsoft's instructions, is where our problem lies. We have tried and tried to get it to work, but can't get it to work fully. Our initial add command of add 192.168.0.0 mask 255.255.0.0 default works great. It's when we try to add any other routes to it that it crashes. Since our network is subnetted into many subnets we have to have multiple lines to get it all working.
Thanks
tayloric
Junior Poster in Training
63 posts since Apr 2004
Reputation Points: 14
Solved Threads: 1