"Lem" wrote:

> noelma wrote:
> > Have 3 PC's on Home Network.  All running WXP SP3.
> > Been working fine up til recently - but may have done something to create
> > this problem while trying to sort out other problems!
> > Anyway, network works ine except number 3 pc cannot access number 2.  Get
> > message that access is denies, etc., then says "You were not connected
> > because a duplicate name exosts on the network.  Go to System in Control
> > Panel to change the computer name and try again".
> > All three PCs have different names, so what could the problem be?
>
> Just for all of the obsessive-compulsives here, on each  of your 3
> computers, right-click "My Computer," select "Properties," and click the
> "Computer Name" tab. Report in your next post *both* the "Full computer
> name" *and* the "Workgroup" name for each of your 3 computers.
>
> If that doesn't give you a clue, open a Command Prompt window and type
>
> nbtstat -n [press Enter]
> nbtstat -r [press Enter]
>
> and report the results from both of these commands.  Be sure to use a
> lower case "r" in the second command.
>
> --
> Lem -- MS-MVP
>
> To the moon and back with 2K words of RAM and 36K words of ROM.
> http://en.wikipedia.org/wiki/Apollo_Guidance_Computer
> http://history.nasa.gov/afj/compessay.htm
>

> Hi Lem.
> Referring to the 3 PCs as 1, 2 & 3.
> 1 can see/share 2 & 3 no problems
> 2 can see/share 1 & 3 no problems
> 3 can see/share 1 no problems
> 3 can see 2 as a member of group, but no access.
> Names: 1 = Fujit001, 2 = Fujit002, 3 = Fujit003
> All show Workgroup as MSHOME.
>
> nbtstat -n results:
> Node IP addresses - 1 = 192.468.1.100
> 2 = 192.468.1.101
> 3 = 192.468.1.102
> Net Bios Local Name Table for 1
> FUJIT001  <00>  UNIQUE  REGISTERED
> FUJIT001  <20>  UNIQUE  REGISTERED
> MSHOME  <00>  GROUP REGISTERED
> MSHOME  <1E>  GROUP REGISTERED
> Net Bios Local Name Table for 2
> FUJIT002  <00>  UNIQUE  REGISTERED
> FUJIT002  <20>  UNIQUE  REGISTERED
> MSHOME  <00>  GROUP REGISTERED
> MSHOME  <1E>  GROUP REGISTERED
> Net Bios Local Name Table for 3
> FUJIT003  <00>  UNIQUE  REGISTERED
> MSHOME  <00>  GROUP REGISTERED
> FUJIT003  <20>  UNIQUE  REGISTERED
> MSHOME  <1E>  GROUP REGISTERED
> MSHOME  <1D>  UNIQUE REGISTERED
> .._MSBROWSE_.  <01> GROUP REGISTERED
>
> nbtstat -r results:                            PC1     PC2     PC3
> RESOLVED BY BROADCAST               17       31       215
> RESOLVED BY NAME SERVER              0         0           0
> REGISTERED BY BROADCAST              8         8           6
> REGISTERED BY NAME SERVER           0         0           0
>
> NET BIOS NAMES RESOLVED BY BROADCAST
>
> PC1
> FUJIT003  <00>
> FUJIT002  <00>
> FUJIT002
> FUJIT002  <00>
> FUJIT002
> FUJIT002  <00>
> FUJIT002  <00>
> FUJIT002
>
> PC2
> FUJIT003  <00>
> FUJIT001  <00>
> FUJIT001
> FUJIT003
> FUJIT003  <00>
> FUJIT001  <00>
> FUJIT001
> FUJIT003
>
> PC3
> FUJIT001  <00>
> FUJIT002  <00>
> FUJIT001  <00>
> FUJIT002  <00>
> FUJIT001
> FUJIT001  <00>
> FUJIT001  <00>
> FUJIT001  <00>
>
>
>
>
>
> "Lem" wrote:
>
>> noelma wrote:
>>> Have 3 PC's on Home Network.  All running WXP SP3.
>>> Been working fine up til recently - but may have done something to create
>>> this problem while trying to sort out other problems!
>>> Anyway, network works ine except number 3 pc cannot access number 2.  Get
>>> message that access is denies, etc., then says "You were not connected
>>> because a duplicate name exosts on the network.  Go to System in Control
>>> Panel to change the computer name and try again".
>>> All three PCs have different names, so what could the problem be?
>> Just for all of the obsessive-compulsives here, on each  of your 3
>> computers, right-click "My Computer," select "Properties," and click the
>> "Computer Name" tab. Report in your next post *both* the "Full computer
>> name" *and* the "Workgroup" name for each of your 3 computers.
>>
>> If that doesn't give you a clue, open a Command Prompt window and type
>>
>> nbtstat -n [press Enter]
>> nbtstat -r [press Enter]
>>
>> and report the results from both of these commands.  Be sure to use a
>> lower case "r" in the second command.
>>
>> --
>> Lem -- MS-MVP
>>
>> To the moon and back with 2K words of RAM and 36K words of ROM.
>> http://en.wikipedia.org/wiki/Apollo_Guidance_Computer
>> http://history.nasa.gov/afj/compessay.htm
>>

