Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Unable to browse network

Status
Not open for further replies.

deboge

Programmer
Aug 9, 2002
2
CA
I have a windows 2000 server setup as a stand alone server in our network. There is a primary 2000 server which is a pdc and there are about 10 windows 2000 pro machines in the network.

The system that cannot browse the network is setup as terminal server in applicatin services mode and is also running licensing services therefore i cannot set it as a member server. (which i have done trying to resolve the problem but it did not work) The service packs are all up to date. This system can be accessed from all machines which see it fine, and they are able to run terminal service sessions fine. I am able to get to all shared folders drives and printers on the problem machine. The problem i am having is when i am on the system itself i can not access any other computer even using the netbios name or ip address. I can use net view at the dos prompt and see the resources available on the other machines. I can ping by netbios name or by using ip address. When i use net use command with the \\name or \\ip address i get the system giving back an error 67 cannot find network name.


Any help would be appreciated.
 
I know it sounds odd, but sometimes you'll get that error if you try to connect resources with invalid credentials. Since this server is not a member of the domain, the local account you're logging in with will not be recognized by your DC. Try doing the NET USE command with the "user" parameter as a test:
NET USE * \\servername\sharename /u:your-domain\valid-domain-username
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top