|
| If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|||||||
|
|
|
Thread Tools | Display Modes |
|
#16
January 29th 09, 10:24 PM
posted to microsoft.public.windowsxp.network_web
|
|||
|
|||
browsing workgroup doesn't work on one computer
* 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? 
|
| Ads |
|
#17
January 29th 09, 10:24 PM
posted to microsoft.public.windowsxp.network_web
|
|||
|
|||
|
browsing workgroup doesn't work on one computer
* 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?
|
|
#18
January 30th 09, 02:59 AM
posted to microsoft.public.windowsxp.network_web
|
|||
|
|||
|
browsing workgroup doesn't work on one computer
Alain Bourgeois;925987 Wrote: * 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? Use wireshark found at 'Wireshark: Go deep.' (http://www.wireshark.org) which is a free but good tool to do network diagnostics. Honestly though, I REALLY think your one Windows XP SP3 OS is frankly busted. It happens and I know that you don't want to reinstall but unless you can find the exact problem that is probably the best solution. Unless you are running a real server like 2003 or 2008 then Windows sucks for sharing and networking. The last thing I'll say is WINDOWS SUCKS FOR NETWORKING AND SHARING! Really I am sorry and am not trying to be annoying but unless you find the registry problem (the most likely culprit) you probably won't get it working. And if you did not try it already, the fixes previously mentioned a couple posts up could help you.
|
|
#19
January 30th 09, 02:59 AM
posted to microsoft.public.windowsxp.network_web
|
|||
|
|||
|
browsing workgroup doesn't work on one computer
Alain Bourgeois;925987 Wrote: * 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? Use wireshark found at 'Wireshark: Go deep.' (http://www.wireshark.org) which is a free but good tool to do network diagnostics. Honestly though, I REALLY think your one Windows XP SP3 OS is frankly busted. It happens and I know that you don't want to reinstall but unless you can find the exact problem that is probably the best solution. Unless you are running a real server like 2003 or 2008 then Windows sucks for sharing and networking. The last thing I'll say is WINDOWS SUCKS FOR NETWORKING AND SHARING! Really I am sorry and am not trying to be annoying but unless you find the registry problem (the most likely culprit) you probably won't get it working. And if you did not try it already, the fixes previously mentioned a couple posts up could help you.
|
|
#20
January 31st 09, 10:35 AM
posted to microsoft.public.windowsxp.network_web
|
|||
|
|||
|
browsing workgroup doesn't work on one computer
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" wrote in message news  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 a 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.
|
|
#21
January 31st 09, 10:35 AM
posted to microsoft.public.windowsxp.network_web
|
|||
|
|||
|
browsing workgroup doesn't work on one computer
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" wrote in message news 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 a 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.
|
|
#22
February 11th 09, 09:32 PM
posted to microsoft.public.windowsxp.network_web
|
|||
|
|||
|
browsing workgroup doesn't work on one computer
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" wrote in message ... 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" wrote in message news 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 a 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.
|
|
#23
February 11th 09, 09:32 PM
posted to microsoft.public.windowsxp.network_web
|
|||
|
|||
|
browsing workgroup doesn't work on one computer
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" wrote in message ... 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" wrote in message news 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 a 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.
|
|
| Thread Tools | |
| Display Modes | |
|
|
Linear Mode
