Puzzling nework behavior

  • Thread starter Thread starter Paul B
  • Start date Start date
P

Paul B

I had a 2 Win XP Home computer, one printer LAN running through a
broadband router with no problem. But the router died and had to
be replaced.

After reinstalling the printer drivers both computers can talk to
the printer. But that's where the reliability ends.

On boot, neither computer can access the other via LAN. I get a
permissions error. If I drop both firewalls my backup computer
then can see the main machine. Then if I put the firewalls back
up (kerio 2.15, btw), machine B STILL can see machine A in real
time!

Now to machine A. Machine A sees the LAN, "Mynet", but cannot
access it. I get the "no permissions" error msg.

I've spent a lot of time tinkering around and am getting
absolutely nowhere. I find this stuff very frustrating and what's
more I suspect it doesn't have to be so.

Anyway, any direction would be much appreciated.

Thanks,
p.
 
Paul B said:
I had a 2 Win XP Home computer, one printer LAN running through a
broadband router with no problem. But the router died and had to
be replaced.

After reinstalling the printer drivers both computers can talk to
the printer. But that's where the reliability ends.

On boot, neither computer can access the other via LAN. I get a
permissions error. If I drop both firewalls my backup computer
then can see the main machine. Then if I put the firewalls back
up (kerio 2.15, btw), machine B STILL can see machine A in real
time!

Now to machine A. Machine A sees the LAN, "Mynet", but cannot
access it. I get the "no permissions" error msg.

I've spent a lot of time tinkering around and am getting
absolutely nowhere. I find this stuff very frustrating and what's
more I suspect it doesn't have to be so.

Anyway, any direction would be much appreciated.

Thanks,
p.
Click to expand...
The best explanation would be that the two computers are blocking ICMP
packets, but the printer is not.
However, merely saying "permissions error" is very incomplete. You need to
quote the message verbatim.
Otherwise, you will get lots of advice that can be quite wide of the mark
(just as this one might be).

My initial stab would be to insure that each firewall is setup to allow ICMP
to enter the computer. This step
is sometimes called "file and printer sharing".

My second stab would be to insure that when I access a remote computer, I do
so via an account on the remote computer whose name and password is
identical to the account that I am using.

Jim
 
The best explanation would be that the two computers are blocking ICMP
packets, but the printer is not.
However, merely saying "permissions error" is very incomplete. You need to
quote the message verbatim.
Otherwise, you will get lots of advice that can be quite wide of the mark
(just as this one might be).

My initial stab would be to insure that each firewall is setup to allow ICMP
to enter the computer. This step
is sometimes called "file and printer sharing".

My second stab would be to insure that when I access a remote computer, I do
so via an account on the remote computer whose name and password is
identical to the account that I am using.

Jim
Click to expand...


The error dialog says ".... is not accessible. You might not have
permission to use this network resource. Contact the
administrator, blah blah.... The network path was not found".

I have my firewall set up to allow all traffic on the local net.
It's the third rule in priority, after localhost and DNS lookup.

I should have added in my post that I had this network working
last night. I fully expected it to be so today, but it's not.

I'd be really surprised if accounts across computers need to have
the same name and password. That doesn't sound right at all.

I just discovered something in my firewall that might be the
culprit. I have to run out right now but I'll post back in a
couple of hours about what I found.

Thanks,
p.
 
Paul B said:
The error dialog says ".... is not accessible. You might not have
permission to use this network resource. Contact the
administrator, blah blah.... The network path was not found".

I have my firewall set up to allow all traffic on the local net.
It's the third rule in priority, after localhost and DNS lookup.

I should have added in my post that I had this network working
last night. I fully expected it to be so today, but it's not.

I'd be really surprised if accounts across computers need to have
the same name and password. That doesn't sound right at all.

I just discovered something in my firewall that might be the
culprit. I have to run out right now but I'll post back in a
couple of hours about what I found.

Thanks,
p.
Click to expand...
It is merely easier to share files and printers across a network if you have
identical accounts on both. This is assuming that you are not using Guest
authentication.
You should consult the websites of MVP Jack or MVP Chuck for help with your
message. I have never had this problem myself thus I can't help with its
resolution.
Jim
 
The error dialog says ".... is not accessible. You might not have
permission to use this network resource. Contact the
administrator, blah blah.... The network path was not found".

I have my firewall set up to allow all traffic on the local net.
It's the third rule in priority, after localhost and DNS lookup.

I should have added in my post that I had this network working
last night. I fully expected it to be so today, but it's not.

I'd be really surprised if accounts across computers need to have
the same name and password. That doesn't sound right at all.

I just discovered something in my firewall that might be the
culprit. I have to run out right now but I'll post back in a
couple of hours about what I found.

Thanks,
p.
Click to expand...

I couldn't resist checking this out. There's a tab on the
firewall that I very rarely access, and it's a LAN override of
the user rules. I had setup a trusted zone there for the old
router, but hadn't updated it for the new. I just did so and I'm
networking swimmingly!

The implication is that the Allow All rule for the LAN's IP range
wasn't permissive enough to facilitate the network. I have no
reason why that would be. That rule should have carried the thing
without the Trusted Zone helping out, ISTM.

One practical question also remains. Now, in Windows Explorer I
see the shared folders on each computer, but I no longer have the
"Entire Network" entry, with (3) sub-entries like MS Windows
Networking. Not sure this matters, but it's weird.

Thanks,
p.
 
Back
Top