R
Richard Wakeman
Hi - Ok, here is the problem. I work as a computer assistant for a large
office complex. Even the Systems Analyst in our IT group are stumped on
this one. Recently in one of the departments, they installed about 5
workstations all "cloned" or imaged with XP Pro hard drives, and then set
them up on a local LAN peer to peer. Then the goal was to have these
workstations connect to an older PC running Windows 2000 which contains a
Database Program and to be able to network with this database application.
On each workstation (XP's), the database program was installed and then
pointed to look at the data on the 2000 PC. This will work fine, once there
is a connection between workstation and the 2000 PC.
The basic problem is that connection with this PC with Win 2000 (NT) and the
database program does not hold after logging out and then back in, or
rebooting, etc. Once a particular workstation is up, a connection can be
established by going into the Network Places and clicking on the 2000 PC to
open it up. Yes, Network will see the name of that PC and lists the other
workstations by name too, of course. So clicking on it will bring up a
Password dialog, and you have to enter the 2000 PC's Userid and Password and
then it will handshake and connect and all's well. In this case, the
Windows 2000 machine has a user id with no password. The workstations all
have UserIDs that are the same but with different Passwords one each.
So, then after connecting one can map a network drive to it and tell it to
reconnect at logon, etc. But then loging off and back on, there is no
connection, and one has to be re-established thru the Network Places again.
Then odd thing about this is that sometimes it will work at seeming random
workstations either all the time or sometimes. But most of them, do not
connect at all except when forced to.
We thought maybe the problem was that all the drives were cloned with the
same SID, so we changed SID's -- but it made no difference. Anybody got any
clues?
Thanks,
RickyW.....
office complex. Even the Systems Analyst in our IT group are stumped on
this one. Recently in one of the departments, they installed about 5
workstations all "cloned" or imaged with XP Pro hard drives, and then set
them up on a local LAN peer to peer. Then the goal was to have these
workstations connect to an older PC running Windows 2000 which contains a
Database Program and to be able to network with this database application.
On each workstation (XP's), the database program was installed and then
pointed to look at the data on the 2000 PC. This will work fine, once there
is a connection between workstation and the 2000 PC.
The basic problem is that connection with this PC with Win 2000 (NT) and the
database program does not hold after logging out and then back in, or
rebooting, etc. Once a particular workstation is up, a connection can be
established by going into the Network Places and clicking on the 2000 PC to
open it up. Yes, Network will see the name of that PC and lists the other
workstations by name too, of course. So clicking on it will bring up a
Password dialog, and you have to enter the 2000 PC's Userid and Password and
then it will handshake and connect and all's well. In this case, the
Windows 2000 machine has a user id with no password. The workstations all
have UserIDs that are the same but with different Passwords one each.
So, then after connecting one can map a network drive to it and tell it to
reconnect at logon, etc. But then loging off and back on, there is no
connection, and one has to be re-established thru the Network Places again.
Then odd thing about this is that sometimes it will work at seeming random
workstations either all the time or sometimes. But most of them, do not
connect at all except when forced to.
We thought maybe the problem was that all the drives were cloned with the
same SID, so we changed SID's -- but it made no difference. Anybody got any
clues?
Thanks,
RickyW.....