"Lem" wrote:

> noelma wrote:
> > Hi Lem.
> > Referring to the 3 PCs as 1, 2 & 3.
> > 1 can see/share 2 & 3 no problems
> > 2 can see/share 1 & 3 no problems
> > 3 can see/share 1 no problems
> > 3 can see 2 as a member of group, but no access.
> > Names: 1 = Fujit001, 2 = Fujit002, 3 = Fujit003
> > All show Workgroup as MSHOME.
> >
> > nbtstat -n results:
> > Node IP addresses - 1 = 192.468.1.100
> > 2 = 192.468.1.101
> > 3 = 192.468.1.102
> > Net Bios Local Name Table for 1
> > FUJIT001  <00>  UNIQUE  REGISTERED
> > FUJIT001  <20>  UNIQUE  REGISTERED
> > MSHOME  <00>  GROUP REGISTERED
> > MSHOME  <1E>  GROUP REGISTERED
> > Net Bios Local Name Table for 2
> > FUJIT002  <00>  UNIQUE  REGISTERED
> > FUJIT002  <20>  UNIQUE  REGISTERED
> > MSHOME  <00>  GROUP REGISTERED
> > MSHOME  <1E>  GROUP REGISTERED
> > Net Bios Local Name Table for 3
> > FUJIT003  <00>  UNIQUE  REGISTERED
> > MSHOME  <00>  GROUP REGISTERED
> > FUJIT003  <20>  UNIQUE  REGISTERED
> > MSHOME  <1E>  GROUP REGISTERED
> > MSHOME  <1D>  UNIQUE REGISTERED
> > .._MSBROWSE_.  <01> GROUP REGISTERED
> >
> > nbtstat -r results:                            PC1     PC2     PC3
> > RESOLVED BY BROADCAST               17       31       215
> > RESOLVED BY NAME SERVER              0         0           0
> > REGISTERED BY BROADCAST              8         8           6
> > REGISTERED BY NAME SERVER           0         0           0
> >
> > NET BIOS NAMES RESOLVED BY BROADCAST
> >
> > PC1
> > FUJIT003  <00>
> > FUJIT002  <00>
> > FUJIT002
> > FUJIT002  <00>
> > FUJIT002
> > FUJIT002  <00>
> > FUJIT002  <00>
> > FUJIT002
> >
> > PC2
> > FUJIT003  <00>
> > FUJIT001  <00>
> > FUJIT001
> > FUJIT003
> > FUJIT003  <00>
> > FUJIT001  <00>
> > FUJIT001
> > FUJIT003
> >
> > PC3
> > FUJIT001  <00>
> > FUJIT002  <00>
> > FUJIT001  <00>
> > FUJIT002  <00>
> > FUJIT001
> > FUJIT001  <00>
> > FUJIT001  <00>
> > FUJIT001  <00>
> >
> >
> >
> >
> >
> > "Lem" wrote:
> >
> >> noelma wrote:
> >>> Have 3 PC's on Home Network.  All running WXP SP3.
> >>> Been working fine up til recently - but may have done something to create
> >>> this problem while trying to sort out other problems!
> >>> Anyway, network works ine except number 3 pc cannot access number 2.  Get
> >>> message that access is denies, etc., then says "You were not connected
> >>> because a duplicate name exosts on the network.  Go to System in Control
> >>> Panel to change the computer name and try again".
> >>> All three PCs have different names, so what could the problem be?
> >> Just for all of the obsessive-compulsives here, on each  of your 3
> >> computers, right-click "My Computer," select "Properties," and click the
> >> "Computer Name" tab. Report in your next post *both* the "Full computer
> >> name" *and* the "Workgroup" name for each of your 3 computers.
> >>
> >> If that doesn't give you a clue, open a Command Prompt window and type
> >>
> >> nbtstat -n [press Enter]
> >> nbtstat -r [press Enter]
> >>
> >> and report the results from both of these commands.  Be sure to use a
> >> lower case "r" in the second command.
> >>
> >> --
> >> Lem -- MS-MVP
> >>
> >> To the moon and back with 2K words of RAM and 36K words of ROM.
> >> http://en.wikipedia.org/wiki/Apollo_Guidance_Computer
> >> http://history.nasa.gov/afj/compessay.htm
> >>
>
> The problem isn't obvious.
>
> When you were trying to sort out your other problems, did you do
> anything with your LMHOSTS file on any of the PCs? What did you do?
>
> What are you using to control your network? Anything other than a
> standard consumer-grade router?
>
> Did you add any protocols to the adapters on any of the the machines?
> If you go to "View Network Connections" and right click on the icon for
> the Local Area Connection and select Properties, is there anything else
> listed other than these four items (it's OK if you don't have all 4)?
> Client for Microsoft Networks
> QoS Packet Scheduler
> File and Printer Sharing for Microsoft Networks
> Internet Protocol (TCP/IP)
> --
> Lem -- MS-MVP
>
> To the moon and back with 2K words of RAM and 36K words of ROM.
> http://en.wikipedia.org/wiki/Apollo_Guidance_Computer
> http://history.nasa.gov/afj/compessay.htm
>

