WEIRD VPN Behavior
Tom
server and am totally clueless as to why this is happening. This
only happens with my userid.
I login to the SBS R2 from outside...my internal IP is 172.20.1.0/24
and I also have a 10.1.4.0/24 network. The VPN server also has
routes to 10.1.4.0. This works fine for all users and they can reach
10.1.4.0 network.
But when "I" login the server gets a new route. For example, when I
run "netstat -rn" I see the route that used to be 10.1.4.0 pointing to
172.20.1.1 now points to my IP on the VPN server (maybe 10.1.4.0 now
points to 172.20.1.200 from the VPN DHCP pool). That's weird enough
by it's self, but the other thing that blows my mind is...why does
that only happen with my account and if I use any other user ID to
login the routes stays ok, pointing to 172.20.1.1 and all is fine. I
know my account has domain admin privs, but still....why does that
happen at all? If other users have admin privs will that happen to
them too?
This is just too weird...I can't even think of a good lie to explain
this weird behavior...it's just weird!
Joe
Firstly, this can be done deliberately. In a user's properties, there is
provision for adding static routes to the SBS routing table when that
user connects by VPN. This is just possibly the explanation. (I'm
assuming you don't have a 10. network at the remote location.)
The other one is rather less tangible, but totally consistent with
'weird'. The 10. network is historically known as a 'class A' network,
run with a 255.0.0.0 netmask. AT&T have one (12.0.0.0) as do a few other
very large organisations. It appears that some software recognises 10.
as a class A, and gives it a 255.0.0.0 netmask even if you have
specified otherwise. I can't name names, as this kind of thing turns up
when you really need to get something working *now* and you don't have
time to experiment. I do know that I won't ever use 10. with anything
other than a class A netmask, and I believe Claus has had similar
experiences. If you need a 255.255.255.0 netmask, use one of the
192.168. networks.
I'd mention in passing that the 172.16. network 'traditionally' has a
255.255.0.0 netmask, and this may also cause issues, but I've never
personally experienced them as I have with 10.
Tom
Thanks much for the quick reply...I'm just so confused how this could
possibly happen...The odd thing is that when I use other accounts it
does not happen. In the users properties...are you speaking of on the
server or the client that's dialing in?
Thanks again!
Tom
Oh...I guess I can't be with the client, because it happens on any
system I use...I've tried 4 other systems and they all do the same, so
it has to be something on the server that's causing it to do that with
my profile, but I'm sure I have not intentionally altered my profile
settings on the server. jessh...some things ya just can't explain!
Claus
connection. Does the same happen?
--
Claus
"Tom" <tdenh...@gmail.com> wrote in message
news:9a9da7ce-ec4f-4c88...@d4g2000prg.googlegroups.com...
Tom
> I would try to delete your profile on the server and then try a fresh
> connection. Does the same happen?
>
> --
I finally figured this one out!
I didn't remember this, but because was the first time I setup SBS
VPN, I was remember trying to assign static routes at the very
beginning so that I would not have to use the default gateway on the
VPN pipe. Under my profile in the "Dial-in" I found a button to
"Apply Static Routes". I had forgot all about doing this!
Well...apparently the routes were not applied properly...maybe related
to issues discussed above with the 10.0.0.0 networks. Once I removed
the "Apply Static Routes" rule everything was fine again. Turns out it
was me (the admin) saying "I didn't do anything unusual"...LOL! Guess
I actually did:( Lesson learned. Sorry for taking your time helping
out:)
Claus
--
Claus
"Tom" <tdenh...@gmail.com> wrote in message
news:ae9f4204-1105-411b...@f10g2000hsf.googlegroups.com...