I have a user connecting to our network via Microsoft VPN. They are able to establish a connection and open a terminal emulator that uses telnet, but they cannot open email, resolve names or ping names and IP addresses. When I ping the ip or the name, it just times out. If I do an ipconfig /all, it is listing our DNS servers, but it doesn't appear that it is using our DNS. This is only happening on users that have OptOnline for a cable provider. I have users connecting via Comcast that are not experiencing the problems. Any ideas? Thanks.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
No ping from VPN Connection
- Thread starter mortkc
- Start date
- Thread starter
- #3
John Lewis
Programmer
My guess would be routing issues, although I wouldn't expect telnet to work either.
Do you have public IPs on the server side network, or are you NATing? Specifically, does the server that you are telnetting to have a public IP?
On the client side, try to ping the VPN connection server side IP. Fire up the connection, open the status box for the connection and click on details. Two addresses should be listed. First ping the server. If that doesn't work, try the client. Both should work.
Another thing that just popped into view, if OptOnline is assigning users private IPs that happen to fall on the same RFC network as your server side network or the addresses assigned to RRAS, you could see something similar, although again I would be surprised that telnet works.
Try a tracert to the IP of the telnet server. Make sure it is hitting the VPN as the first hop. Also, look at the routing table on the client (ROUTE PRINT).
Not going to be an easy one. Be patient and stick with it.
Do you have public IPs on the server side network, or are you NATing? Specifically, does the server that you are telnetting to have a public IP?
On the client side, try to ping the VPN connection server side IP. Fire up the connection, open the status box for the connection and click on details. Two addresses should be listed. First ping the server. If that doesn't work, try the client. Both should work.
Another thing that just popped into view, if OptOnline is assigning users private IPs that happen to fall on the same RFC network as your server side network or the addresses assigned to RRAS, you could see something similar, although again I would be surprised that telnet works.
Try a tracert to the IP of the telnet server. Make sure it is hitting the VPN as the first hop. Also, look at the routing table on the client (ROUTE PRINT).
Not going to be an easy one. Be patient and stick with it.
- Thread starter
- #5
when pinging and running tracert, some of the users are resolving the public side addresses, and not the private network. They are able to open a telnet and map network drives, but not open outlook email. When opening email, it prompts for user, password and domain, but then fails on the login credentials.
I am seeing exactly the same thing. My desktop at home, VPN over DSL, works without a problem. My laptop at home, VPN accessed by AOL (yuk... it's a corporate thing) via 56K dial up can map drives, see the other network machines but fails credentials when logging into Exchange 2K with Outlook 2K. OWA works on both. Both machines are running W2k (desktop SP3, laptop SP4).... Help?
- Status
Similar threads
- Locked
- Question