Re: Can't see laptop on MSHOME workgroup
- From: Chuck <none@xxxxxxxxxxx>
- Date: 7 Jul 2005 16:19:02 -0500
On Thu, 7 Jul 2005 13:41:02 -0700, "Chris D." <ChrisD@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote:
>"Chuck" wrote:
>
>> On Thu, 7 Jul 2005 12:08:20 -0700, "Jerry" <NoSpamChiefZeke@xxxxxxx> wrote:
>>
>> >"Chris D." <ChrisD@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> >news:4F25E297-66B4-4303-A0AF-8C7DBFCFAC75@xxxxxxxxxxxxxxxx
>> >> Hi guys...I have 2 desktop PCs, and one laptop all connected to my router.
>> >> I
>> >> have setup all three machines to be a member of the default MSHOME
>> >> workgroup.
>> >> Additionally, I have turned on file-sharing for different drives on all
>> >> three
>> >> machines. The 2 desktops work flawlessly...I can easily transfer files
>> >> from
>> >> one to the other. The laptop, however, is the problem. Although the two
>> >> desktops show that the laptop is available as a worgroup computer, when I
>> >> try
>> >> to access the laptop from either of the PCs, I get an error message
>> >> stating
>> >> that I apparently do not have permissions to access the laptop. I went
>> >> back
>> >> in the laptop to doublecheck that I indeed was sharing several folders,
>> >> but
>> >> they are not accessible from the PCs. Is there some sort of permissions
>> >> that
>> >> I should be checking on the laptop.????
>>
>> >For security reasons you should not be using the default MSHOME as your
>> >workgroup - the whole world knows this and many willing to do you harm will
>> >exploit your use of MSHOME.
>> >
>> >Is the firewall on all three setup to recognize the workgroup correctly?
>>
>> Jerry,
>>
>> The workgroup name just controls what computers get displayed in the root of
>> Network Neighborhood. From any given computer, all computers in the same
>> workgroup (domain) as that computer will display there. Any computer in a
>> different domain (workgroup) will be visible under Entire Network - Microsoft
>> Windows Network.
>>
>> Since the computers are inside a NAT router, the workgroup isn't visible to the
>> outside world anyway.
>>
>> You do need to ensure that all computers are in the same workgroup, though.
>>
>> Besides a firewall configuration, which is a valid concern in addition to the
>> restrictanonymous setting (even though the firewall is NOT sensitive to
>> workgroup), a third possibility would be a browser conflict. Use browstat, run
>> from each computer, to diagnose a browser conflict.
>> <http://nitecruzr.blogspot.com/2005/05/browstat-utility-from-microsoft.html>
>Here is browstat of the server:
>
>Microsoft Windows XP [Version 5.1.2600]
>(C) Copyright 1985-2001 Microsoft Corp.
>
>C:\Documents and Settings\Chris D>cd Desktop
>
>C:\Documents and Settings\Chris D\Desktop>browstat status
>
>
>Status for domain MSHOME on transport
>\Device\NetBT_Tcpip_{DD2A07A4-EC9D-4BD1-88
>05-BFA47D12F4EF}
> Browsing is active on domain.
> Master browser name is: OLDFAITHFUL
>Could not open key in registry, error = 5 Unable to determine build
>of br
>owser master: 5
> \\\\OLDFAITHFUL . Version:05.01 Flags: 51203 NT POTENTIAL MASTER
> 1 backup servers retrieved from master OLDFAITHFUL
> \\OLDFAITHFUL
> There are 3 servers in domain MSHOME on transport
>\Device\NetBT_Tcpip_{DD2A0
>7A4-EC9D-4BD1-8805-BFA47D12F4EF}
> There are 1 domains in domain MSHOME on transport
>\Device\NetBT_Tcpip_{DD2A0
>7A4-EC9D-4BD1-8805-BFA47D12F4EF}
Chris,
Browstat is most useful when run from 2 or more computers, and the results
compared.
Is OldFaithful the server, or one of the clients?
The "error = 5" is a possible problem. Since you say you checked (changed?)
restrictanonymous, did you check (change?) it on OldFaithful, or on the other
computer(s)? Or is there maybe another problem? You may have to solve multiple
problems.
<http://nitecruzr.blogspot.com/2005/07/restrictanonymous-and-your-server.html>
Please provide "browstat status" and "ipconfig /all" for all 3 computers, and
list details about the devices (computers and router). Diagnosis of your
problem will be more successful with the necessary details known, so we don't
have to guess.
<http://nitecruzr.blogspot.com/2005/06/background-information-useful-in.html>
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>
--
Cheers,
Chuck MS-MVP [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck sonic net.
.
- Follow-Ups:
- Re: Can't see laptop on MSHOME workgroup
- From: Chris D.
- Re: Can't see laptop on MSHOME workgroup
- References:
- Can't see laptop on MSHOME workgroup
- From: Chris D.
- Re: Can't see laptop on MSHOME workgroup
- From: Jerry
- Re: Can't see laptop on MSHOME workgroup
- From: Chuck
- Re: Can't see laptop on MSHOME workgroup
- From: Chris D.
- Can't see laptop on MSHOME workgroup
- Prev by Date: RE: Can't see laptop on MSHOME workgroup
- Next by Date: Re: Can't see laptop on MSHOME workgroup
- Previous by thread: Re: Can't see laptop on MSHOME workgroup
- Next by thread: Re: Can't see laptop on MSHOME workgroup
- Index(es):
Relevant Pages
|
