Unable to see Server Files 1

[romh]

Ok. I know there is a FAQ on this but I still dont; understand the soloution. I have a Windows 2000 Adv server AD at work. I set up a VPN on the server. I then tried to establish a VPN from home (from Windows XP prof.). The connection succeeds but I do not know how to reach or even view the server files at work. I've tried using Network Neigborhood, and that doesn;t work. I've tried going to
\\servename\sharename in Windows Explorer and IE and that doesn;t work either.

I tried looking this problem on Yahoo and Microsoft support and it seems like the explanatiion has something to do with WINS server. But I don;t understand it. So what do I have to do in order to view the contens of the server from home with a VPN, in order to copy and move files between them?

Thanks

 

[ChicagoTechNet]

this may help you. quoted from

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

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

 

[romh]

I've read that before and thought that might be useful, but is step 1 and 2 referring to the client's network or the VPN server's network? Does number 3 refer to the client's or VPN's computer?
Could you clarify that for me?


Thanks