The system cannot log you on now because the domain not available

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

Can someone assist please?
What i tried doing on every machine,is set the nic to 100mb full duplex.
Now it doesn't come up with The system cannot log you on now because the
domain <DOMAIN_NAME> it sits there for 20 seconds and then it starts to apply
personal settings.]

can someone advise me please?


"MCP200" 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

so, you set your NIC to 100MB and the symptom is gone

except there is a 20 second delay after logon and "Apply Personal Settings"

just not sure what your question is, so let me ask some :

is your problem the 20 second delay ?
does it occur after a boot ?
does it occur after a logout (no boot) ?


"MCP200" <(E-Mail Removed)> wrote in message
news:1E679D44-AB68-49F8-8C88-(E-Mail Removed)...
> Can someone assist please?
> What i tried doing on every machine,is set the nic to 100mb full duplex.
> Now it doesn't come up with The system cannot log you on now because the
> domain <DOMAIN_NAME> it sits there for 20 seconds and then it starts to
apply
> personal settings.]
>
> can someone advise me please?
>
>
> "MCP200" 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

"Edwin vMierlo" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> so, you set your NIC to 100MB and the symptom is gone
>
> except there is a 20 second delay after logon and "Apply Personal
> Settings"
>
> just not sure what your question is, so let me ask some :
>
> is your problem the 20 second delay ?
> does it occur after a boot ?
> does it occur after a logout (no boot) ?
>
>
> "MCP200" <(E-Mail Removed)> wrote in message
> news:1E679D44-AB68-49F8-8C88-(E-Mail Removed)...
>> Can someone assist please?
>> What i tried doing on every machine,is set the nic to 100mb full duplex.
>> Now it doesn't come up with The system cannot log you on now because the
>> domain <DOMAIN_NAME> it sits there for 20 seconds and then it starts to
> apply
>> personal settings.]
>>
>> can someone advise me please?
>>
>>
>> "MCP200" 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
>

Do your DNS settings point to the internal DNS (AD) server *only*? You
shouldn't have any external DNS entries on any of your internal clients.

Edwin I was getting the error message every time I starup the machine,
however the message no longer appears since enabling 100mb full duplex on the
network card, but now it sits there for 20-25 seconds and then it starts
applying personal settings instantely.Seems that when it starts up it doesn't
get the ip address from the dhcp server fast enough?

If I log off and log on again, it logs me on straight away. This is occurs
only when you first starup your computer.

I wanna know why there is such delay at startup?

Many Thanks


"Edwin vMierlo" wrote:

> so, you set your NIC to 100MB and the symptom is gone
>
> except there is a 20 second delay after logon and "Apply Personal Settings"
>
> just not sure what your question is, so let me ask some :
>
> is your problem the 20 second delay ?
> does it occur after a boot ?
> does it occur after a logout (no boot) ?
>
>
> "MCP200" <(E-Mail Removed)> wrote in message
> news:1E679D44-AB68-49F8-8C88-(E-Mail Removed)...
> > Can someone assist please?
> > What i tried doing on every machine,is set the nic to 100mb full duplex.
> > Now it doesn't come up with The system cannot log you on now because the
> > domain <DOMAIN_NAME> it sits there for 20 seconds and then it starts to
> apply
> > personal settings.]
> >
> > can someone advise me please?
> >
> >
> > "MCP200" 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
>
>
>

Steve,
The internal machine have dns settings which point to the server box.
Also the dns server forwards the query to the router which it provides the
ISP's primay and secondary dns.

Thank you

"steve" wrote:

> "Edwin vMierlo" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > so, you set your NIC to 100MB and the symptom is gone
> >
> > except there is a 20 second delay after logon and "Apply Personal
> > Settings"
> >
> > just not sure what your question is, so let me ask some :
> >
> > is your problem the 20 second delay ?
> > does it occur after a boot ?
> > does it occur after a logout (no boot) ?
> >
> >
> > "MCP200" <(E-Mail Removed)> wrote in message
> > news:1E679D44-AB68-49F8-8C88-(E-Mail Removed)...
> >> Can someone assist please?
> >> What i tried doing on every machine,is set the nic to 100mb full duplex.
> >> Now it doesn't come up with The system cannot log you on now because the
> >> domain <DOMAIN_NAME> it sits there for 20 seconds and then it starts to
> > apply
> >> personal settings.]
> >>
> >> can someone advise me please?
> >>
> >>
> >> "MCP200" 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
> >
>
> Do your DNS settings point to the internal DNS (AD) server *only*? You
> shouldn't have any external DNS entries on any of your internal clients.
>
>
>