> Hi Lem!  Thanks for all the effort!  To answer your questions:
> When you were trying to sort out your other problems, did you do
> anything with your LMHOSTS file on any of the PCs? NOT AS FAR AS I KNOW.
> What did you do? RAN SubInACL Tool TO RECTIFY REGISTRY PROBLEM ON PC1
> PREVENTING INSTALL OF REAL PLAYER.
> What are you using to control your network? Anything other than a standard
> consumer-grade router? NO - LINKSYS ADSL GATEWAY
> Did you add any protocols to the adapters on any of the the machines? NO
>> Client for Microsoft Networks
>> QoS Packet Scheduler
>> File and Printer Sharing for Microsoft Networks
>> Internet Protocol (TCP/IP)
> ONLY ALL FOUR ON EACH MACHINE.
>
> Thinking about starting again by renaming all machines and setting up
> network fresh.  Any reasons not to do that?
>
>
>
>
>
> "Lem" wrote:
>
>> noelma wrote:
>>> Hi Lem.
>>> Referring to the 3 PCs as 1, 2 & 3.
>>> 1 can see/share 2 & 3 no problems
>>> 2 can see/share 1 & 3 no problems
>>> 3 can see/share 1 no problems
>>> 3 can see 2 as a member of group, but no access.
>>> Names: 1 = Fujit001, 2 = Fujit002, 3 = Fujit003
>>> All show Workgroup as MSHOME.
>>>
>>> nbtstat -n results:
>>> Node IP addresses - 1 = 192.468.1.100
>>> 2 = 192.468.1.101
>>> 3 = 192.468.1.102
>>> Net Bios Local Name Table for 1
>>> FUJIT001  <00>  UNIQUE  REGISTERED
>>> FUJIT001  <20>  UNIQUE  REGISTERED
>>> MSHOME  <00>  GROUP REGISTERED
>>> MSHOME  <1E>  GROUP REGISTERED
>>> Net Bios Local Name Table for 2
>>> FUJIT002  <00>  UNIQUE  REGISTERED
>>> FUJIT002  <20>  UNIQUE  REGISTERED
>>> MSHOME  <00>  GROUP REGISTERED
>>> MSHOME  <1E>  GROUP REGISTERED
>>> Net Bios Local Name Table for 3
>>> FUJIT003  <00>  UNIQUE  REGISTERED
>>> MSHOME  <00>  GROUP REGISTERED
>>> FUJIT003  <20>  UNIQUE  REGISTERED
>>> MSHOME  <1E>  GROUP REGISTERED
>>> MSHOME  <1D>  UNIQUE REGISTERED
>>> .._MSBROWSE_.  <01> GROUP REGISTERED
>>>
>>> nbtstat -r results:                            PC1     PC2     PC3
>>> RESOLVED BY BROADCAST               17       31       215
>>> RESOLVED BY NAME SERVER              0         0           0
>>> REGISTERED BY BROADCAST              8         8           6
>>> REGISTERED BY NAME SERVER           0         0           0
>>>
>>> NET BIOS NAMES RESOLVED BY BROADCAST
>>>
>>> PC1
>>> FUJIT003  <00>
>>> FUJIT002  <00>
>>> FUJIT002
>>> FUJIT002  <00>
>>> FUJIT002
>>> FUJIT002  <00>
>>> FUJIT002  <00>
>>> FUJIT002
>>>
>>> PC2
>>> FUJIT003  <00>
>>> FUJIT001  <00>
>>> FUJIT001
>>> FUJIT003
>>> FUJIT003  <00>
>>> FUJIT001  <00>
>>> FUJIT001
>>> FUJIT003
>>>
>>> PC3
>>> FUJIT001  <00>
>>> FUJIT002  <00>
>>> FUJIT001  <00>
>>> FUJIT002  <00>
>>> FUJIT001
>>> FUJIT001  <00>
>>> FUJIT001  <00>
>>> FUJIT001  <00>
>>>
>>>
>>>
>>>
>>>
>>> "Lem" wrote:
>>>
>>>> noelma wrote:
>>>>> Have 3 PC's on Home Network.  All running WXP SP3.
>>>>> Been working fine up til recently - but may have done something to create
>>>>> this problem while trying to sort out other problems!
>>>>> Anyway, network works ine except number 3 pc cannot access number 2.  Get
>>>>> message that access is denies, etc., then says "You were not connected
>>>>> because a duplicate name exosts on the network.  Go to System in Control
>>>>> Panel to change the computer name and try again".
>>>>> All three PCs have different names, so what could the problem be?
>>>> Just for all of the obsessive-compulsives here, on each  of your 3
>>>> computers, right-click "My Computer," select "Properties," and click the
>>>> "Computer Name" tab. Report in your next post *both* the "Full computer
>>>> name" *and* the "Workgroup" name for each of your 3 computers.
>>>>
>>>> If that doesn't give you a clue, open a Command Prompt window and type
>>>>
>>>> nbtstat -n [press Enter]
>>>> nbtstat -r [press Enter]
>>>>
>>>> and report the results from both of these commands.  Be sure to use a
>>>> lower case "r" in the second command.
>>>>
>>>> --
>>>> Lem -- MS-MVP
>>>>
>>>> To the moon and back with 2K words of RAM and 36K words of ROM.
>>>> http://en.wikipedia.org/wiki/Apollo_Guidance_Computer
>>>> http://history.nasa.gov/afj/compessay.htm
>>>>
>> The problem isn't obvious.
>>
>> When you were trying to sort out your other problems, did you do
>> anything with your LMHOSTS file on any of the PCs? What did you do?
>>
>> What are you using to control your network? Anything other than a
>> standard consumer-grade router?
>>
>> Did you add any protocols to the adapters on any of the the machines?
>> If you go to "View Network Connections" and right click on the icon for
>> the Local Area Connection and select Properties, is there anything else
>> listed other than these four items (it's OK if you don't have all 4)?
>> Client for Microsoft Networks
>> QoS Packet Scheduler
>> File and Printer Sharing for Microsoft Networks
>> Internet Protocol (TCP/IP)
>> --
>> Lem -- MS-MVP
>>
>> To the moon and back with 2K words of RAM and 36K words of ROM.
>> http://en.wikipedia.org/wiki/Apollo_Guidance_Computer
>> http://history.nasa.gov/afj/compessay.htm
>>

