XP home network

[Paddy]

Have two XP Prof PCs (One is 1.8GHz Athlon ("A"); other is 1.8GHz Celeron
"B") connected by crossover CAT5 RJ45 into respective NICs.

I ran Network Wizard on "A" - made floppy and ran its netsetup on "B". All
seems OK.

Both are running Kaspersky Internet Security Suite - firewall on each set to
allow 169.168.0.0.

Both see each other and both see each other's shared folders.

Cable broadband modem on "A", shared (ICS) and working fine on "B" also for
internet and email etc.

"A" can access "B"'s shared folders.

HOWEVER here's the rub.

Not only can "B" see, but not access "A"'s shared folders, but NEITHER CAN
"A" access its own shared folders VIA the NETWORK.

It can access them directly as folders, but not via the network.

See http://paddymar.webng.com/Network-Folders2.jpg screen shot with notes.

Thanks

Paddy

 

[Paddy]

Both are running Kaspersky Internet Security Suite - firewall on each set
to allow 169.168.0.0.

Stoopid! I meant of course 192.168.0.0 - grand-daughter (3) was showing me
a new drawing .....

Paddy

 

[Chuck [MVP]]

Have two XP Prof PCs (One is 1.8GHz Athlon ("A"); other is 1.8GHz Celeron
"B") connected by crossover CAT5 RJ45 into respective NICs.

I ran Network Wizard on "A" - made floppy and ran its netsetup on "B". All
seems OK.

Both are running Kaspersky Internet Security Suite - firewall on each set to
allow 169.168.0.0.

Both see each other and both see each other's shared folders.

Cable broadband modem on "A", shared (ICS) and working fine on "B" also for
internet and email etc.

"A" can access "B"'s shared folders.

HOWEVER here's the rub.

Not only can "B" see, but not access "A"'s shared folders, but NEITHER CAN
"A" access its own shared folders VIA the NETWORK.

It can access them directly as folders, but not via the network.

See http://paddymar.webng.com/Network-Folders2.jpg screen shot with notes.

Thanks

Paddy

Paddy,

I'm going to bet that you have a browser conflict here. Let's look at logs from
"browstat status", "ipconfig /all", "net config server", and "net config
workstation", from each computer, so we can diagnose the problem. Read this
article, and linked articles, and follow instructions precisely (download
browstat!):
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>
http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp

