"access is denied" error when networking lap top to cpu

[kim]

we're trying to get a lap top to communicate with a home
cpu. cable internet is being shared with each computer
via dlink di-604. each computer can access the internet.
the computers list each other in their respective network
places. the computers can ping each other by IP address
and compute name. the cpu can read the laptops shared
files. the lap top cannot access the cpu. the error
message is, "\\dillon (the name of the cpu) 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 permission. access
is denied." we've spent hours and hours on this one.
Help! Please and Thanks. Kim

 

[Lanwench [MVP - Exchange]]

Are both computers in the same workgroup, and have you created each user
account/password identically on each?

 

[Robert L [MS-MVP]]

quoted from http://www.ChicagoTech.net
.... is not accessible

Message: "....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. Network path was not found."

Resolutions:
1) make sure no any firewall running.
2) make sure you have created the same workgroup, and the same username on
w2k/xp for logging on a remote computer.
3) check user's rights.
4) you may want to enable guest account on w2k/xp.
5) if you are using simple file sharing, you may try to disable it and
re-share the drive manually.
6) if it is mixed OS (win98, NT, ME and W2K/XP) network, enable NetBIOS over
TCP/IP.
7) make sure the Computer Browser service is started if all computers are
w2k/xp.
8) stop Computer Browser service on win9x, ME and NT if this is a mixed OS
network.
9) cache credential by using net use \\computername\share /user:username
command (it is better to have the username logon shared computer).
10) if you have tried enabling netbios over tcp/ip but doesn't work, you may
try to load netbeui (loading netbeui may slow your network).
11) Make sure the server service is running.
12) If you can see the share in Network Neighborhood but not access it, this
issue may be resolved by verifying that both the share permissions and the
NTFS partition permissions are correctly configured for individual user or
group access.



--
For more and other information, go to http://www.ChicagoTech.net

Don't send e-mail or reply to me except you need consulting services.
Posting on MS newsgroup will benefit all readers and you may get more help.

Robert Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN, Anti-Virus, Tips & Troubleshooting on
http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.

 

[Chuck]

we're trying to get a lap top to communicate with a home
cpu. cable internet is being shared with each computer
via dlink di-604. each computer can access the internet.
the computers list each other in their respective network
places. the computers can ping each other by IP address
and compute name. the cpu can read the laptops shared
files. the lap top cannot access the cpu. the error
message is, "\\dillon (the name of the cpu) 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 permission. access
is denied." we've spent hours and hours on this one.
Help! Please and Thanks. Kim

Kim,

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 the SFS settings the same on each computer.

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".

If you set the Local Security Policy to "Guest only", make sure that the Guest
account is enabled, and has an identical, non-blank, password on all computers.
If "Classic", setup and use a common account with identical, non-blank, password
on all computers.

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

 

[Kim]

Whoops! both computers are running window XP home
edition.

 

[kim]

whoops! both computers are running windows xp home edition

 

[kim]

The error message was not that the network path was not
found. It was "access is denied" The operating systems on
both computers is xp home edition. Do your suggestions
still apply? Kim

-----Original Message-----
quoted from http://www.ChicagoTech.net
.... is not accessible

Message: "....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. Network path was not found."

Resolutions:
1) make sure no any firewall running.
2) make sure you have created the same workgroup, and the same username on
w2k/xp for logging on a remote computer.
3) check user's rights.
4) you may want to enable guest account on w2k/xp.
5) if you are using simple file sharing, you may try to disable it and
re-share the drive manually.
6) if it is mixed OS (win98, NT, ME and W2K/XP) network, enable NetBIOS over
TCP/IP.
7) make sure the Computer Browser service is started if all computers are
w2k/xp.
8) stop Computer Browser service on win9x, ME and NT if this is a mixed OS
network.
9) cache credential by using net use

\\computername\share /user:username

 

[Lanwench [MVP - Exchange]]

That shouldn't make any difference here....see the other posts for more info
that may help, although my advice still applies.

 

[Guest]

Are both computers (laptop and cpu) in the same domain or workgroup? and are you using DHCP with this.. and do both computers have the same DNS and WINS?

 

[Chuck]

Whoops! both computers are running window XP home
edition.

Please provide ipconfig information for each computer.
Start - Run - "ipconfig /all >c:\ipconfig.txt" - Open c:\ipconfig.txt in
Notepad, copy and paste into your next post.

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