Re: The system cannot log you on now because the domain not avail
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
> > > >
> >
> >
> >
Re: The system cannot log you on now because the domain not avail
Edwin,
The symptoms mentioned below are correct.
I will log on as domain user and domain admin and compare the event logs.
I will post the event logs.I'm bit superised that this issue occured with
new machine that was put on the network and similar issue on every host
machine,
Many Thanks.
"Edwin vMierlo" wrote:
> 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
> > > > >
> > >
> > >
> > >
>
>
>
Re: The system cannot log you on now because the domain not avail
Hi Edwin,
This is what i captured from the event viewer
Your computer was not able to renew its address from the network (from the
DHCP Server) for the Network Card with network address 00148510768D. The
following error occurred:
The semaphore timeout period has expired. . Your computer will continue to
try and obtain an address on its own from the network address (DHCP) server.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
This error message is on 5 different machines that i tried.
i cleared the system event and restarted the machine.It was 20-25 seconds
and then it logged on.So i logged on as admin and check the system event and
it was the same event.Seems that the problem is with DHCP.
"MCP200" wrote:
> Edwin,
> The symptoms mentioned below are correct.
> I will log on as domain user and domain admin and compare the event logs.
> I will post the event logs.I'm bit superised that this issue occured with
> new machine that was put on the network and similar issue on every host
> machine,
>
> Many Thanks.
>
> "Edwin vMierlo" wrote:
>
> > 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
> > > > > >
> > > >
> > > >
> > > >
> >
> >
> >
Re: The system cannot log you on now because the domain not avail
Ok, so now I would go and configure 1 port on your switch to "portfast"
For information on how to do this on Cisco:
http://www.cisco.com/warp/public/473/12.html
and then test again
"MCP200" <MCP200@discussions.microsoft.com> wrote in message
news:5CB052B5-4336-45D8-B727-DB739FB04618@microsoft.com...
> Hi Edwin,
> This is what i captured from the event viewer
>
> Your computer was not able to renew its address from the network (from the
> DHCP Server) for the Network Card with network address 00148510768D. The
> following error occurred:
> The semaphore timeout period has expired. . Your computer will continue to
> try and obtain an address on its own from the network address (DHCP)
server.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
>
> This error message is on 5 different machines that i tried.
> i cleared the system event and restarted the machine.It was 20-25 seconds
> and then it logged on.So i logged on as admin and check the system event
and
> it was the same event.Seems that the problem is with DHCP.
>
>
>
> "MCP200" wrote:
>
> > Edwin,
> > The symptoms mentioned below are correct.
> > I will log on as domain user and domain admin and compare the event
logs.
> > I will post the event logs.I'm bit superised that this issue occured
with
> > new machine that was put on the network and similar issue on every host
> > machine,
> >
> > Many Thanks.
> >
> > "Edwin vMierlo" wrote:
> >
> > > 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
> > > > > > >
> > > > >
> > > > >
> > > > >
> > >
> > >
> > >
Re: The system cannot log you on now because the domain not avail
I'll test tommorrow and i'll let you know.
Many Thanks.
"Edwin vMierlo" wrote:
> Ok, so now I would go and configure 1 port on your switch to "portfast"
>
> For information on how to do this on Cisco:
> http://www.cisco.com/warp/public/473/12.html
>
> and then test again
>
>
>
> "MCP200" <MCP200@discussions.microsoft.com> wrote in message
> news:5CB052B5-4336-45D8-B727-DB739FB04618@microsoft.com...
> > Hi Edwin,
> > This is what i captured from the event viewer
> >
> > Your computer was not able to renew its address from the network (from the
> > DHCP Server) for the Network Card with network address 00148510768D. The
> > following error occurred:
> > The semaphore timeout period has expired. . Your computer will continue to
> > try and obtain an address on its own from the network address (DHCP)
> server.
> >
> > For more information, see Help and Support Center at
> > http://go.microsoft.com/fwlink/events.asp.
> >
> >
> > This error message is on 5 different machines that i tried.
> > i cleared the system event and restarted the machine.It was 20-25 seconds
> > and then it logged on.So i logged on as admin and check the system event
> and
> > it was the same event.Seems that the problem is with DHCP.
> >
> >
> >
> > "MCP200" wrote:
> >
> > > Edwin,
> > > The symptoms mentioned below are correct.
> > > I will log on as domain user and domain admin and compare the event
> logs.
> > > I will post the event logs.I'm bit superised that this issue occured
> with
> > > new machine that was put on the network and similar issue on every host
> > > machine,
> > >
> > > Many Thanks.
> > >
> > > "Edwin vMierlo" wrote:
> > >
> > > > 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
> > > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > >
> > > >
> > > >
>
>
>
Re: The system cannot log you on now because the domain not avail
Edwin,
Sorry for getting back to you late.
What i done was switch off the two cisco switches and connected another for
testing reasons and it still gave me the same symptom :(
This time when i checked the system event.
It gave me the following "
Event ID 1010 :
The DHCP service encountered the following error while cleaning up the
database:
An error occurred while accessing the DHCP database. Look at the
DHCP server event log for more information on this error.
and..
Event ID 1016 :
The DHCP service encountered the following error when backing up the
database:
An error occurred while accessing the DHCP database. Look at the
DHCP server event log for more information on this error.
and...
Event ID 1014:
he following problem occurred with the Jet database -1032: Jet database
read or write operations failed. If the computer or database has just been
upgraded, then this message can be safely ignored. If this message appears
frequently, either there is not enough disk space to complete the operation
or the database or backup database may be corrupt. To correct this problem,
either free additional space on your hard disk or restore the database.
After you restore the database, ensure that conflict detection is enabled in
DHCP server properties. For information about restoring the database, see
Help and Support Center. Additional Debug Information: JetBackup"
I don't think the issue is releated to it.
I'm thinking of disabling the DHCP on the server and enable it on the router
and see if it's same issue?i feel lost now
"MCP200" wrote:
> I'll test tommorrow and i'll let you know.
>
> Many Thanks.
>
>
> "Edwin vMierlo" wrote:
>
> > Ok, so now I would go and configure 1 port on your switch to "portfast"
> >
> > For information on how to do this on Cisco:
> > http://www.cisco.com/warp/public/473/12.html
> >
> > and then test again
> >
> >
> >
> > "MCP200" <MCP200@discussions.microsoft.com> wrote in message
> > news:5CB052B5-4336-45D8-B727-DB739FB04618@microsoft.com...
> > > Hi Edwin,
> > > This is what i captured from the event viewer
> > >
> > > Your computer was not able to renew its address from the network (from the
> > > DHCP Server) for the Network Card with network address 00148510768D. The
> > > following error occurred:
> > > The semaphore timeout period has expired. . Your computer will continue to
> > > try and obtain an address on its own from the network address (DHCP)
> > server.
> > >
> > > For more information, see Help and Support Center at
> > > http://go.microsoft.com/fwlink/events.asp.
> > >
> > >
> > > This error message is on 5 different machines that i tried.
> > > i cleared the system event and restarted the machine.It was 20-25 seconds
> > > and then it logged on.So i logged on as admin and check the system event
> > and
> > > it was the same event.Seems that the problem is with DHCP.
> > >
> > >
> > >
> > > "MCP200" wrote:
> > >
> > > > Edwin,
> > > > The symptoms mentioned below are correct.
> > > > I will log on as domain user and domain admin and compare the event
> > logs.
> > > > I will post the event logs.I'm bit superised that this issue occured
> > with
> > > > new machine that was put on the network and similar issue on every host
> > > > machine,
> > > >
> > > > Many Thanks.
> > > >
> > > > "Edwin vMierlo" wrote:
> > > >
> > > > > 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
> > > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > >
> > > > >
> > > > >
> >
> >
> >
Re: The system cannot log you on now because the domain not avail
The new switch that i replaced has no STP ability and it's not cisco switch.
"MCP200" wrote:
> I'll test tommorrow and i'll let you know.
>
> Many Thanks.
>
>
> "Edwin vMierlo" wrote:
>
> > Ok, so now I would go and configure 1 port on your switch to "portfast"
> >
> > For information on how to do this on Cisco:
> > http://www.cisco.com/warp/public/473/12.html
> >
> > and then test again
> >
> >
> >
> > "MCP200" <MCP200@discussions.microsoft.com> wrote in message
> > news:5CB052B5-4336-45D8-B727-DB739FB04618@microsoft.com...
> > > Hi Edwin,
> > > This is what i captured from the event viewer
> > >
> > > Your computer was not able to renew its address from the network (from the
> > > DHCP Server) for the Network Card with network address 00148510768D. The
> > > following error occurred:
> > > The semaphore timeout period has expired. . Your computer will continue to
> > > try and obtain an address on its own from the network address (DHCP)
> > server.
> > >
> > > For more information, see Help and Support Center at
> > > http://go.microsoft.com/fwlink/events.asp.
> > >
> > >
> > > This error message is on 5 different machines that i tried.
> > > i cleared the system event and restarted the machine.It was 20-25 seconds
> > > and then it logged on.So i logged on as admin and check the system event
> > and
> > > it was the same event.Seems that the problem is with DHCP.
> > >
> > >
> > >
> > > "MCP200" wrote:
> > >
> > > > Edwin,
> > > > The symptoms mentioned below are correct.
> > > > I will log on as domain user and domain admin and compare the event
> > logs.
> > > > I will post the event logs.I'm bit superised that this issue occured
> > with
> > > > new machine that was put on the network and similar issue on every host
> > > > machine,
> > > >
> > > > Many Thanks.
> > > >
> > > > "Edwin vMierlo" wrote:
> > > >
> > > > > 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
> > > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > >
> > > > >
> > > > >
> >
> >
> >
Re: The system cannot log you on now because the domain not avail
Have a look at this
https://www.microsoft.com/technet/pr....mspx?mfr=true
"MCP200" <MCP200@discussions.microsoft.com> wrote in message
news:F321E288-63B7-4017-9D49-2925C055123A@microsoft.com...
> Edwin,
> Sorry for getting back to you late.
> What i done was switch off the two cisco switches and connected another
for
> testing reasons and it still gave me the same symptom :(
>
> This time when i checked the system event.
> It gave me the following "
>
>
> Event ID 1010 :
>
> The DHCP service encountered the following error while cleaning up the
> database:
> An error occurred while accessing the DHCP database. Look at the
> DHCP server event log for more information on this error.
>
> and..
>
> Event ID 1016 :
>
> The DHCP service encountered the following error when backing up the
> database:
> An error occurred while accessing the DHCP database. Look at the
> DHCP server event log for more information on this error.
>
> and...
>
> Event ID 1014:
>
> he following problem occurred with the Jet database -1032: Jet database
> read or write operations failed. If the computer or database has just
been
> upgraded, then this message can be safely ignored. If this message
appears
> frequently, either there is not enough disk space to complete the
operation
> or the database or backup database may be corrupt. To correct this
problem,
> either free additional space on your hard disk or restore the database.
> After you restore the database, ensure that conflict detection is enabled
in
> DHCP server properties. For information about restoring the database, see
> Help and Support Center. Additional Debug Information: JetBackup"
>
> I don't think the issue is releated to it.
>
> I'm thinking of disabling the DHCP on the server and enable it on the
router
> and see if it's same issue?i feel lost now
>
>
>
> "MCP200" wrote:
>
> > I'll test tommorrow and i'll let you know.
> >
> > Many Thanks.
> >
> >
> > "Edwin vMierlo" wrote:
> >
> > > Ok, so now I would go and configure 1 port on your switch to
"portfast"
> > >
> > > For information on how to do this on Cisco:
> > > http://www.cisco.com/warp/public/473/12.html
> > >
> > > and then test again
> > >
> > >
> > >
> > > "MCP200" <MCP200@discussions.microsoft.com> wrote in message
> > > news:5CB052B5-4336-45D8-B727-DB739FB04618@microsoft.com...
> > > > Hi Edwin,
> > > > This is what i captured from the event viewer
> > > >
> > > > Your computer was not able to renew its address from the network
(from the
> > > > DHCP Server) for the Network Card with network address 00148510768D.
The
> > > > following error occurred:
> > > > The semaphore timeout period has expired. . Your computer will
continue to
> > > > try and obtain an address on its own from the network address (DHCP)
> > > server.
> > > >
> > > > For more information, see Help and Support Center at
> > > > http://go.microsoft.com/fwlink/events.asp.
> > > >
> > > >
> > > > This error message is on 5 different machines that i tried.
> > > > i cleared the system event and restarted the machine.It was 20-25
seconds
> > > > and then it logged on.So i logged on as admin and check the system
event
> > > and
> > > > it was the same event.Seems that the problem is with DHCP.
> > > >
> > > >
> > > >
> > > > "MCP200" wrote:
> > > >
> > > > > Edwin,
> > > > > The symptoms mentioned below are correct.
> > > > > I will log on as domain user and domain admin and compare the
event
> > > logs.
> > > > > I will post the event logs.I'm bit superised that this issue
occured
> > > with
> > > > > new machine that was put on the network and similar issue on every
host
> > > > > machine,
> > > > >
> > > > > Many Thanks.
> > > > >
> > > > > "Edwin vMierlo" wrote:
> > > > >
> > > > > > 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
> > > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > >
> > >
> > >
