Dear all,

I have 3 pc's in a single network, in a single workgroup named MSHOME, and
one wireless router / hub:
OLDONE Win xp home sp3 192.168.1.4 wireless
BUREAU Win xp home sp3 192.168.1.2 ethernet
HANONM Win vista home sp1 192.168.1.3 ethernet

Submask is 255.255.255.0
Router IP is 192.168.1.1
PC IP's are given by router dhcp.
Netbios on tcp/ip is set to default (dhcp).

The firewalls are disabled on all computers.

All pc's can surf on the internet.
Pinging from any computer to any computer on IP address works. (including
bureau)
Pinging from any computer to any computer on computer name also works.
(including bureau)
Guest account is enabled on all computers.
Username and password are the same on all pc's.

BUT I have a LAN problem: when browsing entire network/MSHOME workgroup:
* from oldone and hanonm-> I see computers oldone and hanonm, but not bureau
* from bureau: I get the following message (FRENCH):
Mshome n'est pas accessible. Vous ne disposez peut-être pas des
autotisations nécessaires pour utiliser cette ressource réseau. Contactez
l'administrateur de ce serveur pour savoir si vous disposez des
autorisations d'accès.
La liste des serveurs de groupe de travail n'est pas disponible
actuellement.

Which can be translated as:
Mshome is not accessible. You have perhaps not autotisations to use this
network resource. Contact the administrator of this server to find out if
you have access permissions.
The list of workgroup servers is currently unavailable.

Any hint?


Regards,
Alain

Hi
Check the Guest account permissions make sure it is allowed to read/write,
what ever you deem as necessary.
Make sure that all computers Firewalls are set to allow communication and
sharing.
In general
Vista File and Printer Sharing-
http://technet.microsoft.com/en-us/l.../bb727037.aspx
Windows XP File Sharing -
http://support.microsoft.com/default...b;en-us;304040
Printer Sharing XP -
http://www.microsoft.com/windowsxp/u...utt_july2.mspx
Windows Native Firewall setting for Sharing XP -
http://support.microsoft.com/kb/875357
Windows XP patch for Sharing with Vista -
http://support.microsoft.com/kb/922120
Jack (MVP-Networking).


"Alain Bourgeois" <(E-Mail Removed)> wrote in message
news:4978e881$0$2862$(E-Mail Removed)...
> Dear all,
>
> I have 3 pc's in a single network, in a single workgroup named MSHOME, and
> one wireless router / hub:
> OLDONE Win xp home sp3 192.168.1.4 wireless
> BUREAU Win xp home sp3 192.168.1.2 ethernet
> HANONM Win vista home sp1 192.168.1.3 ethernet
>
> Submask is 255.255.255.0
> Router IP is 192.168.1.1
> PC IP's are given by router dhcp.
> Netbios on tcp/ip is set to default (dhcp).
>
> The firewalls are disabled on all computers.
>
> All pc's can surf on the internet.
> Pinging from any computer to any computer on IP address works. (including
> bureau)
> Pinging from any computer to any computer on computer name also works.
> (including bureau)
> Guest account is enabled on all computers.
> Username and password are the same on all pc's.
>
> BUT I have a LAN problem: when browsing entire network/MSHOME workgroup:
> * from oldone and hanonm-> I see computers oldone and hanonm, but not
> bureau
> * from bureau: I get the following message (FRENCH):
> Mshome n'est pas accessible. Vous ne disposez peut-être pas des
> autotisations nécessaires pour utiliser cette ressource réseau. Contactez
> l'administrateur de ce serveur pour savoir si vous disposez des
> autorisations d'accès.
> La liste des serveurs de groupe de travail n'est pas disponible
> actuellement.
>
> Which can be translated as:
> Mshome is not accessible. You have perhaps not autotisations to use this
> network resource. Contact the administrator of this server to find out if
> you have access permissions.
> The list of workgroup servers is currently unavailable.
>
> Any hint?
>
>
> Regards,
> Alain
>
>

The problem is a network browsing only:
* ping works
* file sharing also works if \\computername\share is used!


