• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 355
  • Last Modified:

Domains do not appear in network places browse list

I have two locations I recently setup a VPN for, one in the US and one in Jamaica.  The VPN is from a Watchgaurd Firebox to a Linksys router and it works fine.  The two networks are on different subnets.  The network behind the watchguard is on the 192.168.1.x subnet and contains two domains with a 2-way trust. The network behind the linksys is on a 192.168.3.x subnet and contains only 1 domain.  I can ping all the servers and workstations from both locations.  I can also type \\hostname\folder and access the computers across the vpn that way.  But the domains do not show up in the network browse list, making it impossible to create the trust between the domains across the vpn.  The domain in Jamaica is a AD domain and has one 2003 server.  The domains here, one is an NT domain, and one is an AD domain 2003 server.  Any suggestions on how I can get them to show up?
1 Solution
Have you tried manually adding entries to your LMHOSTS file via the methods listed  here >> http://support.microsoft.com/?kbid=150800#kb1 .  Basically you're adding a \0x1b for each PDC.

Scroll down to the section on mult-domain browsing with LMHOSTS and see if this helps.

- dan -
Setup a WINS Server at both locations. (Add remove programs - windows componets - wins server)

Set them to replicate to one another.  

Set your server and computers in your domain to point to the WINS Server. (Just add the wins server address in DHCP)

This will your computers to see each other in network neighbour hood.
darkhawk23Author Commented:
I have Wins setup on both sides, and have added the wins server ip's to the pdc's and global catalog servers, and also to the dhcp scopes on both sides.  I can ping the computername, so name resolution is working, but the domain doesn't appear in my network places.  By the way, all the workstations on both sides are XP Pro.
Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Does nothing show up in network neighbourhood? Does your local domain show up?
darkhawk23Author Commented:
I can see the normal computers and domains there,  just not the domains that should show up now the vpn is up...i.e.
Site1  Quality, QMM   Site 2 QMJ          
Site1 should see QMJ now, and Site 2 should see Quality and QMJ now
darkhawk23Author Commented:
I tried to create LMHOSTS files like in the kb article, but i must be doing something wrong.  Here is my configuration:

Domain:       QMM                        Domain:          Quality                           Domain:      QMJ
QMMPDC              QM-PDC                  QMJPDC

That's all the statics of any importance that i would need my users to see.  Could help me create a proper LMHOSTS file to import?
darkhawk23Author Commented:
I removed the Wins Server in the remote location, becauase all the pc's are XP.  I changed the server tcp/ip setting to point to wins server here, and changed their dhcp scope.  I had setup static WINS mapping in Wins manager here to point to them, so i deleted those as well.  Then, I remoted into their server and sent a ping request by computer name to the wins server here and the other static address so they would be in the cache.  After that, I checked out the the network places, and the domains showed there and they showed here.  Funny, don't know exactly what fixed it but it did.  So, problem solved.
Glad to here you got it solved!!!
PAQed with points refunded (500)

Community Support Moderator
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now