First of all, ensure you have shared at least one folder in the other PCs because some MS-Windows boxes cannot be seen in the network neighborhood unless their folders/printers are shared.
If your target PC is in the same LAN, i.e. they are connected to the LAN ports of the same Vigor Router.
1. Make sure that you have installed ” Client for Microsoft Networks ” and “File and Printer sharing for Microsoft Networks ” on your all PCs.
2. Make sure that you have enabled “NetBIOS over TCP/IP ” on all PCs. This is the default on Windows XP, but will have to be set manually on Windows 95/98.
3. Make sure that you have turned off any firewalls on all PCs. When you have communication working you can turn the firewall back on, and if this was causing the problem change its configuration to NOT block packets from LAN addresses (192.168.1.*).
4. Telnet into your router to check telnet command “mngt defenseworm on/off “. This function is used to defend against network attacks and blocks TCP 135,137,138,139,445 by default. Use “mngt defenseworm off ” to turn it off.
IF your target PC is in a remote LAN via ISDN or VPN, try the following:
In “Network Neighborhood”, search for the PC using its IP address instead of browsing for it by name. eg type \\192.168.1.x in the address bar of Windows Explorer.
If that works, you can create a way to search by name using lmhosts file:
- Search the ‘lmhosts.sam’ file in your PC.
- Rename ‘lmhosts.sam’ as ‘lmhosts’ (no file extension).
- Follow the example in the lmhosts file to add a line like “192.168.5.38 DrayTek” where the actual values depends on your network environment.
- This will need to be done on all PCs on the network who would like to find that computer by name
An alternative to modifying the lmhosts file is to set up a WINS (Windows Internet Name Service) server at both ends of the VPN tunnel.