OK, so we have more info now, which actually changes the symptom description
a bit.
Just to summarise here:
- boot computer
- logon immediately after boot with "normal domain user" will cause 20-25
seconds of delay
- logon immediately after boot with "domain administrator" will NOT cause
20-25 seconds of delay
- logon after 30 seconds wait after boot with "normal domain user" will NOT
cause 20-25 seconds of delay
do you agree with the (new) symptom description ?
(I don't think this is caused by your network switches, likely be in the
host machine.)
any different system event messages if you compare a failed "domain user"
logon with a sucsesful "administrator" logon ?
list them as :
1) failed logon with normal user
-- log error 1
-- log error 2
2) sucsesful logon with admin
-- log error A
-- log error B
Rgds,
Edwin.
"MCP200" <MCP200@discussions.microsoft.com> wrote in message
news:E7A2D3C9-EABB-49E2-8838-020447E52C09@microsoft.com...
> Edwin ,
> It hasn't fixed the problem :(
> I even confiured a port switch as full duplex and didn't fix the problem.
> don't know were to start from now.
>
> This issue does not occur when logging with administrator account after
> bootup.
>
>
> "Edwin vMierlo" wrote:
>
> > "I have installed the patch that has been mentioned for the DHCP"
> >
> > did it make a difference ? fixed ?
> >
> >
> >
> >
> > "MCP200" <MCP200@discussions.microsoft.com> wrote in message
> > news:4C1386B8-20C7-4C22-AFF2-95FF66574CE3@microsoft.com...
> > > Hi guys,
> > > I have checked the system event viewer.I have the following error
messages
> > > for server
> > >
> > >
> > > The server could not bind to the transport
> > > \Device\NetBT_Tcpip_{92922F1B-B28D-4F4E-8C36-960107B1B1E7}.
> > >
> > > For more information, see Help and Support Center at
> > > http://go.microsoft.com/fwlink/events.asp.
> > >
> > >
> > > and for Netlogon
> > >
> > >
> > > The dynamic deletion of the DNS record
'ForestDnsZones.shaps.nsw.edu.au.
> > 600
> > > IN A 192.168.168.254' failed on the following DNS server:
> > >
> > > DNS server IP address: <UNAVAILABLE>
> > > Returned Response Code (RCODE): 0
> > > Returned Status Code: 0
> > >
> > > USER ACTION
> > > To prevent remote computers from connecting unnecessarily to the
domain
> > > controller, delete the record manually or troubleshoot the failure to
> > > dynamically delete the record. To learn more about debugging DNS, see
Help
> > > and Support Center.
> > >
> > > ADDITIONAL DATA
> > > Error Value: A socket operation was attempted to an unreachable host.
> > >
> > > For more information, see Help and Support Center at
> > > http://go.microsoft.com/fwlink/events.asp.
> > >
> > >
> > > I have run the command DCDiag.exe and it showed that everything has
> > passed.
> > > I also ran the command nltest.exe /dsregdns .
> > >
> > > I have installed the patch that has been mentioned for the DHCP.
> > >
> > >
> > >
> > > "harrykrishna.nospam@online.ie" wrote:
> > >
> > > > I know the following is kind of specific but it may apply to you
> > > > anyways if you are running Windows 2000 SP4.
> > > >
> > > > Did this behaviour start happening after you installed KB914388?
> > > >
> > > > Do you have "The DHCP Client service hung on starting" errors in
your
> > > > event log?
> > > >
> > > > If so, try the following:
> > > >
> > > > Use Regedit32 and go to
> > > > HKLM\System\CurrentControlSet\Services\DHCP\DependOnService
> > > >
> > > > add ProtectedStorage to the bottom of the list of services and
reboot.
> > > >
> > > > HTH
> > > >
> > > >
> > > >
> > > >
> > > > MCP200 <MCP200@discussions.microsoft.com> wrote:
> > > >
> > > > >Hi Everyone,
> > > > >I get The system cannot log you on now because the domain
<DOMAIN_NAME>
> > is
> > > > >not available when i try to log onto the the domain
> > > > >
> > > > >When I get to the stage of entering the username and password it
waits
> > for
> > > > >10 seconds and then I get an error message saying that the domain
is
> > > > >unavailable, however if I wait 20-25 seconds before logging on, it
logs
> > me on
> > > > >straight away
> > > > >
> > > > >It only occurs when you first boot up the machine ,and If I enter
the
> > > > >username and password I get the domain is unavailable but it's
working
> > fine
> > > > >the 2nd attempt and logs me onto the domain very quick
> > > > >
> > > > >I don't know if its dns issue ,but it sounds that the machine isn't
> > getting
> > > > >the ip address from the DHCP server quick enough. What's your
opinion
> > please?
> > > > >
> > > > >Is this releated to Cached Logon Count problem?
> > > > >
> > > > >Thanks
> > > >
> > > >
> > > > Ha®®y
> > > >
> > > > HarryKrishna.nospam@online.ie
> > > >
> >
> >
> >


Reply With Quote

Bookmarks