Windows Forum

Ask something
Discussion Locked

Network Neighborhood

0 helpful
14 replies

by pbrs

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am getting an error only on some systems in our network when trying to access the backupserver through network neighborhood. The error is "\\backupserver is not accessible
The computer or sharename could not be found. Make sure you typed it correctly, and try again."

But when I am mapping the server with the Ipaddress of the server,then I am able to access the server.And it will lost again when I restart the machine.
The backupserver is the BDC,and there is no problem accessing the PDC.I am running microsoft proxyserver on the same backupserver with two NIC's.

on the PDC's event viwer I am receiving this error many times,The error is
"No Windows NT Domain Controller is available for domain compaq. (This event is expected andcan be ignored when booting with the 'No Net' Hardware Profile.) The following error occurred:
There are currently no logon servers available to service the logon request.

Is the error in the PDC related to the problem in BDC or it is some other problem? I am not able to figure out the problem in accessing with the server name "backupserver" through network neighborhood on some machines.
I tried removing and configuring the tcp/ip and ethernet drivers.But nothing worked.

14 replies

by gigelul

Hi,
Your questions require to clarify some aspects:
- the systems which can't access "backupserver" have the same problems with other network resources/shares? If, yes, you must reauthenticate this workstation in domain.
- NetLogon service run onboth PDC and BDC? Check in control panel\services and set to automatic and start it.
- This error: "No Windows NT Domain Controller is available for domain compaq...", have details about which system generate it? And you defined a custom hardware profile for this system? Try with default\original hardware profile. Check in control panel\devices.
- Try from Server Manager selecting the BDC a manual "synchronize with primary domain controller" and check in event viewer if its done.
Answer to this questions, in a comments, and I will try to give you more help.

by gigelul

Your Domain Name is "COMPAQ"? If not, you have a computer or more, configured to logon to "COMPAQ" domain which of course don't exist. Change logon domain name for these computer/s.

by vh_s

Usually this problem is related to application of service packs.

It could come that after working fine, some (major) modifications on configuration were made to one of the servers. Service Pack requires that you would re-apply after modification were made.

I would suggest you to re-apply the SP you used for both servers. To my experience, these kind of error would directly disappear.

vh_s

by joseph moore

I agree with Answer2. This should be solved by using a WINS server. WINS records the IP addresses and machine names of all configured WINS clients.
Then, when someone sends out a discover packet for \\BACKUPSERVER, the WINS server answers the packet, sending the client the IP address of the machine.
Name resolution. This is what WINS does.
So, if you don't have a WINS server, set one up. Then configure these troublesome clients to use the WINS server.
That should take care of it.

by m.r.

The problem is in the multihomed BDC running Proxy. There are numerous articles on multihomed systems in relation to WINS, domain controlers, network browsers/browsing, dynamic DNS, you name it. In general it's not recommended, kind of contradictory. If WINS is in use, try adding a static entry. You could also use LMHOSTS but that's not practical. If Dynamic DNS do the same. You may want to have this server not be a backup browser. This is set in the REG - see MS KB. Check your Bindingson the Proxy. The outside NIC shouldn't have any of the MS networking bound to it. It should only be able to reach the Domain from the inside NIC. Multihomed is the key word to search on.

by pbrs

Hi All,
Thank you for the interest shown in answering my question. I have solved the problem. The mistake I have done is I put the network cable to the other NIC. Because of this some of the systems are unable to resolve the name backupserver to the ipaddress.
Once again thank you all for the interest shown.
Bharat

by pbrs

I finally could able to figure out the problem.Thank you all for the interest shown in answering my question.

This discussion is closed to new replies.