2003 server cannot browse the domain
I have a 2003 server that cannot browse the domain for windows explorer. When I click the domain, I get DOMIAN is not accessible. You might not have permission.... The parameter is incorrect. Also, I cannot browse local shares from the
server. \\server\share is not accessible... No network provider accepted the given path.
Event viewer is also shows Bowser event 8021 and 8032.
I have research the problem and have tried everything I can find to troubleshoot this issue.
February 16th, 2011 8:56pm
Hi
Is your server a member of the domain?? if not add it.. if it is a member then do the credentials you are using to log on to the server have permissions to carry out the tasks you want to carry out?? And normally the error "No network provider
accepted the given path" could be a networking issue ip addressing on your server make sure it is correct.. if you can send an ipconfig /all of this server and the machines you are trying to connect to that would be great.. but you can also check to make sure
you are in the same network as the rest of the machines and that subnet mask is correct and also that you have the correct DNS settings on your server if you are using the
\\someonescomputername\share :)
I seriously think its a problem with your ip addressing though... check it out and confirm. post the ipconfigs /all i asked for,, from the server and form another machine pref the machine you want to access
tech-nique
Free Windows Admin Tool Kit Click here and download it now
February 16th, 2011 11:54pm
I fairly confident it is not an IP addressing. I can access shares on this server from any other machine on the domain. Just not from itself. I am a Domain admin so permissions should not be an issue.
February 17th, 2011 12:22am
Hi Armstic
Is your server on the same network as the other machines??? The error message you are getting is usually associated with wrong gateway ip address or incorrect routing on the router which does not provide a route for the server to take when looking for a
client outside its network.. but if routing is correctly configured from your clients to the server they will access the server files but the server won't be able to access their files because it doesnt know how to get there.
I really wish you could have sent in the ipconfig /all results so we get a basis to start from, Please even if you are fairly confident that is not the issue.. post up the IPCONFIG /ALL i asked for so we can work on this issue.
Looking foward to your prompt cooperation :)tech-nique
Free Windows Admin Tool Kit Click here and download it now
February 17th, 2011 8:14pm
I can ping every thing from the server and and vice versa, so this is not a IP issue. The fact that I can access the shares on this server from a remote machine also proves this, because the server would not be able return packets if there was a gateway
problem. Is there someone who understands IP that can help?
February 23rd, 2011 5:02pm
Hi
is your server multihomed or was it multihomed before (does the server have 2 NICS both of them with ip addresses and connected to the network?)?
are u using teaming or any other sort of NLB or failover mechanism??
Is DNS configured on this server?? which roles are running on the server ?? And is DNS working properly (test with NSLOOKUP), and please post up the results..
the more you cooperate with what we need to troubleshoot your problem the easier it wil be and the faster it will all be..
ipconfig /all would have told us the answers to most if not all the questions i am now having to ask you yet you could have given us this information a long time ago.tech-nique
Free Windows Admin Tool Kit Click here and download it now
February 23rd, 2011 6:10pm


