strange log-on issue

Helix

the only time i seem to post here is when things are messed up lol

right, the problem we're having is as follows:

we have a windows xp laptop here, and when trying to log onto our network with our admin account, we get the following error

windows cannot connect to the domain, either because the domain controller is down or otherwise unavailable, or because your computer account was not found. please try again later. if this message continues to appear, contact your system administrator for assistance

but the domain controller is working fine, and the computer account exists. and im the system administrator lol

we were also having an issue pushing out virus scan software from our central epolicy orchestrator server to the laptop, so it seems like somethings definitely not right with the network setup. but heres the clincher, no matter how many times you try to log onto windows on our network domain with the network cable in the machine, it doesnt work. but if you take the network cable out, it DOES work about 4th time round.

to make things even more messy, we cant log onto the machine itself on the local admin account at all. its not a case of incorrect passwords or anything like that either, we know that for certain.

im fairly new to this game, so i wouldnt have the experience to know whats up, but if anyone has any ideas theyd be gladly recieved

cheers

ntlbell

If you can logon with the cable out it's just "cached credentials" it usually points to a network problem.

Have you tried a different network point? cable? can you log on from other boxes? blah blah the usuall nonsense!

Helix

yup tried the cable and its not it, as well as different network points

every other machine on the network (150ish) are working fine with no logon issues

*edit* cant log on with the cable plugged in, only when its plugged out, which makes no sense to me at all considering its the network we're logging on to

feylya

Can you remotely manage the laptop and bring up the event logs? See what's going on?

ntlbell

Helix wrote:

yup tried the cable and its not it, as well as different network points

every other machine on the network (150ish) are working fine with no logon issues

*edit* cant log on with the cable plugged in, only when its plugged out, which makes no sense to me at all considering its the network we're logging on to

It's called cached credentials, it's logging you on to the laptop via cached credentials, for this you don't need to be logged into the network.

when you plug the cable into the laptop is much activitiy on the link light of the nic?

have you a spare pcmia nic that you could test in the laptop?

also how long has it been since it was logged into the domain?

what happens when you try log on using the local machine (this computer) ? what's the error?

Helix

nope, cant get in remotely coz it wont take the login while the network cable is connected

i can get into the machine alrite, after maybe 4 attempts while the network cable is out, but the event logs arent providing much. there is mention of authentication issues, BUT having looked that up, it doesnt appear to be anything. its not coming up as an error either, just a warning, and the ms help site says that its an issue that has been solved by the time you read the warning in the event log anyway

none of it makes much sense at all

feylya

If you're a domain admin, you shouldn't need to log onto the laptop to get the event logs.

How is your NIC set up? 100/full or auto/auto?

Helix

ntlbell wrote:

It's called cached credentials, it's logging you on to the laptop via cached credentials, for this you don't need to be logged into the network.

when you plug the cable into the laptop is much activitiy on the link light of the nic?

have you a spare pcmia nic that you could test in the laptop?

ill check now

ok just the usual, nothing too crazy

once youre logged in and plug the cable in tho, you have full network access

ntlbell

Helix wrote:

ill check now

ok just the usual, nothing too crazy

once youre logged in and plug the cable in tho, you have full network access

ok, but is the machine getting an IP address from the DHCP after you plugin?

if you do an IPCONFIG/RENEW what happens?

have you tried reinstalling the nic in device manager?

some laptops have a "switch" for the nic to turn it off?

check all the simple things first.

Helix

feylya wrote:

If you're a domain admin, you shouldn't need to log onto the laptop to get the event logs.

How is your NIC set up? 100/full or auto/auto?

which event logs are you talking about? on the laptop or on the domain controller? cant get into the laptop without logging on like

i didnt set up the laptop nic, and the bloke who did isnt in, so how does one check that?

Helix

ntlbell wrote:

ok, but is the machine getting an IP address from the DHCP after you plugin?

if you do an IPCONFIG/RENEW what happens?

have you tried reinstalling the nic in device manager?

some laptops have a "switch" for the nic to turn it off?

check all the simple things first.

yeh its gettin an ip alrite, will reinstall the nic, but surely if we're getting network connectivity after logon its doing its job?

ntlbell

Helix wrote:

which event logs are you talking about? on the laptop or on the domain controller? cant get into the laptop without logging on like

i didnt set up the laptop nic, and the bloke who did isnt in, so how does one check that?

device manager click on the nic, properties advanved/flow control

feylya

I'm talking about the laptop ones. You do not need to be logged onto the laptop to read them. If you can ping the laptop from the DC, you should be able to open compmgmt.msc with your admin credentials and connect to the laptop.

Go to the network properties and check the advanced tab.

ntlbell

Helix wrote:

yeh its gettin an ip alrite, will reinstall the nic, but surely if we're getting network connectivity after logon its doing its job?

then no don't bother re-installing the nic.

ideally this is what you need to do.

get on to the laptop as a local admin, i know you said this is an issue but try sort this first

delete the machine account from AD and re-add the laptop to the domain.

should be sorted then