a-johnbe
Wed Jun 16 20:15:46 CDT 2004
To work around this issue you should first verify connectivity. The
following article is a good place to start.
320697.KB.EN-US HOW TO: Turn On and Configure Inbound VPN Access in Small
Business
http://support.microsoft.com/default.aspx?scid=KB;EN-US;320697
Once connectivity is established and the clients can connect to remote
network services directly. There are two options for using your network
browser.
OPTION ONE
===========
Use WINS and LMHosts file.
First, Verify that WINS is running on the Server and all clients point to
server for WINS resolution.
Two, Create a LMHosts File for every workstation that needs to browse
through VPN.
The LMHosts file must contain the following entries:
xxx.xxx.xxx.xxx SERVERNAME #PRE #DOM:DOMAIN-TEST
xxx.xxx.xxx.xxx "DOMAIN-TEST \0x1B" #PRE
xxx.xxx.xxx.xxx "DOMAIN-TEST \0x1C" #PRE
Where:
xxx.xxx.xxx.xxx is the server's IP address for the internal LAN connection
DOMAIN-TEST is the NetBios name of their domain
SERVERNAME is the NetBios name of their server
You must use the quotes around the domain records
There must be exactly 15 characters/spaces between the first quote and
the backslash.
For more information on creating a LMHosts file, see:
Q180094 How to Write an LMHOSTS File for Domain Validation
http://support.microsoft.com/support/kb/articles/q180/0/94.asp
Once the edited LMHosts file is in place, run the following commands from
DOS prompt.
nbtstat -RR (to load to cache)
nbtstat -c (to verify that the entries have been cached)
OPTION TWO
===========
Configure only the network resources needed by the client.
STEP 1: Using the 'FIND' command on the Start menu choose Computer. In the
Named box enter "\\<computer_name>" without quotes where computer_name
refers to the computer being statically added to network neighborhood.
Again, this article assumes that Windows Networking has been properly
configured and connectivity can be established between these two machines.
Step 2:
Once the machine has been found, simply drag and drop the machine icon into
network neighborhood. When you are prompted to create a shortcut, select
yes.
Optional Step 3: Once the icon is dropped into Network Neighborhood, it can
be renamed. To populate many machines on the LAN/WAN, the .LNK files
created in this process can be copied to the Nethood directory of any user
profile. Once that user logs off and then logs back on again the static
entries in Network Neighborhood will list permanently.
You may also want to look at:
Name resolution and connectivity issues on a Routing and Remote Access
Server that also runs DNS or WINS
http://support.microsoft.com/?id=292822
Regards,
John Behneman MCSE NT/2000
Microsoft Corporation
Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.