"getting an IP" from the network, and time it takes to get it, might vary
depending on your network configuration.
Example: if you are using STP on Cisco switches, the cisco switch might (not
always, just might) take up to 30 seconds to (try to) detect loops in the
topology. These checks happen on all ports, unless you use the "portfast"
command. (this detection of loops in the topology is when layer 1 and 2 are
initializing and to establish link, more than likely at boot time !)

if you use cisco, have a look here
http://www.cisco.com/warp/public/473/12.html

Obviously this is only one factor... there could be many more.


"MCP200" <(E-Mail Removed)> wrote in message
news:0D0A62D0-0088-4DD3-963B-(E-Mail Removed)...
> Edwin I was getting the error message every time I starup the machine,
> however the message no longer appears since enabling 100mb full duplex on
the
> network card, but now it sits there for 20-25 seconds and then it starts
> applying personal settings instantely.Seems that when it starts up it
doesn't
> get the ip address from the dhcp server fast enough?
>
> If I log off and log on again, it logs me on straight away. This is occurs
> only when you first starup your computer.
>
> I wanna know why there is such delay at startup?
>
> Many Thanks
>
>
> "Edwin vMierlo" wrote:
>
> > so, you set your NIC to 100MB and the symptom is gone
> >
> > except there is a 20 second delay after logon and "Apply Personal
Settings"
> >
> > just not sure what your question is, so let me ask some :
> >
> > is your problem the 20 second delay ?
> > does it occur after a boot ?
> > does it occur after a logout (no boot) ?
> >
> >
> > "MCP200" <(E-Mail Removed)> wrote in message
> > news:1E679D44-AB68-49F8-8C88-(E-Mail Removed)...
> > > Can someone assist please?
> > > What i tried doing on every machine,is set the nic to 100mb full
duplex.
> > > Now it doesn't come up with The system cannot log you on now because
the
> > > domain <DOMAIN_NAME> it sits there for 20 seconds and then it starts
to
> > apply
> > > personal settings.]
> > >
> > > can someone advise me please?
> > >
> > >
> > > "MCP200" 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
> >
> >
> >

Thanks for the reply,
I have two 2948 Cisco switches installed, but they are not configured.
It's been installed as it is. So there is no way of management unless I
configure them.


The old server was connected to the same switches and would apply personal
settings after entering username and password but would take long time
because of dns issue.Now with new server once entering the userid and
password it waits for 20-25 seconds and then it starts to apply personal
settings very quick.At first i was getting the domain is unvailable but
that's rectified since enabling 100 MB Full Duplex.

Do you suggest to configure the switches?

Sorry for being a pain

Thanks

However with this server once you bootup and enter the username and
password ,it thinks for 20-25 seconds and then it starts to apply peronsal
setting and your in windowes instantely.



"Edwin vMierlo" wrote:

>
>
> "getting an IP" from the network, and time it takes to get it, might vary
> depending on your network configuration.
> Example: if you are using STP on Cisco switches, the cisco switch might (not
> always, just might) take up to 30 seconds to (try to) detect loops in the
> topology. These checks happen on all ports, unless you use the "portfast"
> command. (this detection of loops in the topology is when layer 1 and 2 are
> initializing and to establish link, more than likely at boot time !)
>
> if you use cisco, have a look here
> http://www.cisco.com/warp/public/473/12.html
>
> Obviously this is only one factor... there could be many more.
>
>
> "MCP200" <(E-Mail Removed)> wrote in message
> news:0D0A62D0-0088-4DD3-963B-(E-Mail Removed)...
> > Edwin I was getting the error message every time I starup the machine,
> > however the message no longer appears since enabling 100mb full duplex on
> the
> > network card, but now it sits there for 20-25 seconds and then it starts
> > applying personal settings instantely.Seems that when it starts up it
> doesn't
> > get the ip address from the dhcp server fast enough?
> >
> > If I log off and log on again, it logs me on straight away. This is occurs
> > only when you first starup your computer.
> >
> > I wanna know why there is such delay at startup?
> >
> > Many Thanks
> >
> >
> > "Edwin vMierlo" wrote:
> >
> > > so, you set your NIC to 100MB and the symptom is gone
> > >
> > > except there is a 20 second delay after logon and "Apply Personal
> Settings"
> > >
> > > just not sure what your question is, so let me ask some :
> > >
> > > is your problem the 20 second delay ?
> > > does it occur after a boot ?
> > > does it occur after a logout (no boot) ?
> > >
> > >
> > > "MCP200" <(E-Mail Removed)> wrote in message
> > > news:1E679D44-AB68-49F8-8C88-(E-Mail Removed)...
> > > > Can someone assist please?
> > > > What i tried doing on every machine,is set the nic to 100mb full
> duplex.
> > > > Now it doesn't come up with The system cannot log you on now because
> the
> > > > domain <DOMAIN_NAME> it sits there for 20 seconds and then it starts
> to
> > > apply
> > > > personal settings.]
> > > >
> > > > can someone advise me please?
> > > >
> > > >
> > > > "MCP200" 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
> > >
> > >
> > >
>
>
>

