Windows NT 4 server VPN connection trouble

[imij11]

I have a server at work that's running Windows NT 4 Server w/ SP6a. I'm trying to connect to it on a Windows XP PC over the internet through a PPTP using RAS on the Server. I can establish a connection with the XP client and I can ping the IP addresses on the office network from a DOS shell. I can't, however, find the computers in Windows XP "Network Places" even if I search by IP address. I tried using the "Net Use" command to create shares but to no avail. I'm sure that not being able to find PC's by name on the office network is a DNS issue but I don't understand why I can't find them by IP.

Also, the NT Server is directly connected to the internet and is routing access to the rest of the office Using Sygate software. Thus there are 2 network cards in the server. This was done because the ISP wanted to charge a ridiculous amount more more if we used a router to share internet access. This option was the loop hole. Any help would be greatly appreciated.

 

[ChicagoTechNet]

sound like name resolution issue. quoted form

http://www.ms-mvps.com/

Unable to access the resources on the network
1) Check the DNS and WINS setting. 2) Verify that either the protocol is enabled for routing or the Entire network option is selected for LAN protocols being used by the VPN clients.

Unable to browse through PPTP/VPN connection
Symptoms: 1. If the WINS server is on the same computer as the PPTP/VPN server, and you attempt to connect to a computer using a PPTP/VPN client, you may experience following problem: 1) The NetBIOS name of the computer to which you are attempting to connect is not resolved. 2) You may receive an error message similar to the following error message: "System error 53 has occurred. The network path was not found" when using net view or opening Network Knighthood.
2. If the WINS server is not on the same computer as the PPTP server and you attempt to connect to a computer using a PPTP client, you may be able to connect to computers on your local area network (LAN), but you may be unable to connect to network shares or resources on the PPTP server.
Resolutions: Inability to browse often means the client can't resolve NetBIOS names.
1. If this is a workgroup network, enable NetBIOS over TCP/IP on the server and clients.
2. If this is domain network and the WINS server is on the same computer as the PPTP/VPN server, move the WINS server to a different computer.
3. Add the NetBEUI protocol for your PPTP tunnel instead of, or in addition to, TCP/IP.
4. By default, most routers and firewalls prevent the transmission of NetBIOS names unless you enable UDP ports 137 and 138 and TCP port 139. Try to enable UDP ports 137 and 138 and TCP port 139 across all routers and firewalls between the PPTP/VPN client and PPTP/VPN server.
5. Make sure the client has correct DNS, WINS and Master Browser settings.
6. Make sure the default gateway points to the remote network rather than to the ISP.
7. Some ISP might block ports required for NetBIOS name broadcasts.
8. If WINS address is not distributed upon connection to VPN, LMHOSTS should be configured to enable Domain to be located.
9. If you try these techniques and the client still can't browse, try to use UNC to connect to the remote resources by ip, for example, use the net use h: \\serverip\sharename command.


Robert Lin, MS-MVP, MCSE & CNE
Windows, Network, Internet, VPN, Routing and How to at

http://www.ms-mvps.com