VPN + US based MS Exchange server

[hut49]

With VPN connected and DefGW unticked

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

Cocuments and Settings
icky>ipconfig /all

***info removed, so I can sleep at night***

Edited by hut49 on Monday 3rd July 14:15

Edited by hut49 on Monday 3rd July 20:48

[hut49]

With VPN connected and DefGW ticked

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

Cocuments and Settings
icky>ipconfig /all

***info remove to protect the innocent (me)***

Edited by hut49 on Monday 3rd July 20:22

[BliarOut]

Ah, it's back

Reboot PC (to save messing around with route delete commands) then type

route ADD 192.168.0.0 MASK 255.255.0.0 192.168.160.200

before connecting the VPN without the DefGW checkbox ticked... Should work a treat

There appears to be a problem with your route being via 192.168.160.201


If it works, type

route ADD 192.168.0.0 MASK 255.255.0.0 192.168.160.200 -p

to make it permanent.

Edited to add that's if your IP address is 201 and GW is 200!!

Edited by BliarOut on Monday 3rd July 14:37

[hut49]

Bummer, I get the following message:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:Documents and Settings icky>route ADD 192.168.0.0 MASK 255.255.0.0 192.168.1
60.200
The route addition failed: Either the interface index is wrong or the gateway do
es not lie on the same network as the interface. Check the IP Address Table for
the machine.

If you've had enough of this don't hesitate to say so - I really appreciate everything that you and DeeJay have done...

[aldi]

Think you'l need to do that after connecting the VPN - the 192 interfaces does not exist untill then. I'm sure the gruesome twosome will be allong to confirm shortly

[_DeeJay_]

aldi said:

Think you'l need to do that after connecting the VPN - the 192 interfaces does not exist untill then. I'm sure the gruesome twosome will be allong to confirm shortly

correct.

[BliarOut]

But I bet it works when the VPN is established....

This could go one of two ways... One of which is it works, the other is that it doesn't

Bring up the VPN without the DefGW box ticked and then add the route.... It will go in. If all is well we have two choices. It might work if you add it with a -p and remain or it might not. If it doesn't then you can always add a shortcut to the desktop to run it once the VPN is up.

In theory once the VPN is up and you make it permanent it *should* stay.

We're very close now.

[hut49]

Thanks Aldi - I tried that (it made sense to me) but got the same error message - I can't believe how long this innocent little thread has become!

[BliarOut]

hut49 said:

Thanks Aldi - I tried that (it made sense to me) but got the same error message - I can't believe how long this innocent little thread has become!

Try opening the command prompt *after* you've bought up the VPN.

[hut49]

I suppose for IT professionals this is rather like a fiendish level of Su-Doku to us mere mortals!!

[hut49]

BliarOut said:

hut49 said:

Thanks Aldi - I tried that (it made sense to me) but got the same error message - I can't believe how long this innocent little thread has become!

Try opening the command prompt *after* you've bought up the VPN.

Same old..

[BliarOut]

Hmmm, subnet mask...

Did your network guys in the US give you all the settings to enter manually for the VPN?

[hut49]

I recall only entering one IP address during the VPN setup and that was a 216.133.X.X number

[_DeeJay_]

Hey Mr Consultant - seems we're barking up the wrong tree; MS changed the behaviour in XP (www.kbalertz.com/254231/Change.Remote.Access.Route.Behavior.Windows.aspx)

So, we were wrong (sorry!).

The actual rule you want (rather counterintuitively) is:

route add 192.168.0.0 mask 255.255.0.0 <your vpn client address> (I believe).

D


edited to add: So, it would have been (assuming you IP address hasn't changed): route add 192.168.0.0 mask 255.255.0.0 192.168.160.201

Using -p isn't an option because it will change so the process will be: VPN in, check the IP you're given, then run the command above, modifying the IP as appropriate.

Edited by _DeeJay_ on Monday 3rd July 15:23

[BliarOut]

However, we had this here...


192.168.160.0 255.255.255.0 192.168.160.201 192.168.160.201 1
192.168.160.201 255.255.255.255 127.0.0.1 127.0.0.1 50
192.168.160.255 255.255.255.255 192.168.160.201 192.168.160.201 50





One thing, I notice a wired and a wireless connection both appear to be present. Is that correct?

[hut49]

Wireless and wired - yes. It could be one or the other exclusively too, if that would hlep.

I tried the new DeeJay strategy inspired by Mr Gates counter-intuitive behaviour and tried

route add 192.168.0.0 mask 255.255.0.0 <your vpn client address>

where I used the vpn IP (216.133.X.X) that was used to set up the VPN - same result

[BliarOut]

I *think* what's happening is we're configuring one interface and the VPN packets we are trying to route are shooting out the other interface. Is it possible to boot her up with just one connection live so we can get to the bottom of what's occuring.

[_DeeJay_]

hut49 said:

Wireless and wired - yes. It could be one or the other exclusively too, if that would hlep.

I tried the new DeeJay strategy inspired by Mr Gates counter-intuitive behaviour and tried

route add 192.168.0.0 mask 255.255.0.0 <your vpn client address>

where I used the vpn IP (216.133.X.X) that was used to set up the VPN - same result

sorry - I didn't make myself clear. I meant the IP address that you are given by the VPN.
We're been messing with 2 addresses, the 1st is the default gateway on the VPN adapter and the other is the IP address given to the adapter itself.

I believe we need a route will looks like this: route add 192.168.0.0 mask 255.255.0.0 x.x.x.x (where x.x.x.x is the 192. address provided to your client after you have VPN'd in rather than the gateway address).

We may have tried that previously (I'm not sure).

So, to reiterate:

1) Reboot
2) VPN in
3) run IPCONFIG. You'll see the IP address given to the VPN adapter
4) run route add 192.168.0.0 mask 255.255.0.0 x.x.x.x (where x.x.x.x is taken from the output in (3))

If that doesn't work, I'm stumpted...

But if it doesn't. Could you post the 'route print' output when you've done the above, just so I'm sure it's not 'fat finger' syndrome

Edited by _DeeJay_ on Monday 3rd July 15:57

[hut49]

Guys - i have a teleconference to attend to back around 6pm. Pour yourself a beer or two and send me the bill!

[_DeeJay_]

hut49 said:

Guys - i have a teleconference to attend to back around 6pm. Pour yourself a beer or two and send me the bill!

OK - give it a go when you return, and the result routing table (route print) would make interesting reading.

We'll need a beer after this (and we're both in Cambridge I think )