XP client joining domain: "the system call level is not correct"

[nsherin]

Hiya,

 

Wonder if anyone can advise here?

 

I'm having a problem with a couple of XP clients one our network. Both are unable to access any network resources - despite having correct TCP/IP settings as assigned by our DHCP server. However, they are able to ping machines on the nework by hostname.

 

I've ruled out network card issues - tried both on-board and PCI network adapters. I then tried to take one of the machines off our domain, which went fine. However, when I went to re-join the PC to the domain, I get the following error:

 

"The system call level is not correct"

 

The other machine with a similar issue, which I have not yet removed from our domain brings up a The domain PHONEIx (being our domain name) is not available".

 

Any ideas/solutions would be much appreciated!

 

Cheers,

Neil

[sparkeh]

Are both machines going through the same switch?

[nsherin]

Are both machines going through the same switch?

 

Yes they are. all other clients on the same switch are running fine.

[Guest TheLibrarian]

Ensure time, date and timezone of the systems closely matches the domain.

 

Have you disabled any services?

[nsherin]

Try renaming the machine and then adding to the domain.

 

Thanks - will give that a go.

[nsherin]

Ensure time, date and timezone of the systems closely matches the domain.

 

Have you disabled any services?

 

The time etc. looks to be fine with the machines. No services have been disabled - in fact their configuration has been kept intact by HDGuard (similar product to Deep Freeze).

[sparkeh]

Yes they are. all other clients on the same switch are running fine.

 

Sure but a failing switch doesn't always fall over in one go. Had something similar myself where a few ports failed at a time then boom the whole lot.

 

From a troubleshooting point of view I would be concerned that the machine already on the domain can't access network resources as this indicates network issues rather then joining domain issues?

[nsherin]

Sure but a failing switch doesn't always fall over in one go. Had something similar myself where a few ports failed at a time then boom the whole lot.

 

From a troubleshooting point of view I would be concerned that the machine already on the domain can't access network resources as this indicates network issues rather then joining domain issues?

 

Thanks - I'll try another switch tomorrow as well. Could be a dodgy port that is causing the issue. It is very strange that the machien can ping other machines by hostname, but not access resources or the web.