• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 275
  • Last Modified:

Problems with NETLOGON

We have recently started experiencing a problem with our network that was first noticed with our network drives becoming unavailable.  The problem is not, however, with network drive mappings, but with the network itself.

The following is noticed when the problem occurs (many times a day):

- The problem only seems to affect our server which is the PDC and DHCP, and acts as a file server for many internal documents.  Most of our mapped network drives are shares found on this server.

- Other mapped drives from other machines are still accessible.  

- This one affected server also runs our internal web server.  The web server does not get affected... and we can still ping this server and access files through web sharing, however:

- When we try the network browser to get to the server in question (even while on the server itself), there is the following message: "//drive_name is not accessible… The remote computer is not available".  We can see the server name, click into it and see the shares, but cannot open any of the shares.  Other computers in the network/domain remain visible and accessible

- A reboot of the server will set things back to normal (for the time being)

- A restart of the "Server" service seems to fix things

- A restart of the "Net Logon" service (which depends on the "Server" service) also seems to work.

From this we gather that this is not a drive mapping problem (we've tried the autodisconnect setting), but with the server becoming unavailable on our network/domain.

Any suggestions would be appreciated.

0
saurabhgulati
Asked:
saurabhgulati
  • 5
  • 3
1 Solution
 
Scott_WillcocksCommented:
is there any logs in the event viewer if so can you post them here so we can look at them
0
 
saurabhgulatiAuthor Commented:
hi,

Unfortunately there are no error logs in the event viewer.
We initially thought its a licencing issue but when I try to go to the licencing feature from within remote desktop, it can't resolve its own server name.

Thanks.
0
 
Scott_WillcocksCommented:
sounds like a wins problem I would check the servers network settings

ipconfig /all and see where it thinks the wins server is also check the server anbd workstation services are functioning
0
Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

 
saurabhgulatiAuthor Commented:
Scott can you please provide more info on this wins issue. I mean what could be the cause. My wins server is set to be the server's own IP address 192.168.1.2.
Also the workstations service is running.

Thanks.
0
 
Scott_WillcocksCommented:
I hope your using DHCP. Make sure dhcp option "046 WINS/NBT Node Type" is set to "0x8" This option will ensure that clients will try first to contact a WINS server, thentry to broadcast for resolution. And obviously option 044 Wins servers, specify both your wins servers.

most basic of all, I hope you don't have very restrictive access lists on your PIX. WINS runs on tcp port 42.


Does your domain controller also act as the DNS server? If this is the case, my first suggestion would be to make sure that your domain controller points to itself for DNS name resolution. Also, change the setting in DNS to "Allow Dynamic updates" and see if that works. If neither of those help, then here are some more leads:

0
 
saurabhgulatiAuthor Commented:
hi Scott,

"Does your domain controller also act as the DNS server? If this is the case, my first suggestion would be to make sure that your domain controller points to itself for DNS name resolution. Also, change the setting in DNS to "Allow Dynamic updates" and see if that works. If neither of those help, then here are some more leads:"

Yes the domain controller acts as a DNS server too. I have added the IP address of the server to its DNS as well. I am unable to find where the "Allow Dynamic updates" is?

"most basic of all, I hope you don't have very restrictive access lists on your PIX. WINS runs on tcp port 42."

No there are no such restrictions.

"I hope your using DHCP. Make sure dhcp option "046 WINS/NBT Node Type" is set to "0x8" This option will ensure that clients will try first to contact a WINS server, thentry to broadcast for resolution. And obviously option 044 Wins servers, specify both your wins servers."

Where can I view and change these settings?
0
 
Scott_WillcocksCommented:
how to enable dynamic dns updates

http://www.microsoft.com/technet/community/columns/cableguy/cg0401.mspx


check here how to change the scope options to 046 wins/nbt node type

0
 
Scott_WillcocksCommented:

oopss forgot to post the link :)

check here how to change the scope options to 046 wins/nbt node type

http://www.comptechdoc.org/os/windows/ntserverguide/ntsdhcp.html
0

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now