Problem accessing files in one direction between computers in a Windows XP workgroup.

  • Thread starter Thread starter John Monahan
  • Start date Start date
J

John Monahan

Hope somebody out there can help. I spent the whole weekend on this with no
success. I have looked over this newsgroup and not seen this kind of
problem.

I have two standard Window XP machines. All up to date with downloads etc.
They are connected to the internet through a Netgear (RT314) gateway router.
Both computers access the internet fine. The problem is looking at files on
each other computer.

In the case of computer A. I can see and access files on computer B no
problem if that folder is configured as shared. (I have ICF off on both
machines, also firewalls off for anti-virus software on both machines).

For the reverse direction however I can see folders on computer A but cannot
open them. I get the following message:-
\\computerA\folderxxx is not accessable . You might not have permission to
use this network resource.Contact the administrator to find out if you have
access permisions...

What has me baffeled is both computers are setup essentialy the same
software wise. I am the administrator on both. I set file sharing to
"everyone" for the relevent folders on each machine. I can ping in both
directions no problem. I am only using TCP/IP,Client for Microsoft Networks,
and File and Printer Sharing. I tried adding NetBEUI, no effect.

Suggestions please
 
Pinging but being unable to access files usually means that a firewall is
present on the computer that won't share its resources with the other.
 
Hi John
This probably wont help you .......but I am experiencing exactly the same same symtoms as you, I am also seeking advice on this problem, had the difficulty now for three weeks.........I shall be keeping an anxious eye on the preceedings in this newsgroup for anyone who can offer some advice
rgards ....henry hodgetts
 
You didn't say, but is the Netgear device also a firewall?
You may want to look into the Microsoft file sharing ports
needed to reach a share through a firewall . .

The NetBIOS ports, 137-139. I'm looking at a Pix at the
moment, which I have bundled the NetBIOS ports, so I
cannot be more specific. I allow UDP and TCP through, when
needed.
The other gotcha that often gets fogotten is the "newer
style" Win2000 and above port 445. Take a look at that!
Here's one of many links on the 'net to learn what port is
what:
http://www.iss.net/security_center/advice/Exploits/Ports/de
fault.htm

Or better yet, do a search for "well known ports", and
you'll have more info than you need.

Disclaimer: Be VERY CAREFUL opening up NetBIOS to the
internet, or anywhere else you do not wish to invite the
worst kind of visitors. NetBIOS is the ONE thing you want
to keep people out of, from any untrusted source.

Ping is a rudimentary check, does nothing definitive,
other than if you CAN ping and get a reply with success,
it only means there is a route from one point to another.
When "ping" fails, it tells you very little, as anything
can prevent ping from working - no route, blocked by a
firewall, etc. Ping is a suite all its own, and firewalls
can be configured to allow/disallow it through (and back).
 
Back
Top