can not see domain controller & windows services can not start

[Guest]

Several months, all machines (340) has been changed with lenovo desktops and
upgraded the winxp sp1 to winxp sp2... lots of this machines can not be
connect to the domain controller and the principal windows services can not
start (ej. Computer Browser, Server, DHCP Client, Windows Audio, Workstation
and others) i found in lenovo the same error and with the same network card...

http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-58745

We test modify the register entry... and don't work
We test in some machines ip address static the problem is fixed.

We don't know if the problem is in the machines, dhcp or dns.

Please somebody can help me

 

[Robert L [MVP - Networking]]

I would check the DNS first. Any error if using nslookup command?

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
Several months, all machines (340) has been changed with lenovo desktops and
upgraded the winxp sp1 to winxp sp2... lots of this machines can not be
connect to the domain controller and the principal windows services can not
start (ej. Computer Browser, Server, DHCP Client, Windows Audio, Workstation
and others) i found in lenovo the same error and with the same network card...

http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-58745

We test modify the register entry... and don't work
We test in some machines ip address static the problem is fixed.

We don't know if the problem is in the machines, dhcp or dns.

Please somebody can help me

 

[Chuck]

Several months, all machines (340) has been changed with lenovo desktops and
upgraded the winxp sp1 to winxp sp2... lots of this machines can not be
connect to the domain controller and the principal windows services can not
start (ej. Computer Browser, Server, DHCP Client, Windows Audio, Workstation
and others) i found in lenovo the same error and with the same network card...

http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-58745

We test modify the register entry... and don't work
We test in some machines ip address static the problem is fixed.

We don't know if the problem is in the machines, dhcp or dns.

Please somebody can help me

 

[Chuck]

Several months, all machines (340) has been changed with lenovo desktops and
upgraded the winxp sp1 to winxp sp2... lots of this machines can not be
connect to the domain controller and the principal windows services can not
start (ej. Computer Browser, Server, DHCP Client, Windows Audio, Workstation
and others) i found in lenovo the same error and with the same network card...

http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-58745

We test modify the register entry... and don't work
We test in some machines ip address static the problem is fixed.

We don't know if the problem is in the machines, dhcp or dns.

Please somebody can help me

If you bought 340 computers from Lenovo, you should have some contact with them
to help you better than an online search that tells you
Solution
This is a limitation between various network hardware and software devices. To
resolve this issue you can enter a delay in the login script.

That's not a solution, in my opinion.

Is there a problem with using static IP addressing?

 

[Guest]

i test with the command and display the dns information.. there something to
check in the dhcp server? this was changed 1 month before of machines
changed.. and working ok with winxp sp1. i'm sure that problem is in the dns
or dhcp servers, but i can't to prove this..

other suggestion?

sorry my english is not good

 

[Guest]

with static ip address the computers found the domain controller and delay in
start not work, and appear the same error.

but that is not the solution.

in the event viewer appear the following message:

"Your computer was not able to renew its address from the network (from the
DHCP Server) for the Network Card with network address xxxxxxxxxxxxx. 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."

and

"No Domain Controller is available for domain CL due to the following:
There are currently no logon servers available to service the logon request.
..
Make sure that the computer is connected to the network and try again. If
the problem persists, please contact your domain administrator."

and the services can't start..

you are right Chuck,but , the supervisor don't want contact with lenovo in
search for an internal solution..

Lenovo or Microsoft are good options to resolve the problem, if we've 340
licences of windows xp professional and office 2003, and other aplications,
they must be respond...

 

[Chuck]

with static ip address the computers found the domain controller and delay in
start not work, and appear the same error.

but that is not the solution.

in the event viewer appear the following message:

"Your computer was not able to renew its address from the network (from the
DHCP Server) for the Network Card with network address xxxxxxxxxxxxx. 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."

and

"No Domain Controller is available for domain CL due to the following:
There are currently no logon servers available to service the logon request.
.
Make sure that the computer is connected to the network and try again. If
the problem persists, please contact your domain administrator."

and the services can't start..

you are right Chuck,but , the supervisor don't want contact with lenovo in
search for an internal solution..

Lenovo or Microsoft are good options to resolve the problem, if we've 340
licences of windows xp professional and office 2003, and other aplications,
they must be respond...

I suspect the supervisor is busy working on his resume.

OK, the advice
This is a limitation between various network hardware and software devices. To
resolve this issue you can enter a delay in the login script.
would suggest to me that network protocols don't work properly with the drivers
for the NIC. If you can use static IP addressing, then the problem would appear
to start with DHCP. If DHCP doesn't work, then you're going to get an APIPA
address, which puts it on a different subnet and no contact with DNS or with the
domain controller.

What services and protocols does the DHCP client depend upon?