Still screwed sharing folders on XP Pro

[jim]

After a complete re-install, I am still screwed trying to share folders on
the local network. Here are the specifics - please let me know if I am
missing anything.

-----

2 PCs ("A" an older installation and "B" the new installation of XP Pro)

-----

both XP Pro (fully patched)

-----

both in "WORKGROUP"

-----

both have File and Printer Sharing installed and enabled

-----

neither use passwords on the login

-----

both have Windows Firewall enabled with an exception for file and printer
sharing

-----

neither has a 3rd party firewall

-----

PC A can ping B with no problem

-----

PC A can see PC B but cannot access the shared folders...
"\\computername 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."

 

[Guest]

hi jim....try running the network wizard on pc A. also make sure they use
same network masks and same ip address range (this is now if you assign
dedicated ip addresses for each pc.

 

[josh]

After a complete re-install, I am still screwed trying to share folders on
the local network. Here are the specifics - please let me know if I am
missing anything.

-----

2 PCs ("A" an older installation and "B" the new installation of XP Pro)

-----

both XP Pro (fully patched)

-----

both in "WORKGROUP"

-----

both have File and Printer Sharing installed and enabled

-----

neither use passwords on the login

-----

both have Windows Firewall enabled with an exception for file and printer
sharing

-----

neither has a 3rd party firewall

-----

PC A can ping B with no problem

-----

PC A can see PC B but cannot access the shared folders...
"\\computername 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 could be wrong but i thought whenever you were in a workgroup like
this you had to have username and passwords and had to use them to
access eachothers files????

 

[josh]

I could be wrong but i thought whenever you were in a workgroup like
this you had to have username and passwords and had to use them to
access eachothers files????

example:

Computer A's main user is Josh and his password is j0$h

Computer B's main user is Chris and his password is Chr!$

Don't you have to have a user account Josh, and a User account Chris
on both computers with the same passwords...

Clearing up my last statement, again I might be wrong... but this is
what I was taught in my XP class

 

[josh]

example:

Computer A's main user is Josh and his password is j0$h

Computer B's main user is Chris and his password is Chr!$

Don't you have to have a user account Josh, and a User account Chris
on both computers with the same passwords...

Clearing up my last statement, again I might be wrong... but this is
what I was taught in my XP class

Even Clearer...

sorry i keep realizing that this could be mistaken....

Computer A would have
Josh - j0$h
and
Chris -Chr!$

Computer B would also have
Chris - Chr!$
and
Josh - j0$h


Still... not sure if im 100% correct here

 

[jim]

A has a dedicated ip of 192.168.1.233 and a network mask of 255.255.255.0

A has a static ip showing 192.168.1.2 and a network mask of 255.255.255.0

I ran the network wizard on both PCs.

A can see the shares on B, but when I click on one ("shared"), I get
"\\B\shared is not accessible. You might not have permission to use the
network resource. Contact the administrator to find out of you have access
permissions. The network path was not found."

I turned off simple file sharing on B. I un-shared "c:\shared". Then I
shared the "c:\shared" folder as "sharedx", slecting all permissions for
"everyone" using the non-simple sharing screens and I still get the same
error.

I uninstalled and re-installed the "file and Printer sharing" service on B's
nic. I re-enabled simple file sharing on B. I re-shared B's "c:\shared" as
"shared with all having all permissions.And, now I get "\\B\shared is not
accessible. You might not have permission to use the network resource.
Contact the administrator to find out of you have access permissions. not
enough server storage is available to process this command."

Odd as A has 4GB RAM and B has 3GB RAM with damned little running in the
background.

I sniffed around and found a Microsoft article on the latest error messge
and did as it said - increasing the IRPStackSize registry entries to 18 for
A and 15 for B with no changes.

I even tried turning off the Windows firewall on B to no avail.

There is a major ****ing problem here....and I'm not convinced that it is
me.

jim

 

[jim]

I kicked both PCs IRQStackSize DWORD values in the registry to the max value
of 50 (decimal) and I am now getting....\\B\shared is not accessible. You
might not have permission to use the network resource. Contact the
administrator to find out of you have access permissions. The network path
was not found."

B shows A the share in windows explorer. So how the hell can the path not
be found?

jim

 

[jim]

I re-installed motherboard drivers, nic drivers.....still nothing.

jim

 

[Guest]

Since "B" is the new installation, all "Services" are probably still at
"default" settings.
Try comparing "B"s services to "A"s services.
i.e. - Is "Computer Browser" service, etc., turned "On" on "A"?

 

[Malke]

After a complete re-install, I am still screwed trying to share folders on
the local network. Here are the specifics - please let me know if I am
missing anything.

2 PCs ("A" an older installation and "B" the new installation of XP Pro)

both XP Pro (fully patched)

both in "WORKGROUP"

both have File and Printer Sharing installed and enabled

neither use passwords on the login

both have Windows Firewall enabled with an exception for file and printer
sharing

neither has a 3rd party firewall

(snippage)

1. Turn off Simple Sharing on both machines from Control Panel>Folder
Options>View tab.

2. Create identical user account *and* assign passwords. They need to
match on both machines although you don't need to be logged into the
same account on both machines for successful sharing. Use control
userpasswords2 to automatically log into a user account if desired (will
go directly to that account's Desktop).

Configure Windows to Automatically Login (MVP Ramesh) -
http://windowsxp.mvps.org/Autologon.htm


Malke

 

[jim]

(snippage)

1. Turn off Simple Sharing on both machines from Control Panel>Folder
Options>View tab.

2. Create identical user account *and* assign passwords. They need to
match on both machines although you don't need to be logged into the same
account on both machines for successful sharing. Use control
userpasswords2 to automatically log into a user account if desired (will
go directly to that account's Desktop).

Configure Windows to Automatically Login (MVP Ramesh) -
http://windowsxp.mvps.org/Autologon.htm

Thanks Mallke, but I don't want to hack around it, I really want to know
what is going on here.

I have 3 PCs on my home LAN. The first 2 (Z & A) have been here for a
couple of years and use XP Pro and have never needed to share logins to
access each other's files when shared using simple file sharing and allowing
access to all users.

This 3rd PC (B) is also XP Pro, and can see and manipulate the shared files
and folders on Z & A. And, while Z & A can see B on the network, and can
even see the folders being shared by B, any attempt to open those shared
folders meets with failure.

I just renamed the workgroup on each PC and still no sharing. I then tried
to map a drive to C$ on B and was shown a login screen for B\Guest and asked
for the password for the Guest account.

Well, there isn't one. The guest account on B has NEVER been enabled and
has NEVER had a password set. It has never been used. So, why would XP ask
me for the Guest account login to access the C$ share?

I tried the same thing with the "shared" folder on B with the same dialog
popping up. If you hit enter (as there is no password and the Guest account
has never been active) the screen does not go away.

There is no password on the main account, and using it also does not make
the login screen go away when trying to map a drive.

<< pause while i set a password on B's main/only account and reboot it>>

Nope - still no luck. I get the same error with "The network path was not
found." as an explanation.

If the network path was not found, how am I seeing it in windows explorer?
I have changed its name several times to make sure that it is getting picked
up on the network.

Son-of-a-bitch! You'd think XP would actually work (or at least tell you
why it isn't in a way that would allow you to fix whatever is wrong) after
being out this many years.

jim

 

[jim]

I found what was screwing up networking for me, and it wasn't XP (my
apologies to Microsoft).

It was NOD32, and antivirus app put out by eset. Take that off and no
problems. Put it back and you are back at square one.

Granted, Eset has a more up to date version out than the one I am using from
last year - but shouldn't a product licensed for 2 years actually work for 2
years (or at least update itself properly)?

Well, I'm off to try the new version. I'll let you know in a few minutes if
it also fks up my network.

Thanks for all of the posts!

jim

 

[smlunatick]

I found what was screwing up networking for me, and it wasn't XP (my
apologies to Microsoft).

It was NOD32, and antivirus app put out by eset. Take that off and no
problems. Put it back and you are back at square one.

Granted, Eset has a more up to date version out than the one I am using from
last year - but shouldn't a product licensed for 2 years actually work for 2
years (or at least update itself properly)?

Well, I'm off to try the new version. I'll let you know in a few minutes if
it also fks up my network.

Thanks for all of the posts!

jim







- Show quoted text -

Most newer anti-virus systems (McAfee and Norton, along with NOD) not
include a module to prevent Internet worms from running. These
modules behave exactly like firewalls and you must locate the settings
to "tweak" them for your local network shares.

 

[jim]

Most newer anti-virus systems (McAfee and Norton, along with NOD) not
include a module to prevent Internet worms from running. These
modules behave exactly like firewalls and you must locate the settings
to "tweak" them for your local network shares.

I looked but didn't see where to do this. I even tried turning off ALL
functions that allowed themselves to be de-activated and it still blocked
me.

I sent an email to Eset but haven't heard anything back yet.

I'll update this thread as soon as they ;et me know something.

jim

 

[smlunatick]

I looked but didn't see where to do this. I even tried turning off ALL
functions that allowed themselves to be de-activated and it still blocked
me.

I sent an email to Eset but haven't heard anything back yet.

I'll update this thread as soon as they ;et me know something.

jim- Hide quoted text -

- Show quoted text -

Not familiar with Eset but I know that McAfee's worm blocking module
does not turn completely off when you "disable" it. It seem that you
must uninstall it.