Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Pastimes : Dream Machine ( Build your own PC ) -- Ignore unavailable to you. Want to Upgrade?

To: Clarence Dodge who wrote (6286)	2/14/1999 7:17:00 PM
From: Spots	Read Replies (2) \| Respond to of 14778

Before I forget, I'm going to post the sequence of events that happened to me yesterday. I have some suspicions but no knowledge of what caused it, so I won't speculate here. Configured NT (WS) on one PC, then cloned the boot drive to a new disk. Booted clone on same PC (rejumpered to be same drive), logged on to network, no problem. As expected. Booted disk on new PC. Two config differences: Different NIC, same type as configured, but different mac addr... duh, forgot the name of it--anyhow, different network ids for the NIC. Also no SCSI card. SCSI card not an issue; I just note it. Attempt to log on to network as domain member failed. A symptom. This is not about domains. Could not ping other pcs on lan. NIC amd hub show connectivity. Could not ping this PC from others on lane. Could not find computers by name, though NETBUEI was installed. NIC driver started and working normally. Reinstall driver, no change. Delete and re-add NIC, no change (you'd think this would recognize the new NIC address, or I would). Changed out of domain to workgroup; changed PC name; tried to change back; could not connect to domain controller. Could not ping nor be pinged. Apparently neither NETBEUI nor TCP/IP working. Deleted both protocols, then added them back. Bingo! Up it came. I was then able to rejoin the domain with the new PC name and everything was happy. Real puzzle was, it was not a domain/security issue as far as I could make out, because I couldn't even do low level IP tests. Nor was it a NIC mac ID issue, as far as I can tell, because I deleted and readded the NIC. So I don't have a clue what it was. Maybe a SID issue, but that doesn't seem too likely at all. As the King of Siam said to Anna, is a puzzlement.