"Jack (MVP-Networking)." <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi
> Check the Guest account permissions make sure it is allowed to read/write,
> what ever you deem as necessary.
> Make sure that all computers Firewalls are set to allow communication and
> sharing.
> In general
> Vista File and Printer Sharing-
> http://technet.microsoft.com/en-us/l.../bb727037.aspx
> Windows XP File Sharing -
> http://support.microsoft.com/default...b;en-us;304040
> Printer Sharing XP -
> http://www.microsoft.com/windowsxp/u...utt_july2.mspx
> Windows Native Firewall setting for Sharing XP -
> http://support.microsoft.com/kb/875357
> Windows XP patch for Sharing with Vista -
> http://support.microsoft.com/kb/922120
> Jack (MVP-Networking).
>
>
> "Alain Bourgeois" <(E-Mail Removed)> wrote in message
> news:4978e881$0$2862$(E-Mail Removed)...
>> Dear all,
>>
>> I have 3 pc's in a single network, in a single workgroup named MSHOME,
>> and one wireless router / hub:
>> OLDONE Win xp home sp3 192.168.1.4 wireless
>> BUREAU Win xp home sp3 192.168.1.2 ethernet
>> HANONM Win vista home sp1 192.168.1.3 ethernet
>>
>> Submask is 255.255.255.0
>> Router IP is 192.168.1.1
>> PC IP's are given by router dhcp.
>> Netbios on tcp/ip is set to default (dhcp).
>>
>> The firewalls are disabled on all computers.
>>
>> All pc's can surf on the internet.
>> Pinging from any computer to any computer on IP address works. (including
>> bureau)
>> Pinging from any computer to any computer on computer name also works.
>> (including bureau)
>> Guest account is enabled on all computers.
>> Username and password are the same on all pc's.
>>
>> BUT I have a LAN problem: when browsing entire network/MSHOME workgroup:
>> * from oldone and hanonm-> I see computers oldone and hanonm, but not
>> bureau
>> * from bureau: I get the following message (FRENCH):
>> Mshome n'est pas accessible. Vous ne disposez peut-être pas des
>> autotisations nécessaires pour utiliser cette ressource réseau. Contactez
>> l'administrateur de ce serveur pour savoir si vous disposez des
>> autorisations d'accès.
>> La liste des serveurs de groupe de travail n'est pas disponible
>> actuellement.
>>
>> Which can be translated as:
>> Mshome is not accessible. You have perhaps not autotisations to use this
>> network resource. Contact the administrator of this server to find out if
>> you have access permissions.
>> The list of workgroup servers is currently unavailable.
>>
>> Any hint?
>>
>>
>> Regards,
>> Alain
>>
>>
>

Sorry,