no, not at this point

a quick test:
- boot the machine
- wait 5 minutes (at this point all network should be up and done)
- then login

does it still "sit there" for 20-25 seconds ?



"MCP200" <(E-Mail Removed)> wrote in message
news:A22CAAB2-CC30-412C-B9D5-(E-Mail Removed)...
> Thanks for the reply,
> I have two 2948 Cisco switches installed, but they are not configured.
> It's been installed as it is. So there is no way of management unless I
> configure them.
>
>
> The old server was connected to the same switches and would apply
personal
> settings after entering username and password but would take long time
> because of dns issue.Now with new server once entering the userid and
> password it waits for 20-25 seconds and then it starts to apply personal
> settings very quick.At first i was getting the domain is unvailable but
> that's rectified since enabling 100 MB Full Duplex.
>
> Do you suggest to configure the switches?
>
> Sorry for being a pain
>
> Thanks
>
> However with this server once you bootup and enter the username and
> password ,it thinks for 20-25 seconds and then it starts to apply peronsal
> setting and your in windowes instantely.
>
>
>
> "Edwin vMierlo" wrote:
>
> >
> >
> > "getting an IP" from the network, and time it takes to get it, might
vary
> > depending on your network configuration.
> > Example: if you are using STP on Cisco switches, the cisco switch might
(not
> > always, just might) take up to 30 seconds to (try to) detect loops in
the
> > topology. These checks happen on all ports, unless you use the
"portfast"
> > command. (this detection of loops in the topology is when layer 1 and 2
are
> > initializing and to establish link, more than likely at boot time !)
> >
> > if you use cisco, have a look here
> > http://www.cisco.com/warp/public/473/12.html
> >
> > Obviously this is only one factor... there could be many more.
> >
> >
> > "MCP200" <(E-Mail Removed)> wrote in message
> > news:0D0A62D0-0088-4DD3-963B-(E-Mail Removed)...
> > > Edwin I was getting the error message every time I starup the machine,
> > > however the message no longer appears since enabling 100mb full duplex
on
> > the
> > > network card, but now it sits there for 20-25 seconds and then it
starts
> > > applying personal settings instantely.Seems that when it starts up it
> > doesn't
> > > get the ip address from the dhcp server fast enough?
> > >
> > > If I log off and log on again, it logs me on straight away. This is
occurs
> > > only when you first starup your computer.
> > >
> > > I wanna know why there is such delay at startup?
> > >
> > > Many Thanks
> > >
> > >
> > > "Edwin vMierlo" wrote:
> > >
> > > > so, you set your NIC to 100MB and the symptom is gone
> > > >
> > > > except there is a 20 second delay after logon and "Apply Personal
> > Settings"
> > > >
> > > > just not sure what your question is, so let me ask some :
> > > >
> > > > is your problem the 20 second delay ?
> > > > does it occur after a boot ?
> > > > does it occur after a logout (no boot) ?
> > > >
> > > >
> > > > "MCP200" <(E-Mail Removed)> wrote in message
> > > > news:1E679D44-AB68-49F8-8C88-(E-Mail Removed)...
> > > > > Can someone assist please?
> > > > > What i tried doing on every machine,is set the nic to 100mb full
> > duplex.
> > > > > Now it doesn't come up with The system cannot log you on now
because
> > the
> > > > > domain <DOMAIN_NAME> it sits there for 20 seconds and then it
starts
> > to
> > > > apply
> > > > > personal settings.]
> > > > >
> > > > > can someone advise me please?
> > > > >
> > > > >
> > > > > "MCP200" 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
> > > >
> > > >
> > > >
> >
> >
> >

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\Depend OnService

add ProtectedStorage to the bottom of the list of services and reboot.

HTH




MCP200 <(E-Mail Removed)> 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

(E-Mail Removed)