Re: Duplicate Name exists on the Network
- From: "William L. Hartzell" <wlhartzell@xxxxxxxxxxx>
- Date: Fri, 08 Jul 2005 18:11:26 -0500
Sir:
R. G. Newbury wrote:
On Fri, 8 Jul 2005 20:46:11 UTC, Michael Lueck <NmlueckO@xxxxxxxxxxxxxxxxxxxxxxxx> wrote:Go back and check your notes. The update path to 32-bits is Wr8610 and
Trevor Hemsley wrote:
I think I've had this error when I've tried to call a workstation the same name as a userid.There are probably some reserved words you should not name the computer... seems like userid's and groupid's could do this sort of a thing. Been a long time, though, since I delt with computers with names like "accounting" and then someone goes and makes a group of the same name.
That's what makes this so strange. I started with a full working system of:
Warp 4 + Fixpak 15 + DDpak 2 with other upgrades in the WR084xx series, IP085xx series and UN980...
I followed Al Savage's upgrade route. (IIRC from memory: WR08610 then WR08621 then Un980 again (and the TCPOEX fix), then TCPIP4.1 then UN2001 and the two numbered APAR fixes... maybe UN980 was re-installed some else in the sequence..maybe even more than once... There were a lot of re-boots!)
Throughout this, I did not start the server. I did start the requester in order to check the connectivity. But at no time did I change any users, groups or names. Only somewhere near or at the end, did I start getting the duplicate name error.....
And there are only a limited number of user id's and none of them are duplicates. Presently consist only of: geoff, newbury, tp600e, linus, tor2 and tor3 (latter 3 are desktop systems...and I have stripped them out of c:\mptn\etc\hosts at least temporarily..
Thoroughly weird as this error comes up when the system is standalone!...But there are no dups in net.acc, so where/what could
it be.
delete tcpcoex.exe. Reboot. Install un0980. Reboot. Install wr8621 and the new tcpcoex.exe. Reboot. Failure to delete tcpcoex.exe before the first reboot will cause part of the first install to be deleted, which then will not be present to be updated by the last install.
Afterwards, you'll need to do the Peer updates and then run the Peer install/configure program, to make it happy with the new code. If you don't run (install) the updates for Peer, the configure program will remove part of the MPTN updates (you'll know that this is happening when it asks for the Warp 4 cd).
-- Bill Thanks a Million! .
- Follow-Ups:
- Re: Duplicate Name exists on the Network
- From: R. G. Newbury
- Re: Duplicate Name exists on the Network
- References:
- Duplicate Name exists on the Network
- From: R. G. Newbury
- Re: Duplicate Name exists on the Network
- From: Allodoxaphobia
- Re: Duplicate Name exists on the Network
- From: R. G. Newbury
- Re: Duplicate Name exists on the Network
- From: Trevor Hemsley
- Re: Duplicate Name exists on the Network
- From: Michael Lueck
- Re: Duplicate Name exists on the Network
- From: R. G. Newbury
- Duplicate Name exists on the Network
- Prev by Date: Re: Duplicate Name exists on the Network
- Next by Date: Re: Duplicate Name exists on the Network
- Previous by thread: Re: Duplicate Name exists on the Network
- Next by thread: Re: Duplicate Name exists on the Network
- Index(es):
Relevant Pages
|