the problem is NOT file sharing. Samba will not solve anything: sharing
works already correctly. It is a pure network browsing problem (see all pc's
in same workgroup, I don't know other softwares doing this). And if I have
to create shortcuts to each pc, this is not a solution.
"phaedrus06" <(E-Mail Removed)> wrote in message
news(E-Mail Removed)...
>
> I know this sucks but the most common problem with Windows file sharing
> is, well, Windows. It sounds like you did everything correctly and you
> were rather thorough, but Windows is unfortunately broken. How it
> happens can be one of many ways like registry errors, software
> conflicts, or maybe your OS is just old (an OS's quality can naturally
> decay with time, usually over three years). I hate to tell you but the
> best solution is probably a reinstall. I don't like it and reluctantly
> tell my clients that is a good idea because rarely if ever should one
> have to reinstall an OS to fix a problem.
>
> What I would recommend in the meantime, since frankly no one likes to
> reinstall, is to create a Run shortcut on your desktop pointing to the
> computer you are having difficultly browsing. Either that or use
> freeware file sharing software instead of Windows which would be more
> reliable and faster. I personally think Samba is a good one to use but
> you can Google for others if you like.
>
> Some quick fixes you can try are:
>
> registry/file cleaning
>
> 2 chkdsk /r from the CLI
>
> 3 rebuilding the TCP stack on the afflicted PC which is basically
> uninstalling then reinstalling the TCP/IP protocol
>
> 4 check Windows for file integrity (you will need the Windows install
> disk) using SFC /scannow from the Run line
>
> 5 Lastly check the router or network device for any settings you may
> have missed. Sometimes the routers are bad themselves and switching
> them with another will help but not always. In your case the problem
> seems to be with Windows.
>
>
> Hope it helps.
>
>

None of these allow me to browse network.
"phaedrus06" <(E-Mail Removed)> wrote in message
news(E-Mail Removed)...
>
> Well when I was referring to file sharing I meant all aspects of it
> including browsing as you were mentioning which is the problem. Did you
> try any of the fixes I mentioned? They are all useful in their own way
> and until you try it you won't know it can help you.
>
> Also why not create a shortcut to your shared folder for network
> browsing if it works as you say? Even if regular browsing doesn't work
> at least you have that until you can figure something out. Besides
> sometimes as I mentioned before Windows just plain sucks and doesn't
> work no matter what you do so a reinstall may be necessary if you REALLY
> NEED that one network browser. Otherwise if you don't need the normal
> browser then just make a shortcut on the Desktop or try the previous
> solutions. Hope you find something.
>
>

* Is there a way to set a log level, and so to track what happens when
browsing workgroup "mshome"? Or to sniff network on a particular port?

Alain - I have EXACTLY the same problem.
These are new Dell PC with XP installed.
Everything was working fine - suddenly 1 PC is barred
from the workgroup exactly as you described.

See my separate post which I sent before noting your thread.


Alain Bourgeois wrote:
> Sorry,
>
> the problem is NOT file sharing. Samba will not solve anything: sharing
> works already correctly. It is a pure network browsing problem (see all pc's
> in same workgroup, I don't know other softwares doing this). And if I have
> to create shortcuts to each pc, this is not a solution.
> "phaedrus06" <(E-Mail Removed)> wrote in message
> news(E-Mail Removed)...
>> I know this sucks but the most common problem with Windows file sharing
>> is, well, Windows. It sounds like you did everything correctly and you
>> were rather thorough, but Windows is unfortunately broken. How it
>> happens can be one of many ways like registry errors, software
>> conflicts, or maybe your OS is just old (an OS's quality can naturally
>> decay with time, usually over three years). I hate to tell you but the
>> best solution is probably a reinstall. I don't like it and reluctantly
>> tell my clients that is a good idea because rarely if ever should one
>> have to reinstall an OS to fix a problem.
>>
>> What I would recommend in the meantime, since frankly no one likes to
>> reinstall, is to create a Run shortcut on your desktop pointing to the
>> computer you are having difficultly browsing. Either that or use
>> freeware file sharing software instead of Windows which would be more
>> reliable and faster. I personally think Samba is a good one to use but
>> you can Google for others if you like.
>>
>> Some quick fixes you can try are:
>>
>> registry/file cleaning
>>
>> 2 chkdsk /r from the CLI
>>
>> 3 rebuilding the TCP stack on the afflicted PC which is basically
>> uninstalling then reinstalling the TCP/IP protocol
>>
>> 4 check Windows for file integrity (you will need the Windows install
>> disk) using SFC /scannow from the Run line
>>
>> 5 Lastly check the router or network device for any settings you may
>> have missed. Sometimes the routers are bad themselves and switching
>> them with another will help but not always. In your case the problem
>> seems to be with Windows.
>>
>>
>> Hope it helps.
>>
>>
>
>

The solution to the problem:
Although nod32 fw/av was disabled, it seems incoming udp was blocked.
The computer browsing network has sent requests, but udp answers from other
computers were blocked. There was a checkbox in nod32 network config, and it
works now. I didn't change anything to network config.



"David K" <(E-Mail Removed)> wrote in message
news:%23Vw3p%(E-Mail Removed)...
> Alain - I have EXACTLY the same problem.
> These are new Dell PC with XP installed.
> Everything was working fine - suddenly 1 PC is barred
> from the workgroup exactly as you described.
>
> See my separate post which I sent before noting your thread.
>
>
> Alain Bourgeois wrote:
>> Sorry,
>>
>> the problem is NOT file sharing. Samba will not solve anything: sharing
>> works already correctly. It is a pure network browsing problem (see all
>> pc's in same workgroup, I don't know other softwares doing this). And if
>> I have to create shortcuts to each pc, this is not a solution.
>> "phaedrus06" <(E-Mail Removed)> wrote in message
>> news(E-Mail Removed)...
>>> I know this sucks but the most common problem with Windows file sharing
>>> is, well, Windows. It sounds like you did everything correctly and you
>>> were rather thorough, but Windows is unfortunately broken. How it
>>> happens can be one of many ways like registry errors, software
>>> conflicts, or maybe your OS is just old (an OS's quality can naturally
>>> decay with time, usually over three years). I hate to tell you but the
>>> best solution is probably a reinstall. I don't like it and reluctantly
>>> tell my clients that is a good idea because rarely if ever should one
>>> have to reinstall an OS to fix a problem.
>>>
>>> What I would recommend in the meantime, since frankly no one likes to
>>> reinstall, is to create a Run shortcut on your desktop pointing to the
>>> computer you are having difficultly browsing. Either that or use
>>> freeware file sharing software instead of Windows which would be more
>>> reliable and faster. I personally think Samba is a good one to use but
>>> you can Google for others if you like.
>>>
>>> Some quick fixes you can try are:
>>>
>>> registry/file cleaning
>>>
>>> 2 chkdsk /r from the CLI
>>>
>>> 3 rebuilding the TCP stack on the afflicted PC which is basically
>>> uninstalling then reinstalling the TCP/IP protocol
>>>
>>> 4 check Windows for file integrity (you will need the Windows install
>>> disk) using SFC /scannow from the Run line
>>>
>>> 5 Lastly check the router or network device for any settings you may
>>> have missed. Sometimes the routers are bad themselves and switching
>>> them with another will help but not always. In your case the problem
>>> seems to be with Windows.
>>>
>>>
>>> Hope it helps.
>>>
>>>
>>