General discussion

Locked

Unable to browse domain

By jlbpotter ·
I have a couple of XP boxes that will not browse a domain. These boxes are on a 2K domain and have no problem browsing their domain. When using My Network Places and trying to connect to a trusted NT4 domain they get an error stating that the path is not found. But what I can do is copy a shortcut from another machine that points to any machine in the NT4 domain and I am able to get to that machine. That is the only way I can get in. I can't browse the domain, I can only go straight to a machine if I know it's name. Any ideas? Thanks

This conversation is currently closed to new comments.

5 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Unable to browse domain

by TechKid In reply to Unable to browse domain

make sure "enable netbios over tcp/ip" is selected in your network card properties

Turn off "simple file sharing" in Windows Explorer>Tools>Folder Options>View> all the way at the bottom it says "Use simple file sharing". Uncheck that

Collapse -

Unable to browse domain

by jlbpotter In reply to Unable to browse domain

Tried those. Did not work. Thanks anyways.

Collapse -

Unable to browse domain

by ctmoore1998 In reply to Unable to browse domain

What protocol are you using? Let's assume TCP/IP. So Next what is the TCP/IP configuration that you are using static or DHCP? I assume that the trust relationship is from the NT domain to the 2000 domain, and IP forwarding is configured on the 2000 server?? If not then you will have to list the NT4 server in the LMHOST file for the workstation so that it "knows" the NT4 server. An example would be the 2K server IP is 192.168.0.4 S/N 255.255.255.0; XP workstation DHCP from 2K server 192.168.0.42 S/N 255.255.255.0 {DNS is properly configure on the 2k server} NT4 server 192.168.22.2 s/n 255.255.255.0 See if the 2000 server has 2 NIC one in the .0 network and one in the .22 network and is configure to forward IP's then you should be able to access the NT box from the XP workstation. However if there is a single NIC and the NT4 is in the .0.xxx network then the problem lies in the DNS of the 2k server. You must make the appropiate DNS entry so that the NT will be accessible.

Collapse -

Unable to browse domain

by jlbpotter In reply to Unable to browse domain

Poster rated this answer

Collapse -

Unable to browse domain

by jlbpotter In reply to Unable to browse domain

This question was closed by the author

Back to Windows Forum
5 total posts (Page 1 of 1)  

Related Discussions

Related Forums