Browsing the Network

[briteeyez]

Hi

I cannot browse my network from my second domain controller. I have a 3Com 24 Port 10/100 switch. I am running Windows 2000 server with about 15 clients running Win2000 Pro. I use RJ-45 cables. I can at times ping the server and get responses, however I cannot browse via Network Neighbourhood. If I use network neighbourhood i have to browse by IP's. Everytime I try to browse the network via \\servername, i get the error - "logon failure: the target machine name is unavailable." The clients on the network however can ping the PDC without any problems as well as the second domain controller in question.

Here is the thing, i do not have any errors being logged within my event viewers, however the only warning i am logging is that license logging warning where it states that the file replication failed between the two servers because the PDC could not be contacted.

Everytime i try to print from the machine in question i get the error the "RPC is unavaliable".

Someone please help, any assitance would be greatly appreciated.

 

[porkchop1214]

try that in the cmd mode first

nbtstat -n
&
nbtstat -a <your pdc name>

see whether it has conflict or not first Kill Ghost Prince

 

[briteeyez]

There are no conflicts. any other ideas.

 

[shawnpd40]

Can you browse from the first DC? Also, can you map to another machine using the IP address and share name (\\192.168.1.1\myshare)?

What type of name resolution service are using? Active Directory with DDNS? If not I assume WINS? If you are running WINS, then you will have to ensure you have selected NetBIOS over TCP/IP on the WINS tab for TCP/IP properties.
One thing I read last night is that MS recommends running your WINS service on a machine other than your (P)DC...

 

[briteeyez]

i am running active directory and dns. i do not have wins running. do you recommend that i should. i can browse from the first domain controller without any problems.

 

[jonwilbanks]

Sounds like DNS problems. Try changing DNS server in NIC properties of second server to ip address of PDC.

 

[jonwilbanks]

Try changing DNS server in NIC properties of second server to ip address of PDC.

 

[briteeyez]

It is set to the PDC dns ip address. thats not it.

 

[shawnpd40]

Briteeyez,
If you don't need to run WINS and are running AD in a DDNS environment, I would discourage you from installing WINS...but sounds like you have some name resolution issues.

Let me do a little more research to see if I can help...please let me know if you get this resolved...name resolution always seems so simple yet how many times do we work these issues?

 

[briteeyez]

thanks for ur help shawn, question thou - why do you discourage running WINS.

 

[koquito]

try on the problematic DC, net sessions /delete /y
try it until you see no sessions with your DC.
INmidiately after that, go to a workstation, log in to the network, and go to Run-->\\servername to see what happens. A+, MCP, CCNA
marbinpr@hotmail.com

Keep fighting for your knowledge!

 

[shawnpd40]

briteeyez,
I am no longer a fan of WINS of you are running a native 2000 domain. WINS is OK if you have to support pre 2000 machines within your domain. However, if you are native 2000 then NetBIOS (with WINS name resolution) is a redundant service not required. I like to keep things as simple as possible...
Here I am grasping at straws...does the DC that cannot browse register with DNS server? By that I mean is the &quot;Register this connection's address in DNS&quot; checked?
Can other machines browse to this DC? By either IP or FQDN?
I really hope you all ready found the answer and would like to know the fix...