Server 2003 VPN quirk with single user

[ECCOGuy]

This is a new one for me! I'm on a small network with one Server 2003 Std and one 2003 SBS. Both only have one NIC each. I've several other users that VPN in on an almost daily basis with no problems. I have one user who's account has been around longer then I've been with the company (as are most of the accounts). Go figure this issue is the president's account! When you create a VPN tunnel (these are PPTP tunnels), it connects just fine. What happens, though, is that ANY other connection to that server hangs! The Std server is a file server and SQL, all connections except the president's tunnel hangs, and does not respond until the VPN is disconnected! The SBS is also doing exchange. When I try to VPN to that server, it does the same thing. Everyone's connection to Exchange is broken until the VPN tunnel is disconnected. And by everyone I mean LAN connections, everything. I've tried from serveral different workstations, inside or outside the router. As I said at first, I have at least 5 other users that have no issue; it seems only related to his account. What I've gathered is that before I worked here the accounts were migrated from a w2k AD to a 2003 AD. I'd perfer not to recreate his account and recreate all his permissions, but I'm not too sure what other things to look at, so I'm asking everyone here for some help!

Thanks

Spencer
MCSE2k, MCSA2k, Net+, A+

 

[msworld]

Sounds like name resolutions. It depends on how you setup the VPN, the server may register two name records on the WINS or DNS so that everyone lose the connection to the server. This link mayhlep.

Name resolution on VPN
That reason is that VPN server is a Virtual Multihomed Server. The resolution is to disable NetBIOS Over TCP/IP and DNS register on all interfaces including ...

http://www.chicagotech.net/nameresolutionpnvpn.htm

Bob Lin, MS-MVP, MCSE & CNE
How to Setup Windows, Network, VPN & Remote Access on

http://www.HowToNetworking.com

 

[ECCOGuy]

Thanks for the tip... But I don't think that addresses why it only happens when he tunnels in. At least five other users tunnel in daily without the issue manifesting.

Spencer
MCSE2k, MCSA2k, Net+, A+

 

[ECCOGuy]

I just found it out. The previous Network Admin (if you could call her that!) had added a static route under his account in the dial-in connection tab that pointed to our local network. What it looked like it was doing was every time he opened the tunnel the server re-routed all connections through his tunnel. Hence everyone's connection hung until he closed his tunnel. I figured it was something with his account, but I couldn't put my finger on it until I starting digging though the AD with an LDAP viewer and compared his account to another's!

Thanks for the help, though!

Spencer
MCSE2k, MCSA2k, Net+, A+

 

[msworld]

Thank you for the feedback.

Bob Lin, MS-MVP, MCSE & CNE
How to Setup Windows, Network, VPN & Remote Access on

http://www.HowToNetworking.com