"Lem" wrote:

> noelma wrote:
> > Hi Lem!  Thanks for all the effort!  To answer your questions:
> > When you were trying to sort out your other problems, did you do
> > anything with your LMHOSTS file on any of the PCs? NOT AS FAR AS I KNOW.
> > What did you do? RAN SubInACL Tool TO RECTIFY REGISTRY PROBLEM ON PC1
> > PREVENTING INSTALL OF REAL PLAYER.
> > What are you using to control your network? Anything other than a standard
> > consumer-grade router? NO - LINKSYS ADSL GATEWAY
> > Did you add any protocols to the adapters on any of the the machines? NO
> >> Client for Microsoft Networks
> >> QoS Packet Scheduler
> >> File and Printer Sharing for Microsoft Networks
> >> Internet Protocol (TCP/IP)
> > ONLY ALL FOUR ON EACH MACHINE.
> >
> > Thinking about starting again by renaming all machines and setting up
> > network fresh.  Any reasons not to do that?
> >
> >
> >
> >
> >
> > "Lem" wrote:
> >
> >> noelma wrote:
> >>> Hi Lem.
> >>> Referring to the 3 PCs as 1, 2 & 3.
> >>> 1 can see/share 2 & 3 no problems
> >>> 2 can see/share 1 & 3 no problems
> >>> 3 can see/share 1 no problems
> >>> 3 can see 2 as a member of group, but no access.
> >>> Names: 1 = Fujit001, 2 = Fujit002, 3 = Fujit003
> >>> All show Workgroup as MSHOME.
> >>>
> >>> nbtstat -n results:
> >>> Node IP addresses - 1 = 192.468.1.100
> >>> 2 = 192.468.1.101
> >>> 3 = 192.468.1.102
> >>> Net Bios Local Name Table for 1
> >>> FUJIT001  <00>  UNIQUE  REGISTERED
> >>> FUJIT001  <20>  UNIQUE  REGISTERED
> >>> MSHOME  <00>  GROUP REGISTERED
> >>> MSHOME  <1E>  GROUP REGISTERED
> >>> Net Bios Local Name Table for 2
> >>> FUJIT002  <00>  UNIQUE  REGISTERED
> >>> FUJIT002  <20>  UNIQUE  REGISTERED
> >>> MSHOME  <00>  GROUP REGISTERED
> >>> MSHOME  <1E>  GROUP REGISTERED
> >>> Net Bios Local Name Table for 3
> >>> FUJIT003  <00>  UNIQUE  REGISTERED
> >>> MSHOME  <00>  GROUP REGISTERED
> >>> FUJIT003  <20>  UNIQUE  REGISTERED
> >>> MSHOME  <1E>  GROUP REGISTERED
> >>> MSHOME  <1D>  UNIQUE REGISTERED
> >>> .._MSBROWSE_.  <01> GROUP REGISTERED
> >>>
> >>> nbtstat -r results:                            PC1     PC2     PC3
> >>> RESOLVED BY BROADCAST               17       31       215
> >>> RESOLVED BY NAME SERVER              0         0           0
> >>> REGISTERED BY BROADCAST              8         8           6
> >>> REGISTERED BY NAME SERVER           0         0           0
> >>>
> >>> NET BIOS NAMES RESOLVED BY BROADCAST
> >>>
> >>> PC1
> >>> FUJIT003  <00>
> >>> FUJIT002  <00>
> >>> FUJIT002
> >>> FUJIT002  <00>
> >>> FUJIT002
> >>> FUJIT002  <00>
> >>> FUJIT002  <00>
> >>> FUJIT002
> >>>
> >>> PC2
> >>> FUJIT003  <00>
> >>> FUJIT001  <00>
> >>> FUJIT001
> >>> FUJIT003
> >>> FUJIT003  <00>
> >>> FUJIT001  <00>
> >>> FUJIT001
> >>> FUJIT003
> >>>
> >>> PC3
> >>> FUJIT001  <00>
> >>> FUJIT002  <00>
> >>> FUJIT001  <00>
> >>> FUJIT002  <00>
> >>> FUJIT001
> >>> FUJIT001  <00>
> >>> FUJIT001  <00>
> >>> FUJIT001  <00>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> "Lem" wrote:
> >>>
> >>>> noelma wrote:
> >>>>> Have 3 PC's on Home Network.  All running WXP SP3.
> >>>>> Been working fine up til recently - but may have done something to create
> >>>>> this problem while trying to sort out other problems!
> >>>>> Anyway, network works ine except number 3 pc cannot access number 2.  Get
> >>>>> message that access is denies, etc., then says "You were not connected
> >>>>> because a duplicate name exosts on the network.  Go to System in Control
> >>>>> Panel to change the computer name and try again".
> >>>>> All three PCs have different names, so what could the problem be?
> >>>> Just for all of the obsessive-compulsives here, on each  of your 3
> >>>> computers, right-click "My Computer," select "Properties," and click the
> >>>> "Computer Name" tab. Report in your next post *both* the "Full computer
> >>>> name" *and* the "Workgroup" name for each of your 3 computers.
> >>>>
> >>>> If that doesn't give you a clue, open a Command Prompt window and type
> >>>>
> >>>> nbtstat -n [press Enter]
> >>>> nbtstat -r [press Enter]
> >>>>
> >>>> and report the results from both of these commands.  Be sure to use a
> >>>> lower case "r" in the second command.
> >>>>
> >>>> --
> >>>> Lem -- MS-MVP
> >>>>
> >>>> To the moon and back with 2K words of RAM and 36K words of ROM.
> >>>> http://en.wikipedia.org/wiki/Apollo_Guidance_Computer
> >>>> http://history.nasa.gov/afj/compessay.htm
> >>>>
> >> The problem isn't obvious.
> >>
> >> When you were trying to sort out your other problems, did you do
> >> anything with your LMHOSTS file on any of the PCs? What did you do?
> >>
> >> What are you using to control your network? Anything other than a
> >> standard consumer-grade router?
> >>
> >> Did you add any protocols to the adapters on any of the the machines?
> >> If you go to "View Network Connections" and right click on the icon for
> >> the Local Area Connection and select Properties, is there anything else
> >> listed other than these four items (it's OK if you don't have all 4)?
> >> Client for Microsoft Networks
> >> QoS Packet Scheduler
> >> File and Printer Sharing for Microsoft Networks
> >> Internet Protocol (TCP/IP)
> >> --
> >> Lem -- MS-MVP
> >>
> >> To the moon and back with 2K words of RAM and 36K words of ROM.
> >> http://en.wikipedia.org/wiki/Apollo_Guidance_Computer
> >> http://history.nasa.gov/afj/compessay.htm
> >>
>
> I haven't used SubInACL myself, but that could well be the source of
> your problem.  If you can use System Restore to go back to a point prior
> to using SubInACL, you might try it and see if that removes your network
> problem.
>
> Otherwise, sure, go ahead and rename all of the machines and resetup the
> network. It couldn't hurt.
>
> Sorry I couldn't offer more definitive help.
> --
> Lem -- MS-MVP
>
> To the moon and back with 2K words of RAM and 36K words of ROM.
> http://en.wikipedia.org/wiki/Apollo_Guidance_Computer
> http://history.nasa.gov/afj/compessay.htm
>

