user logon

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a network of more than 150 users with win2k clients and win2k3 server.
But now for last few days some users can connect to all other systems other
than they are using.if we change the domain extention at the networkwork
identification part,they are able to login.after 2-3 days the same will
happen again. is there any permanent solution for this?
--
 
Jomon Mathew said:
I have a network of more than 150 users with win2k clients and win2k3
server.
But now for last few days some users can connect to all other systems
other
than they are using.if we change the domain extention at the networkwork
identification part,they are able to login.after 2-3 days the same will
happen again. is there any permanent solution for this?
Click to expand...


I cannot be certain the following is YOUR issue, but this is typical
behavior when the admin has tried to set a COMBINATION of
both Internal AND External DNS Servers on each clients NIC->IP
properties.

You must use STRICTLY the INTERNAL DNS in those settings.

Run DCDiag on every DC and check out the following general guide
to DNS with AD:


--
DNS for AD
1) Dynamic for the zone supporting AD
2) All internal DNS clients NIC\IP properties must specify SOLELY
that internal, dynamic DNS server (set.)
3) DCs and even DNS servers are DNS clients too -- see #2
4) If you have more than one Domain, every DNS server must
be able to resolve ALL domains (either directly or indirectly)

netdiag /fix

....or maybe:

dcdiag /fix

(Win2003 can do this from Support tools):
nltest /dsregdns /server:DC-ServerNameGoesHere
http://support.microsoft.com/kb/q260371/

Ensure that DNS zones/domains are fully replicated to all DNS
servers for that (internal) zone/domain.

Also useful may be running DCDiag on each DC, sending the
output to a text file, and searching for FAIL, ERROR, WARN.

Single Label domain zone names are a problem Google:
[ "SINGLE LABEL" domain names DNS 2000 | 2003 microsoft: ]
 
Back
Top