--
Cheers,
Chuck, MS-MVP 2005-2007 [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.

 

[Paddy]

Paddy,

I'm going to bet that you have a browser conflict here. Let's look at
logs from
"browstat status", "ipconfig /all", "net config server", and "net config
workstation", from each computer, so we can diagnose the problem. Read
this
article, and linked articles, and follow instructions precisely (download
browstat!):
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>
http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp

Thanks, Chuck.

I'll do as you suggest and get back with the info you suggest. Teaching
tomorrow (Friday) so it will probably be the weekend.

Thanks again

Paddy


Paddy

 

[Paddy]

Paddy,

I'm going to bet that you have a browser conflict here. Let's look at
logs from
"browstat status", "ipconfig /all", "net config server", and "net config
workstation", from each computer, so we can diagnose the problem.

(snip)

Hi again Chuck - I stayed and dumped all the diagnostics you suggested -
they are here:

http://paddymar.webng.com/Network-Diagnostic-Dumps.zip

Summary of issue: "Athlon" is the "primary" PC with IP 192.168.0.1 and
shared cable modem;
"Celeron" is the "secondary" PC with IP 192.168.0.4. It uses the shared
modem quite happily.

"Athlon" can see and access all shared folders on "Celeron"

However, while the shared folders on "Athlon" can be seen by both PCs in
Network Neighbourhood, neither "Athlon" nor "Celeron" can access those
folders via the network, as shown:

http://paddymar.webng.com/Network-Folders2.jpg

Also, I ran all your suggested utilities while logged on to both PCs as
non-Admin user. However, the Celeron showed an "Access Denied" error with
"net config server" - it required me to log on as Admin. I added a note to
that effect on the bottom of the dump file Celeron-Net-Config-Server.txt

Thanks

Paddy

 

[Chuck [MVP]]

(snip)

Hi again Chuck - I stayed and dumped all the diagnostics you suggested -
they are here:

http://paddymar.webng.com/Network-Diagnostic-Dumps.zip

Summary of issue: "Athlon" is the "primary" PC with IP 192.168.0.1 and
shared cable modem;
"Celeron" is the "secondary" PC with IP 192.168.0.4. It uses the shared
modem quite happily.

"Athlon" can see and access all shared folders on "Celeron"

However, while the shared folders on "Athlon" can be seen by both PCs in
Network Neighbourhood, neither "Athlon" nor "Celeron" can access those
folders via the network, as shown:

http://paddymar.webng.com/Network-Folders2.jpg

Also, I ran all your suggested utilities while logged on to both PCs as
non-Admin user. However, the Celeron showed an "Access Denied" error with
"net config server" - it required me to log on as Admin. I added a note to
that effect on the bottom of the dump file Celeron-Net-Config-Server.txt

Thanks

Paddy

Paddy,

What OS is on each computer - XP Home, XP Pro, Vista? The "net config" command
does require administrative authority.

Both computers recognise Pats as the master browser ("Master browser name is:
PATS"), so it's not a segmented domain. But only one computer ("server") is
seen ("There are 1 servers in domain PATMAR").

You've most likely got a NetBT or personal firewall problem.
<http://nitecruzr.blogspot.com/2006/07/advanced-windows-networking-using.html>
http://nitecruzr.blogspot.com/2006/07/advanced-windows-networking-using.html

But the binding of NetBT to the OptusNet adapter, on Pats, could be a problem.
And it's certainly not what you should be doing. You don't want to connect
NetBT to the Internet. Try disabling that, to start.

--
Cheers,
Chuck, MS-MVP 2005-2007 [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.

 

[Paddy]

What OS is on each computer - XP Home, XP Pro, Vista? The "net config"
command
does require administrative authority.

Both running XP Pro SP2.

Should I re-run the utilities logged on as Admin? Or was the info
sufficient?

Both computers recognise Pats as the master browser ("Master browser name
is:
PATS"), so it's not a segmented domain. But only one computer ("server")
is
seen ("There are 1 servers in domain PATMAR").

You've most likely got a NetBT or personal firewall problem.
<http://nitecruzr.blogspot.com/2006/07/advanced-windows-networking-using.html>
http://nitecruzr.blogspot.com/2006/07/advanced-windows-networking-using.html

But the binding of NetBT to the OptusNet adapter, on Pats, could be a
problem.
And it's certainly not what you should be doing. You don't want to
connect
NetBT to the Internet. Try disabling that, to start.

Thanks, Chuck. Something to read, digest and have a look at.

I'll let you know what I find.

Paddy (networking babe-in-arms!)

 

[Paddy]

Thanks, Chuck. Something to read, digest and have a look at.

Some progress. I perused your articles, and tried some suggestions.
Everything seemed to check out. You suggested my personal firewall. It
seems to be it (although I'm baffled as to how - see sequence)

I uninstalled Kaspersky Internet Security Suite on "Pats". (Left Kaspersky
fully enabled on "Tets", because there was no problem with "Pats" accessing
"Tets" shared folders - only vice versa). Enabled Windows firewall on
"Pats".

Re-ran XP Network Wizard on both PCs. Bingo! Both can now see and access
each others' shared folders. Thus network etc settings appear OK.

Re-installed Kaspersky on "Pats". Bugger. Straight away, "Tets" can see
but not access "Pats" shared folders, but "Pats" can access "Tets" OK.
Seems Kaspersky firewall is the issue.

Uninstalled Kaspersky and re-ran Network Wizard. Back to both can see and
access each others' shared folders. Hmmmm. Kaspersky firewall on "Pats"
the problem?? Reinstall Kaspersky WITHOUT firewall component. Nup.
"Tets" can see but not access "Pats" shared folders, but "Pats" can access
"Tets" OK.

Uninstalled Kaspersky and re-ran Network Wizard. Back to both can see and
access each others' shared folders. Reinstall Kaspersky Anti-Virus
component ONLY. Nup. "Tets" can see but not access "Pats" shared folders,
but "Pats" can access "Tets" OK. It seems ANY installed component of
Kaspersky - not just firewall - block access from "Tets" to "Pats".

I have contacted Kaspersky Support outlining issues. Maybe some
enlightenment from there.

Paddy

 

[Chuck [MVP]]

Some progress. I perused your articles, and tried some suggestions.
Everything seemed to check out. You suggested my personal firewall. It
seems to be it (although I'm baffled as to how - see sequence)

I uninstalled Kaspersky Internet Security Suite on "Pats". (Left Kaspersky
fully enabled on "Tets", because there was no problem with "Pats" accessing
"Tets" shared folders - only vice versa). Enabled Windows firewall on
"Pats".

Re-ran XP Network Wizard on both PCs. Bingo! Both can now see and access
each others' shared folders. Thus network etc settings appear OK.

Re-installed Kaspersky on "Pats". Bugger. Straight away, "Tets" can see
but not access "Pats" shared folders, but "Pats" can access "Tets" OK.
Seems Kaspersky firewall is the issue.

Uninstalled Kaspersky and re-ran Network Wizard. Back to both can see and
access each others' shared folders. Hmmmm. Kaspersky firewall on "Pats"
the problem?? Reinstall Kaspersky WITHOUT firewall component. Nup.
"Tets" can see but not access "Pats" shared folders, but "Pats" can access
"Tets" OK.

Uninstalled Kaspersky and re-ran Network Wizard. Back to both can see and
access each others' shared folders. Reinstall Kaspersky Anti-Virus
component ONLY. Nup. "Tets" can see but not access "Pats" shared folders,
but "Pats" can access "Tets" OK. It seems ANY installed component of
Kaspersky - not just firewall - block access from "Tets" to "Pats".

I have contacted Kaspersky Support outlining issues. Maybe some
enlightenment from there.

Paddy

Paddy,

Look for anti-worm protection, that's a new application level security similar
to antivirus but it's network filtering. If you don't configure anti-worm
properly, it will block SMBs and cause your problem.

--
Cheers,
Chuck, MS-MVP 2005-2007 [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.

 

[Paddy]

Look for anti-worm protection, that's a new application level security
similar
to antivirus but it's network filtering. If you don't configure anti-worm
properly, it will block SMBs and cause your problem.

Thanks again, Chuck.

I'll see if I can find it in the Kaspersky settings. Not sure why Tets
would allow access, but Pats won't. Maybe because Pats is 192.168.0.1 with
the shared internet cable modem connected to it and seen as a "server"?

Networking Infant Paddy

 

[Paddy]

I'll see if I can find it in the Kaspersky settings. Not sure why Tets
would allow access, but Pats won't. Maybe because Pats is 192.168.0.1
with the shared internet cable modem connected to it and seen as a
"server"?

I was not clear above. What I meant is that BOTH are running Kaspersky
Internet Security Suite, and it appears Kaspersky is allowing Pats <-> Tets,
but blocking Tets -> Pats.

Further, Pats Network Places shows Tets shared folders in "Internet" and
accessible, but Tets Network Places shows Pats shared folders etc in "Local
Network" but NOT accessible. Is this difference between Pats and Tets
significant?

See screenshots http://paddymar.webng.com/Pats-Tets-Network-Places.jpg

(Repeating, Tets can access the shared cable modem on Pats)

Thanks again

Paddy

 

[Paddy]

Chuck - all fixed, thanks to you.

For the benefit of others with similar glitches:

It was not my Kaspersky Internet Security Suite after all - it was
IRPStackSize. I had previously set it to 15 to no avail.

The IRPStackSize registry key did not exist - I created it with a value of
15 dec (F hex) initially (as per your web-page suggestion), but to no avail,
a couple of days ago.

After checking Kaspersky worm protection (again to no avail), I revisited
IRPStackSize and modified it to 20 dec (14 Hex).

On rebooting Pats to effect registry change, curiously, Tets Local Area
Connection then showed "Limited Connectivity". Muttering and mumbling I
did a Status|Support | Repair, and voilà!

Pats and Tets can exchange everything up to but not including bodily
fluids ..... at least not thusly.

Thanks, Chuck

You and all other MVPs have blood that is worth bottling.

Paddy

 

[Chuck [MVP]]

Chuck - all fixed, thanks to you.

For the benefit of others with similar glitches:

It was not my Kaspersky Internet Security Suite after all - it was
IRPStackSize. I had previously set it to 15 to no avail.

The IRPStackSize registry key did not exist - I created it with a value of
15 dec (F hex) initially (as per your web-page suggestion), but to no avail,
a couple of days ago.

After checking Kaspersky worm protection (again to no avail), I revisited
IRPStackSize and modified it to 20 dec (14 Hex).

On rebooting Pats to effect registry change, curiously, Tets Local Area
Connection then showed "Limited Connectivity". Muttering and mumbling I
did a Status|Support | Repair, and voilà!

Pats and Tets can exchange everything up to but not including bodily
fluids ..... at least not thusly.

Thanks, Chuck

You and all other MVPs have blood that is worth bottling.

Paddy

And IRPStackSize comes up again. Good job being persistent, Paddy. Guess what,
you aren't a networking infant any more.

--
Cheers,
Chuck, MS-MVP 2005-2007 [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.

 

[Paddy]

And IRPStackSize comes up again. Good job being persistent, Paddy. Guess
what,
you aren't a networking infant any more.

Aw .... shucks ......

Paddy