Re: Win2K shares not visible from one XP Pro machine

Tech-Archive recommends: Fix windows errors by optimizing your registry



On Mon, 30 Apr 2007 20:51:01 -0700, BenK <BenK@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

"Chuck" wrote:

On Mon, 30 Apr 2007 10:26:01 -0700, BenK <BenK@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

I've got a network with a Win2K Workstation serving a small Access database
from a share called "database". There is another Win2K machine and two WinXP
Pro machines that can access this computer by name or IP correctly. However,
I have a WinXP Pro machine that cannot view the shares by either IP or name.
It cannot even view its own shares by IP (works by name). The WinXP system
can ping any system on the network by name or IP. Doing "net view \\ip" of
the local machine does not work, but doing "net view \\name" does work.
Doing a "net view" of any other machine by name or IP fails with "System
Error 53". All machines have unique names and are in the same workgroup.
There is no domain present. IP addresses are assigned by DHCP from the
router. Guest account is enabled on the Win2K system housing the share and
the other 3 machines can connect just fine. because of the problem using
"net view \\name" for the local machine, I suspect the issue is with this
machine. I have tested with the WinXP firewall on and off, disabled
SpySweeper that is installed and disabled Symantec Anti-virus corporate to
test. None of these things have any effect.

You're on the right track. One of the most common causes of this problem would
be a misconfigured or overlooked personal firewall, or other security component.
Symantec products may contain an antiworm protection, that also can act as a
firewall and block traffic. There are other possibilities too.
<http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html>
http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html

Checked that, hence the reason I said I disabled the anti-virus and
anti-spyware software. I also notice that your response to me is the same as
numerous other you have posted in this forum. Did you read my original post
or stop after I said one machine couldn't see another? I don't mean to be
offensive and I'm sorry if it comes out that way, but after spending over 5
hours dealng with this problem so far and searching these groups and much of
the internet to no avail, rehashing what I have read and tried isn't fixing
my problem. Any other suggestions?

You noted having disabled Symantec. If you spend some time reading other
threads, you'll note that:
1) Symantec products don't always disable politely.
2) Some Symantec products contain other components, like antiworm protection,
which will act as a firewall, and block SMBs. Antiworm protection won't disable
with the firewall off switch.

When you talk about computers that can't see one another, you're talking about
blocked browser SMBs.
<http://nitecruzr.blogspot.com/2006/07/advanced-windows-networking-using.html>
http://nitecruzr.blogspot.com/2006/07/advanced-windows-networking-using.html
<http://nitecruzr.blogspot.com/2005/04/nt-browser-or-why-cant-i-always-see.html>
http://nitecruzr.blogspot.com/2005/04/nt-browser-or-why-cant-i-always-see.html

So you referred to having turned off the personal firewall (which may or may not
do anything). My article talks about a lot more than that, including
diagnostics that you can do on your own, or with help here.

If it offends you that I provide the same starting advice in a number of posts,
I apologise. But my initially cited article is relevant to your problem, and
I'll bet there are a few items in there that you haven't tried.

You can start with "error = 53", if you like.
<http://nitecruzr.blogspot.com/2005/06/mysterious-error-53-aka-name-not-found.html>
http://nitecruzr.blogspot.com/2005/06/mysterious-error-53-aka-name-not-found.html

--
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 mvps org.
.



Relevant Pages

  • Re: Win2K shares not visible from one XP Pro machine
    ... There is another Win2K machine and two WinXP ... Pro machines that can access this computer by name or IP correctly. ... I have a WinXP Pro machine that cannot view the shares by either IP or name. ... be a misconfigured or overlooked personal firewall, ...
    (microsoft.public.windowsxp.network_web)
  • Re: Upgrading to Retail WinXP Pro on top of an OEM Installation of
    ... If you have a problem on an individual PC, try disabling the Firewall first, ... I currently have a network of win2kpro, winxppro, winxphome ... I have an old desktop running WinXP Pro that I would ... unless I upgrade my wife's laptop from WinXP H-E to WinXP ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: Upgrading to Retail WinXP Pro on top of an OEM Installation of
    ... as apposed to Win default firewall that only blocks in, ... I currently have a network of win2kpro, winxppro, winxphome & ... I have an old desktop running WinXP Pro that I would like ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: Upgrading to Retail WinXP Pro on top of an OEM Installation of
    ... as apposed to Win default firewall that only blocks in, ... I currently have a network of win2kpro, winxppro, winxphome & ... I have an old desktop running WinXP Pro that I would like ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: xp security vulnerabilities?
    ... > I have recently changed from Win98SE to WinXP corp pro, ... You'll want to keep some kind of firewall ... site is helpful to beginners perhaps but I don't know anyone in the security ... If you intend to be connected for long periods of time I'd suggest getting a DSL router/modem that includes a built in firewalling facility of some kind. ...
    (microsoft.public.windowsxp.security_admin)