Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
This is a bit long, but it says it all:
Just received 30 Compaqs from vendor. Our company supplies image to the vendor. The vendor then images each Pc and sends them off to us.
We opened 3 PC's (NT 4 Service Pack 6A) and were unable to set up any > of the desktops for domain authentication. We can't allow the local Pc to enter the domain. However, we can ping the owld via IP and server name.
1. Local PC is listed on PDC.
2. NIC married to static IP (No DHCP)
3. We can get out to the WEB, log into Lotus Notes (WAN) and use intranet. But, we can't connect to our PDC or any other PDC's that we have tried. We have several domains in our organization and we were unable to connect to any of them!!!!! However, the last shipment, which has the same exact image version it, is able to connect to any domain we enter.
Weird! Please help. Do these PC have to go back!!!! Is there a problem with the NIC? I also used 5 different physical Lan
connections as well as 5 different UP addresses. Still, no luck. I even pulled the Lan from my desktop (which is able to access the world!) and plugged the problem PC into it....No luck! My settings on
my PC are exactly the same as the new batch of PC's received!
I think it's hardware....Your thoughts???
How about binding set up in Network, any specific order necessary???
Can SID be the problem?

We also use Ghost but the best idea is not to have Domain membership on your image as every PC will have the same Computer name and the same SID... Try getting a copy of the freeware newsid that runs OK under the WinNT or Win2ooo pro GUI. NewSID can also rename the computer name...
You will probably need to disconnect from the Domain then reboot, rename PC then reboot
and finally rejoin Domain and yes you guessed it reboot again...If you want a copy of NewSID or have any other hassles then email me
Cheers

i have had this with compaqs and etherlink 3 nics. they would do everything but join the domain. this was because tcp/ip wasn't working. it turned out to be that with these nics you must run the pre-install from the cd that comes with them first.
we removed the adapter in NT.rebooted. ran the pre-install and then installed the nic driver again and it worked.

![]() |
![]() |
![]() |

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |