Discussion Locked

VPN Problems

0 helpful
14 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have only one computer which just fails to make a good VPN connection to the network. It is a Windows 2k Pro workstation. I makes the connection to the network fine, but once connected the only think that I can do with it is ping the servers. I have a webserver in the network and I can ping it also but when I try to view the website via the internal IP address, I cannot. I also cannot connect to the Exchange server with this workstation VPNed in. The user is not a problem since the sameuser can logon with other computers just fine. I have compared all of the settings with other computers just like it and I cannot find any difference. When I do an ipconfig /all, the DNS and WINS servers are correctly listed. I am out of ideas with this PC. This problem PC is normally a dial-in PC. It is not a member of the domain. The workgroup is just called workgroup. I have the same configuration on another Win2k Pro computer with no problems. What I am seeing is that I cannot use any of the TCP ports when VPNed in. I cannot browse Intranets which I have no problem with on other equally configured PCs, I cannot check Exchange mail, I cannot telnet to the exchange server, I cannot FTP. I have tried all using names and IPs withno success. I can ping the server names or the IP addresses. Any Ideas?

14 replies

by contact

i propose you to try Symantec Ghost.
It make you able to clone an other equally configured PC.
you just have to modifing IP and name.

by scifiman

I agree that if you have another W2K working through VPN, try making the clone. However, you may want to try:

1) Try disabling WINS since W2K doesn't need it (unless you have a mixed environment.
2) You didn't mention tunnel setup problems, so after the dialin is successful try mapping one share (net use * \\10.5.5.5\share) and check network neighborhood and you should see hosts.
3) Have you tried the working VPN client ID on the problem PC?
4) Are you running W2K Server? I would thinkthe problem PC must still become part of the Domain if it wants to use services and browse My Network Places. Change Workgroup to your correct domain name.
5) What is authenticating the VPN, your firewall or W2K?

by gbainbridge

No one's mentioned this yet, so I will--

One thing to check would be whether or not you're logging on to the domain. Since you're authenticating with the VPN server, you are successfully becoming part of the IP network, which explains why you can ping hosts. However, unless you're logging on to the domain where the VPN server resides, you won't have domain authentication, which means you won't be able to use anything that potentially requires a domain user account to access (such as an intranet or Exchange server). Even if you authenticate with the same user name and password as you use on the domain, unless you specify the domain, you're not part of it.

In your VPN connection properties, go to the "options" tab and select "Include Windows logon domain." Now, when you specify your username and password, you'll also be able to specify the windows domain name of the network you are connecting to.

Good luck.

by eduardo

dmccarthy:

1. I had with and without WINS. It didn't make a diference.
2. tunnel setup is fine. I am unable to do anything with this PC VPNed in but ping all of the hosts. No other computers that VPN in have this problem.
3. I tried this after you emntioned it. It didn't make a difference.
4. Yes, Win2k server. I plugged in the PC to the LAN and made it a part of the domain. I then disconnected if from the LAN, used the modem to dial up to an ISP and then VPN in (same as all others,) and the same problem was present. I did not have any problems when it was connected directly to the network.
5. Win2k is authenticating. The IAS logs show a successful logon.

I think that this is more of a configuration problem on the PC itself and not on the network. Anything there that you can think of? Thanks.

gbainbridge:

I have not tried this, I do not have the PC anymore but I will walk the user and have him try this. I will mention though that on all other PCs, that option did not have to be checked in order for everything to work fine. It is worth a shot. Thanks.

by eduardo

dmccarthy:

1. I had with and without WINS. It didn't make a diference.
2. tunnel setup is fine. I am unable to do anything with this PC VPNed in but ping all of the hosts. No other computers that VPN in have this problem.
3. I tried this after you emntioned it. It didn't make a difference.
4. Yes, Win2k server. I plugged in the PC to the LAN and made it a part of the domain. I then disconnected if from the LAN, used the modem to dial up to an ISP and then VPN in (same as all others,) and the same problem was present. I did not have any problems when it was connected directly to the network.
5. Win2k is authenticating. The IAS logs show a successful logon.

I think that this is more of a configuration problem on the PC itself and not on the network. Anything there that you can think of? Thanks.

gbainbridge:

I have not tried this, I do not have the PC anymore but I will walk the user and have him try this. I will mention though that on all other PCs, that optiondid not have to be checked in order for everything to work fine. It is worth a shot. Thanks.

by estebandelatorre

I agree with answer 3 and item 2 of answer 2

Also check tcp/ip properties, the Advance tab, wheter or not have one or more a port disabled.
Also make sure that from the ISP node, you can sucesfully log-in across a VPN. Some providers had disabled this feature in order to sell another "level" of service (VPN Aware!)

by maxwell edison

This discussion is closed to new replies.