need help with XP SP2 network problem

  • Thread starter Thread starter Jonesgold
  • Start date Start date
J

Jonesgold

I have a home network running on WIN XP PRO PCs
One PC can't ping or connect to the other. When I go to my network places
and select View workgroup computers, it shows AMD2400ATI but if I click on
it I get the following error.

How can I fix it so this computer has permission to use this network
resource. It worked fine before installing XP SP2.

AMD2400ATI 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.
The network path was not found.

I am administrator on both PCs and have shares on both PCs. I disabled the
firewall and it did not help.

IPs are
196.168.249.1
196.168.249.2


--
Thanks
Jonesgold

Remove the NOSPAM
(e-mail address removed)
 
I have a home network running on WIN XP PRO PCs
One PC can't ping or connect to the other. When I go to my network places
and select View workgroup computers, it shows AMD2400ATI but if I click on
it I get the following error.

How can I fix it so this computer has permission to use this network
resource. It worked fine before installing XP SP2.

AMD2400ATI 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.
The network path was not found.

I am administrator on both PCs and have shares on both PCs. I disabled the
firewall and it did not help.

IPs are
196.168.249.1
196.168.249.2

Jones,

What firewall did you disable? ICF or a third party product?

On any XP Pro computer, check to see if Simple File Sharing (Control Panel -
Folder Options - View - Advanced settings) is enabled or disabled. With XP Pro,
you need to have SFS properly set on each computer.

With XP Pro, if SFS is disabled, check the Local Security Policy (Control Panel
- Administrative Tools). Under Local Policies - Security Options, look at
"Network access: Sharing and security model", and ensure it's set to "Classic -
local users authenticate as themselves".

With XP Pro, if you set the Local Security Policy to "Guest only", make sure
that the Guest account is enabled, thru Local User Manager (Start - Run -
"lusrmgr.msc"), and has an identical, non-blank, password on all computers. If
"Classic", setup and use a common non-Guest account, with identical, non-blank,
password on all computers.

For XP Pro with Simple File Sharing enabled, make sure that the Guest account is
enabled (thru Local User Manager (Start - Run - "lusrmgr.msc")), on each
computer, with identical, non-blank passwords.

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
 
I disabled ICF and Zonealarm. Did not help.
Tried all you said none worked.

Network is only working one-way

--
Thanks
Jonesgold

Remove the NOSPAM
(e-mail address removed)
 
I disabled ICF and Zonealarm. Did not help.
Tried all you said none worked.

Network is only working one-way

If ZoneAlarm (Free? Pro?) is involved, it is very possibly at least part of the
problem. Disabling ZA is known, in multiple cases, to NOT be an effective
procedure. Please re enable ZA, then either 1) Delete it, totally, using all
procedures provided by ZoneLabs, or 2) RTFM and configure it properly for file
sharing.

Please provide ipconfig information for each computer.
Start - Run - "cmd". Type "ipconfig /all >c:\ipconfig.txt" into the command
window - Open c:\ipconfig.txt in Notepad, copy and paste into your next post.
Identify operating system (by name and version) with each ipconfig listing.

Please provide diagnostics. From each computer, test shares visibility (use
actual name / address of each computer as appropriate):
Start - Run then:
1) \\ThisComputerByName
2) \\ThisComputerByIPAddress
3) \\OtherComputerByName
4) \\OtherComputerByIPAddress
Report visibility of shares / exact error displayed in each test (8 tests
total).

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
 
Chuck thought carefully and wrote on 8/19/2004 9:41 PM:
If ZoneAlarm (Free? Pro?) is involved, it is very possibly at least part of the
problem. Disabling ZA is known, in multiple cases, to NOT be an effective
procedure. Please re enable ZA, then either 1) Delete it, totally, using all
procedures provided by ZoneLabs, or 2) RTFM and configure it properly for file
sharing.

Instructions for complete ZoneAlarm removal here:
<http://nh2.nohold.net/noHoldCust25/Prod_1/Articles55646/CompleteUninstallNonNT.html>

I've had to use this a couple times to completely remove my Cisco VPN
Client (who woulda thunk that?).

Lance
*****
 
Back
Top