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: Dave Hanson who wrote (5158)	1/17/1999 12:56:00 AM
From: Sean W. Smith	Read Replies (1) \| Respond to of 14778

Dave, when you mean not see. do you mean MS Networking or TCPIP?? try ping first. Ping all computers. If the network neighborhood doesn't show up it can be one of many windows bugs or Duplicate SID if your running cloned NT. See powerquests site for a util to fix this. Assuming you have something shared try accessing it directly via start \\machine_name Sean

To: Dave Hanson who wrote (5158)	1/17/1999 2:16:00 AM
From: Zeuspaul	Read Replies (3) \| Respond to of 14778

definitive consensus ?? Sure IN A NUTSHELL Spots has presented a fine KOT configuration and Zeuspaul wants to back it up. It started when Clarence indicated he could not see his FAT32 drive from NT. #reply-7280082 I suggested using Partition Magic to change FAT32 to FAT16 #reply-7294718 Clarence #reply-7300452 PM is still in Spots No Fly Zone<g> I think its time I petition him to lift his sanctions on this weapon of mass deconstruction<g>. Spots to the rescue #reply-7300452 This post is Central Clarence responds to Spots' proposal #reply-7315694 Zeuspaul responds to Spot's proposal #reply-7316692 trys to add backup option for KOT Spots thinks backing up KOT adds an unnecessary level of complication #reply-7317974 Clarence has been interested in the idea of backing up the KOT #reply-7318159 Clarence wants to work in the NT envelope #reply-7318601 More on why Spots mildly disagrees #reply-7319797 We agree that PM will have to be used in part in any solution #reply-7319958 in addition to NT disk utility options Sean rolls on the floor laughing #reply-7319991 Upon reflection Zeuspaul alters #reply-7323218 his original response to Spot's proposal Zeuspaul

To: Dave Hanson who wrote (5158)	1/17/1999 3:10:00 PM
From: Spots	Read Replies (2) \| Respond to of 14778

As Sean says, if you cloned it, you have a duplicate SID (System ID), a nono in NT networking. I'm not positive you can change the SID without reinstalling NT, but I THINK changing the workstation name will do it. Looks like you have already done that. I assume you have also changed the clone's IP address so there are no conflicts. An orientation question: I assume you are running a workgroup not a domain, yes? A domain requires an NT server acting as a domain controller, so I'll assume workgroup. I know more about the domain situation, but what the heck, here's a couple of shots. Let's say your workstations are named \\1, \\2, and \\3. \\3 used to be named \\1 right after you cloned it, but you renamed it to \\3. Let me further assume that the username you log on to \\1 and \\2 with is Dave. Checkpoint: \\1 and \\2 can see each other but not \\3; \\3 can see neither \\1 nor \\2; but all three can access the internet via the DSL modem. Is this correct? Aside from the fact that DSL modems are immoral till I can get one too, that is <g>. Assuming that's right, the SID on \\3 should now be different from \\1 if it's possible to do so without reinstalling. First be sure the logon names for \\1, \\2, and \\3 is the same and has the same password on all three systems, then try unjoining and rejoining the current workgroup. Do this by changing the workgroup name in network propertites, rebooting, changing it back, then rebooting again. The idea behind this is the following: In a workgroup, every NT computer maintains its own accounts and permissions, but if you log on to \\A with the same logon name and password as exists on \\B, you can access objects on \\B (with the permissions defined on \\B), provided \\A and \\B are in the same workgroup. If unjoinging then rejoining the workgroup doesn't work, you can try adding the cross-machine accounts explicitly. To do that, in the user manager on \\3 add an account for 1\Dave (substitute for "Dave" whatever name you use to log on to \\1 with, and for "1" whatever the actual name of workstation \\1 is). Give 1\Dave the same privileges that Dave has on \\3. Similarly, on \\1 add a user 3\Dave with the same privileges Dave has on \\1. In both cases, be sure Dave has the same password on both \\1 and \\3. You may need to reboot after this, but you should then be able to see \\3 from \\1 and vice versa (be sure you don't have an IP address collision, though). If that works, do the same thing with Dave on \\2 and \\3 (that is, put a 2\Dave on \\3 and a 3\Dave on \\2). If none of this works, I'm out of ideas except for reinstalling NT on \\3. You have to do a new NT install, too; otherwise you won't change the current SID. Spots PS. Once I successfully installed a new NT preserving my installed applications from the old one as follows: 1. Back up the Software key of HKEY_LOCAL_MACHINE 2. Install new NT over old one. (Make recovery disk for when following step doesn't work.) 3. Bring up to previous bug-pack level (I know MS calls 'em service packs, but let's be truthful). 4. Restore backed up Software key. If everything goes correctly, and if you've sacrificed a sufficient quantity of young memory chips still in shrink wrap to the NT gods, this restores all the application configurations. Of course you can't have disturbed the application files by the reinstall, but generally you won't unless you opt to write over later DLLs with the NT install. BTW, you can restore the software key by (1) make emergency repair disk for old NT; (2) install new NT + service packs as above; (3) restore software key from old NT emergency repair disk. DON'T restore the security key or there goes the new SID <g>.