> Hi Lem!
> Renamed all computers, created a new Workgroup name, ran wizard for craeting
> work group and all is well! :)
> Thanks.
>
> "Lem" wrote:
>
>> noelma wrote:
>>> Hi Lem!  Thanks for all the effort!  To answer your questions:
>>> When you were trying to sort out your other problems, did you do
>>> anything with your LMHOSTS file on any of the PCs? NOT AS FAR AS I KNOW.
>>> What did you do? RAN SubInACL Tool TO RECTIFY REGISTRY PROBLEM ON PC1
>>> PREVENTING INSTALL OF REAL PLAYER.
>>> What are you using to control your network? Anything other than a standard
>>> consumer-grade router? NO - LINKSYS ADSL GATEWAY
>>> Did you add any protocols to the adapters on any of the the machines? NO
>>>> Client for Microsoft Networks
>>>> QoS Packet Scheduler
>>>> File and Printer Sharing for Microsoft Networks
>>>> Internet Protocol (TCP/IP)
>>> ONLY ALL FOUR ON EACH MACHINE.
>>>
>>> Thinking about starting again by renaming all machines and setting up
>>> network fresh.  Any reasons not to do that?
>>>
>>>
>>>
>>>
>>>
>>> "Lem" wrote:
>>>
>>>> noelma wrote:
>>>>> Hi Lem.
>>>>> Referring to the 3 PCs as 1, 2 & 3.
>>>>> 1 can see/share 2 & 3 no problems
>>>>> 2 can see/share 1 & 3 no problems
>>>>> 3 can see/share 1 no problems
>>>>> 3 can see 2 as a member of group, but no access.
>>>>> Names: 1 = Fujit001, 2 = Fujit002, 3 = Fujit003
>>>>> All show Workgroup as MSHOME.
>>>>>
>>>>> nbtstat -n results:
>>>>> Node IP addresses - 1 = 192.468.1.100
>>>>> 2 = 192.468.1.101
>>>>> 3 = 192.468.1.102
>>>>> Net Bios Local Name Table for 1
>>>>> FUJIT001  <00>  UNIQUE  REGISTERED
>>>>> FUJIT001  <20>  UNIQUE  REGISTERED
>>>>> MSHOME  <00>  GROUP REGISTERED
>>>>> MSHOME  <1E>  GROUP REGISTERED
>>>>> Net Bios Local Name Table for 2
>>>>> FUJIT002  <00>  UNIQUE  REGISTERED
>>>>> FUJIT002  <20>  UNIQUE  REGISTERED
>>>>> MSHOME  <00>  GROUP REGISTERED
>>>>> MSHOME  <1E>  GROUP REGISTERED
>>>>> Net Bios Local Name Table for 3
>>>>> FUJIT003  <00>  UNIQUE  REGISTERED
>>>>> MSHOME  <00>  GROUP REGISTERED
>>>>> FUJIT003  <20>  UNIQUE  REGISTERED
>>>>> MSHOME  <1E>  GROUP REGISTERED
>>>>> MSHOME  <1D>  UNIQUE REGISTERED
>>>>> .._MSBROWSE_.  <01> GROUP REGISTERED
>>>>>
>>>>> nbtstat -r results:                            PC1     PC2     PC3
>>>>> RESOLVED BY BROADCAST               17       31       215
>>>>> RESOLVED BY NAME SERVER              0         0           0
>>>>> REGISTERED BY BROADCAST              8         8           6
>>>>> REGISTERED BY NAME SERVER           0         0           0
>>>>>
>>>>> NET BIOS NAMES RESOLVED BY BROADCAST
>>>>>
>>>>> PC1
>>>>> FUJIT003  <00>
>>>>> FUJIT002  <00>
>>>>> FUJIT002
>>>>> FUJIT002  <00>
>>>>> FUJIT002
>>>>> FUJIT002  <00>
>>>>> FUJIT002  <00>
>>>>> FUJIT002
>>>>>
>>>>> PC2
>>>>> FUJIT003  <00>
>>>>> FUJIT001  <00>
>>>>> FUJIT001
>>>>> FUJIT003
>>>>> FUJIT003  <00>
>>>>> FUJIT001  <00>
>>>>> FUJIT001
>>>>> FUJIT003
>>>>>
>>>>> PC3
>>>>> FUJIT001  <00>
>>>>> FUJIT002  <00>
>>>>> FUJIT001  <00>
>>>>> FUJIT002  <00>
>>>>> FUJIT001
>>>>> FUJIT001  <00>
>>>>> FUJIT001  <00>
>>>>> FUJIT001  <00>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> "Lem" wrote:
>>>>>
>>>>>> noelma wrote:
>>>>>>> Have 3 PC's on Home Network.  All running WXP SP3.
>>>>>>> Been working fine up til recently - but may have done something to create
>>>>>>> this problem while trying to sort out other problems!
>>>>>>> Anyway, network works ine except number 3 pc cannot access number 2.  Get
>>>>>>> message that access is denies, etc., then says "You were not connected
>>>>>>> because a duplicate name exosts on the network.  Go to System in Control
>>>>>>> Panel to change the computer name and try again".
>>>>>>> All three PCs have different names, so what could the problem be?
>>>>>> Just for all of the obsessive-compulsives here, on each  of your 3
>>>>>> computers, right-click "My Computer," select "Properties," and click the
>>>>>> "Computer Name" tab. Report in your next post *both* the "Full computer
>>>>>> name" *and* the "Workgroup" name for each of your 3 computers.
>>>>>>
>>>>>> If that doesn't give you a clue, open a Command Prompt window and type
>>>>>>
>>>>>> nbtstat -n [press Enter]
>>>>>> nbtstat -r [press Enter]
>>>>>>
>>>>>> and report the results from both of these commands.  Be sure to use a
>>>>>> lower case "r" in the second command.
>>>>>>
>>>>>> --
>>>>>> Lem -- MS-MVP
>>>>>>
>>>>>> To the moon and back with 2K words of RAM and 36K words of ROM.
>>>>>> http://en.wikipedia.org/wiki/Apollo_Guidance_Computer
>>>>>> http://history.nasa.gov/afj/compessay.htm
>>>>>>
>>>> The problem isn't obvious.
>>>>
>>>> When you were trying to sort out your other problems, did you do
>>>> anything with your LMHOSTS file on any of the PCs? What did you do?
>>>>
>>>> What are you using to control your network? Anything other than a
>>>> standard consumer-grade router?
>>>>
>>>> Did you add any protocols to the adapters on any of the the machines?
>>>> If you go to "View Network Connections" and right click on the icon for
>>>> the Local Area Connection and select Properties, is there anything else
>>>> listed other than these four items (it's OK if you don't have all 4)?
>>>> Client for Microsoft Networks
>>>> QoS Packet Scheduler
>>>> File and Printer Sharing for Microsoft Networks
>>>> Internet Protocol (TCP/IP)
>>>> --
>>>> Lem -- MS-MVP
>>>>
>>>> To the moon and back with 2K words of RAM and 36K words of ROM.
>>>> http://en.wikipedia.org/wiki/Apollo_Guidance_Computer
>>>> http://history.nasa.gov/afj/compessay.htm
>>>>
>> I haven't used SubInACL myself, but that could well be the source of
>> your problem.  If you can use System Restore to go back to a point prior
>> to using SubInACL, you might try it and see if that removes your network
>> problem.
>>
>> Otherwise, sure, go ahead and rename all of the machines and resetup the
>> network. It couldn't hurt.
>>
>> Sorry I couldn't offer more definitive help.
>> --
>> Lem -- MS-MVP
>>
>> To the moon and back with 2K words of RAM and 36K words of ROM.
>> http://en.wikipedia.org/wiki/Apollo_Guidance_Computer
>> http://history.nasa.gov/afj/compessay.htm
>>