File and Print Sharing Problem.

[JustMe]

I'm having a small networking problem I was hoping someone could shed some
light on.

While attempting to add a network printer to a new PC, I noticed I wasn't
able to browse to it. Investigation reveals I'm not able to see the computer
that has the printer but I can't find any reason for it.

Here's the setup:

Have 2 PC's running Win2k Pro sp4 on a small workgroup connected by a
Linksys router. Both of these PC's (A&B) have communicated and been able to
share resources for the past 6 years without problem. I added a new PC (C)
running WinXP Home sp2. The installation went fine till I attempted to share
the printer on (A).

All systems have 3 identical accounts and matching PW's. File and Print
Sharing is installed and bound on each NIC. System (B) has been sharing the
printer attached to (A) for years. All systems can access the Internet via
the router. When browsing for shares, System (B) can see all systems, System
(A) can see (A) & (B) but system (C) sees nothing. It can see the network
but, not any resources attached. FWIW, NetBEUI is enabled on (A) and (B) but
not (C). Yeah, I know I don't need it but I set it up that way years ago
when all I had was a hub. I wanted to make sure I had a network when @Hole
crapped out and I couldn't find the DHCP server. Windows Firewall is turned
off on system (C) and I never installed one on the other systems.

If I log in on system (A) and search for computers using IP, I can't find
(B) or (C). If I search for computer name I can find (B) but not (C).

If I log in on system (B) and search for computers using IP, I can't find
(B) or (C). If I search for computer names I can find both (A) and (C).

If I log in on system (C) and search for computers using IP, I can't find
(A) or (B). If I search for computer names I can find (B) but not (A).

TIA for any insight into a solution anyone would care to share.

 

[JustMe]

I'm having a small networking problem I was hoping someone could shed some
light on.

While attempting to add a network printer to a new PC, I noticed I wasn't
able to browse to it. Investigation reveals I'm not able to see the computer
that has the printer but I can't find any reason for it.

Here's the setup:

Have 2 PC's running Win2k Pro sp4 on a small workgroup connected by a
Linksys router. Both of these PC's (A&B) have communicated and been able to
share resources for the past 6 years without problem. I added a new PC (C)
running WinXP Home sp2. The installation went fine till I attempted to share
the printer on (A).

All systems have 3 identical accounts and matching PW's. File and Print
Sharing is installed and bound on each NIC. System (B) has been sharing the
printer attached to (A) for years. All systems can access the Internet via
the router. When browsing for shares, System (B) can see all systems, System
(A) can see (A) & (B) but system (C) sees nothing. It can see the network
but, not any resources attached. FWIW, NetBEUI is enabled on (A) and (B) but
not (C). Yeah, I know I don't need it but I set it up that way years ago
when all I had was a hub. I wanted to make sure I had a network when @Hole
crapped out and I couldn't find the DHCP server. Windows Firewall is turned
off on system (C) and I never installed one on the other systems.

If I log in on system (A) and search for computers using IP, I can't find
(B) or (C). If I search for computer name I can find (B) but not (C).

If I log in on system (B) and search for computers using IP, I can't find
(B) or (C). If I search for computer names I can find both (A) and (C).

If I log in on system (C) and search for computers using IP, I can't find
(A) or (B). If I search for computer names I can find (B) but not (A).

TIA for any insight into a solution anyone would care to share.

Here's another small piece of the puzzle. Every document I've come across
indicated NetBEUI isn't necessary. Alright, I removed the checkmark next to
NetBEUI and restarted my win2k systems. Now I have no network. All WS's can
access the web under tcpip but No workstation can see any other. It's like
the workgroup is gone. I put NetBEUI back and I can share filed and printers
again, at least on the Win3k systems. Since NetBEUI isn't available on XP I
guess I know why I can't communicate to the WinXP system.

What did I miss? Any Idea's?

 

[Carey Holzman]

Replace NetBeui with IPX/SPX (included with XP) and see if that resolves
your issues.

Carey

 

[JustMe]

That thought crossed my mind. It's the only common transport protocol other
than IP which isn't working.
Thanx

 

[Carey Holzman]

Of course, you really can use just TCP/IP for everything if you want to.
Send me an email and I will walk you through the setup one-on-one if you
want.

(e-mail address removed)

 

[Carey Holzman]

Ok, remember to use this email address: (e-mail address removed)

Carey

 

[Guest]

I am having similar problems connecting a new dell running xp home with sp2
on it, connecting to an home xp sp1 version.

i can see both computers on the small home network from the sp2 system but
only able to access the system itself. I get computer not accessible. You
might not have permissions. The sp1 computer will only see itself.

This is so frustrating 95, 98, NT and 2000 were so similar for networking
and sharing i was able to sep up networks in my sleep.

what the heck do i do????

losing patience and time............help..

 

[Carey Holzman]

