Hi all, here is my issue.

I have a DC running windows 2000. When I browse My network places on this
server, nothing is listed. When I browse from another server I see
everything except this server. WIERD!

I can ping it fine, by IP or Name.

When I try to browse it by \\servername. I get a error. but while on the
server in question, i see all the shares and printers.


HELP!

You are using WINS-Server for name resolution ?
Do you have configured the WINS-Server correctly ?

If you don't use WINS:
Have a look at the Netbios-Node-Type. Should be "something with broadcast"
Must be set in the registry - as far as I know.
http://www.comptechdoc.org/os/window...win2kwins.html

"Sean H" schrieb:

Yes, I am using WINS

as far as I can tell, it is working fine.. This is something that happened
recently, and unfortunatly, i am taking over this server from someone else
who has left the company.

Like I said, all other machines see everything they need to, but this one
does not see anyone (or even itself) and others do not see it.


"Juergen" wrote:

Try:

1. Make sure File and Printer Sharing and NetBIOS over TCP/IP is enabled.

2. Restart the Server service.

3. Check Event Viewer for errors.

4. Check whether the hidden administrative shares are created - if not see:

http://support.microsoft.com/default...b;en-us;318755

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP

"Sean H" <SeanH@discussions.microsoft.com> wrote in message
news:2BFDDD6C-AAD7-429E-9E7F-B7742170B387@microsoft.com...

Thanks Doug,

Did what you mentioned time and time again, but I did it once more for
kicks.. same results.
I have a ton of errors and warning because it cannot talk to anyone. They
include mrxsmb warnings (id 3034) and application warnings of Scecli (id 1202)

Admin shares are there. I can browse to them from that server. but from
anywhere else...forget it.

another interesting tidbit is that I cannot \\servername any other machine
from the affected server. it gives me an error. Logon error: The target
account name is incorrect. but again, this is just happening from the affect
box!

"Doug Sherman [MVP]" wrote:

Hmmm. Try dcdiag - if you get LDAP bind 31 error, see this:

http://support.microsoft.com/default...b;en-us;826902

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP

"Sean H" <SeanH@discussions.microsoft.com> wrote in message
news:C2A86E05-7C25-425C-9154-6FAE86FC3FC5@microsoft.com...

Doug,

Looks like you may have nailed it. I did get an LDAP bind 31 error.

I am going through the processes in the article. I will let you know the
results

Thanks a million!!! If this works, you just saved me a reload!

"Doug Sherman [MVP]" wrote: