Using VPN, loose conectivity with exchsrv

  • Thread starter Thread starter John Flint
  • Start date Start date
J

John Flint

All,

Have a situation where a user on win2k logs in to their
VPN and then is unable to get to the ip of the exchsrv. if
i log them out of the VPN we can gdet to the exchsrv again
(computer1). tried having them log on from another
computer (computer2) known to be able to reach the exchsrv
while connected to the VPN. Doing that we were sucessful
in getting to the exchsrv. So we ruled out a permissions
problem in the VPN logon. Set the computer (computer1) up
in a different location having a different person log on.
same problem as before, so it's not a perms problem with
the user.
QUESTION: What could be setup incorectly to keep ip's
being accessed through the VPN on win2k?
 
You need a hosts file - can't just use the IP address of the Exchange
server, it will want to resolve to a name. Set up an entry in hosts for
xxx.xxx.xxx.xxx (internal IP of Exchange server) to SERVERNAME
 
But I did that already. I try to ping either the server name or IP and I
can't resolve the IP address. if I come off the VPN I can resolve the IP
again. for some reason the IP is being blocked once logged in. Almost as if
it connecting to the wrong network. but I assure you it is the correct one,
otherwise we wouldn't log in in the first place.

John Flint


"Lanwench [MVP - Exchange]"
 
Which IP - public or private? If you're connected via VPN, you should be
using the internal IP and the server's NetBIOS name....

John said:
But I did that already. I try to ping either the server name or IP
and I can't resolve the IP address. if I come off the VPN I can
resolve the IP again. for some reason the IP is being blocked once
logged in. Almost as if it connecting to the wrong network. but I
assure you it is the correct one, otherwise we wouldn't log in in the
first place.

John Flint


"Lanwench [MVP - Exchange]"
You need a hosts file - can't just use the IP address of the Exchange
server, it will want to resolve to a name. Set up an entry in hosts
for xxx.xxx.xxx.xxx (internal IP of Exchange server) to SERVERNAME
Click to expand...
Click to expand...
 
Correct.. Well I fixed the problem, but only because I installed winXP.
everything was setup just the same as I do now, but for some reason the OS
was glitching.. That's the problem I was having. If inside you network you
are allowed to ping, then when you connect to the VPN you should beable to
ping the exchsrv. This is what I couldn't do before, but after starting all
over, I can do now..

I would still like to know why the hell did win2k act like that though. It
just doesn't make sence. Maybe a reg entry or something?

John Flint


"Lanwench [MVP - Exchange]"
Which IP - public or private? If you're connected via VPN, you should be
using the internal IP and the server's NetBIOS name....

John said:
But I did that already. I try to ping either the server name or IP
and I can't resolve the IP address. if I come off the VPN I can
resolve the IP again. for some reason the IP is being blocked once
logged in. Almost as if it connecting to the wrong network. but I
assure you it is the correct one, otherwise we wouldn't log in in the
first place.

John Flint


"Lanwench [MVP - Exchange]"
You need a hosts file - can't just use the IP address of the Exchange
server, it will want to resolve to a name. Set up an entry in hosts
for xxx.xxx.xxx.xxx (internal IP of Exchange server) to SERVERNAME

John Flint wrote:
All,

Have a situation where a user on win2k logs in to their
VPN and then is unable to get to the ip of the exchsrv. if
i log them out of the VPN we can gdet to the exchsrv again
(computer1). tried having them log on from another
computer (computer2) known to be able to reach the exchsrv
while connected to the VPN. Doing that we were sucessful
in getting to the exchsrv. So we ruled out a permissions
problem in the VPN logon. Set the computer (computer1) up
in a different location having a different person log on.
same problem as before, so it's not a perms problem with
the user.
QUESTION: What could be setup incorectly to keep ip's
being accessed through the VPN on win2k?
Click to expand...
Click to expand...
Click to expand...
 
Not sure - now that W2k is gone it's not possible to troubleshoot, but hey,
it's working, so maybe we should just chalk it up to a Mystery of the
Cosmos? ;-)


John Flint said:
Correct.. Well I fixed the problem, but only because I installed winXP.
everything was setup just the same as I do now, but for some reason the OS
was glitching.. That's the problem I was having. If inside you network you
are allowed to ping, then when you connect to the VPN you should beable to
ping the exchsrv. This is what I couldn't do before, but after starting all
over, I can do now..

I would still like to know why the hell did win2k act like that though. It
just doesn't make sence. Maybe a reg entry or something?

John Flint


"Lanwench [MVP - Exchange]"
Which IP - public or private? If you're connected via VPN, you should be
using the internal IP and the server's NetBIOS name....

John said:
But I did that already. I try to ping either the server name or IP
and I can't resolve the IP address. if I come off the VPN I can
resolve the IP again. for some reason the IP is being blocked once
logged in. Almost as if it connecting to the wrong network. but I
assure you it is the correct one, otherwise we wouldn't log in in the
first place.

John Flint


"Lanwench [MVP - Exchange]"
message You need a hosts file - can't just use the IP address of the Exchange
server, it will want to resolve to a name. Set up an entry in hosts
for xxx.xxx.xxx.xxx (internal IP of Exchange server) to SERVERNAME

John Flint wrote:
All,

Have a situation where a user on win2k logs in to their
VPN and then is unable to get to the ip of the exchsrv. if
i log them out of the VPN we can gdet to the exchsrv again
(computer1). tried having them log on from another
computer (computer2) known to be able to reach the exchsrv
while connected to the VPN. Doing that we were sucessful
in getting to the exchsrv. So we ruled out a permissions
problem in the VPN logon. Set the computer (computer1) up
in a different location having a different person log on.
same problem as before, so it's not a perms problem with
the user.
QUESTION: What could be setup incorectly to keep ip's
being accessed through the VPN on win2k?
Click to expand...
Click to expand...
Click to expand...
 
Back
Top