Send me an email and I'll walk you through it.

(e-mail address removed)

 

[JustMe]

Carey:

Thanks for the reminder about Protonic.com. I'd forgotton about them. With
their help I managed to get things working without NetBEUI. As it turns out
it was a two part problem. Had to force the XP system to become the master
browser and then had to reinstall the TCP stack on system (A). Once done,
everything worked as advertised.

 

[Guest]

Could you post the solution? I am having the same problem with a network I
am trying to setup.

I have 4 ws that can see all 5 ws and 1 (a) that sees only itself. I get an
error that I may not have rights to access that computer when trying to
connect to (a). I can ping every system and I get a response.

- Sam

 

[Chuck]

Could you post the solution? I am having the same problem with a network I
am trying to setup.

I have 4 ws that can see all 5 ws and 1 (a) that sees only itself. I get an
error that I may not have rights to access that computer when trying to
connect to (a). I can ping every system and I get a response.

- Sam

Sam,

Please start a new topic (with a different, and descriptive title) for help.
This will benefit both you, and the OP. And, it will help the helpers here find
your posts easier. What seems like the same problem to you may actually be
something different, when diagnosed.

 

[Carey Holzman]

Here you go:
www.careyholzman.com/net1.htm

Carey

 

[Guest]

Carey -

Thanks that worked wonderfully to network my printer connected to (a) yet I
still can't share files with (a). I still get the "you may not have rights
contact your system administrator" error.

 

[Carey Holzman]

What operating system does each PC run? When you get the error message, what
does it say exactly and what are you doing exactly to cause it?

Carey

 

[Eric Niewoehner]

Been dealing with this problem for several months on-and-off. Culprit?
Most likely WEP running on the Linksys wireless router. Turned off
WEP and F & P works like a charm. Left this problem with Linksys
support and they have yet to get back with me. My hunch is that their
is a bug in the Linksys algorithm that corrupts ACL verifications. For
that reason, I often received sporadic blockage to the workgroup, even
though I was a member of it. When the workgroup was accessed, was
refused access to network devices even though I held an equivalent
account on those devices.

Once WEP was removed, discovered some issues with authentication levels
to the Windows 2003 server that is on my network. Login failed because
I had set it to NTLMv5 authentication (done through Local Security
Policies). While theoretically this should not have been a problem
because all my workstations are Windows XP, reducing the level back down
to both LM and NTLMv5 negotiated solved the problem. Again, this may be
related to the Linksys router.

One option failed to resolve the WEP problem, an option that has often
solved problems in other networks I have administered. Tried adding a
WINS server to the network. Even that failed. The problem is quite
puzzling. Theoretically, NetBIOS (which is used to match Microsoft
computer names with an IP address) should be embedded in an TCP/IP
packet, which is embedded in the WEP shroud.

Since I scanned several other messages in this newsgroup, it appears the
problem first emerged with SP2. It is possible that SP2 conducts an
integrity assessment of the authentication packets to establish whether
they have been manipulated, and that the WEP manipulation of the Linksys
router apparently triggers a rejection. I leave that to Microsoft to
explain.

 

[Guest]

Carey -

Both machines run Win XP Home. WS A is connected via Ethernet to a D-Link
DI-524 and the printer we want to network. Laptop B connects via wireless
D-Link G630.

The error occurs after I click My Network Places then I click View
workgroup computers. WS A is visible now (It wasn't before running through
your tutorial) then I click on A and I get

"\\A is not accessible. You might not have permission to use this network
resource. Contact the administrator of this server to find out if you have
access permissions.

Access is denied"

I can access all shared files from WS A but I cannot see it from Laptop B.
I actually have two other laptops and a desktop all connecting via wireless
and all get the same error. All are running XP Home except one on XP Pro. I
just want to get one running for now and I think that will fix the rest.

-Sam

 

[Carey Holzman]

Have you tried resetting the router? There is usually a reset button on the
router.

Carey

 

[Guest]

No dice.

All other computers can communicate with each other both ways but none can
share files with A. Though printing doesn't seem to be a problem.

Sam

 

[Carey Holzman]

On "A":
Click Start, click Run, type: cmd (and hit enter)

Type: ipconfig /all >c:\ipconfig.txt (and hit enter)

Use Notepad to open c:\ipconfig.txt and copy and paste entire contents into
your next post.

Thanks,
Carey

 

[Carey Holzman]

Also, in the Administrative Tools in the Control Panel, ensure the TCP/IP
NetBios Helper service is running.

Also, please follow these steps:
http://www.careyholzman.com/xp/home/xphome-14.htm

Then, try to ping the A computer's IP address and tell me what happens. Try
to ping the A comptuers name and tell me what happens.

Also, tell me the exact error message, word for word, that you get and what
you are "exactly" doing that is causing it.

Thanks!
Carey