XP Home & XP Pro - peer to peer

[Guest]

Hi,

I'm having problems trying to get my existing XP Home (SP1) machine to
access shared resources (ie hard drive) on a new XP Pro (SP1) machine and
vice versa. The two are connected via a simple hub. (I've previously had a
peer to peer network setup between the XP Home PC and an older Win98 machine
which has subsequently been de-commissioned.)

Each can see the other machine but when I try to access the otherI get an
error "\\host is not accessible. You may not have permission to use this
network resource. Contact the administrator of this server to find out if
you have access permissions. The network path was not found".

I've looked around this discussion group and checked a number of things
including -
..shares are established because I can see them from their own machine
..firewall & virus software is currently disabled.
..both are running NetBIOS over TCP/IP
..the browser service is running on both machines
..each have an identical userid account/password established
..each can ping each other no problems (IP addresses and masks are correct)
..have replaced the hub with a switch - no change

What else can I check?
What am I missing here?

Any advice would be appreciated. Thanx.

 

[Guest]

I am having a similar problem. I am going out to the client site right now.
I'll let you know how I did.

 

[Guest]

I have similar problems. Trying to set up a peer group inside my
firewall/router with NAT so I have private IP address range. Netbios did not
help. All worked fine with 2000 and with one computer running 2000 and the
other running XP SP1, Now that both are XP SP2 nothing works.

I suspect that it has something to the way Microsoft sets up the group
policies with SP2 but not sure just what to do about it.

I use two laptops and either or both can be connected to the router either
wired or wireless. My wireless runs WPA with AES encryption which MS does
not support so I must use 3rd party stuff.

I have Norton Internet Security on both machines set up with personal
networking enabled on the IP range I use.

Any help is appreciated.

 

[Doug Sherman [MVP]]

Make sure Simple File Sharing, Guest account, and local users authenticate
as Guest are enabled. See:

http://support.microsoft.com/default.aspx?scid=kb;en-us;304040

Doug sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP

 

[Guest]

Thanks Doug, but...
Checked everything in the KB article - all settings were correct.
Still no change.
Any other ideas?

Tim

 

[Chuck]

Thanks Doug, but...
Checked everything in the KB article - all settings were correct.
Still no change.
Any other ideas?

Tim

Tim,

Are you then using Guest only authentication on the XP Pro computer (either SFS
enabled, or SFS disabled, and Guest only authentication)?

If so, check Local Security Policy "User Rights Assignment: Deny access to this
computer from the network" and make sure that Guest is not in the list.

Next, look on both computers, at registry key
[HKLM\System\CurrentControlSet\Control\Lsa], value restrictanonymous.
<http://www.microsoft.com/windows200...2000/techinfo/reskit/en-us/regentry/46688.asp>
<http://www.jsifaq.com/subf/tip2600/rh2625.htm>

The above articles refer to Windows 2000. Remember WinXP is NT V5.1, and Win2K
is NT V5.0.

Have you used the Registry Editor before? If not, it's a scary tool, but it's
pretty simple once you get used to it. Here are a couple articles that might
help:
<http://www.microsoft.com/windowsxp/...home/using/productdoc/en/tools_regeditors.asp>
<http://www.annoyances.org/exec/show/registry>

Just remember to backup the key (create a registry patch) for
[HKLM\System\CurrentControlSet\Control\Lsa] before making any changes, if
appropriate.

From the Annoyances article:
You can create a Registry patch by opening the Registry Editor, selecting a
branch, and choosing Export from the File menu. Then, specify a filename, and
press OK. You can then view the Registry patch file by opening it in Notepad
(right-click on it and select Edit). Again, just double-click on a Registry
patch file (or use Import in the Registry Editor's File menu) to apply it to the
registry.

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.