foxyloxley: Thats not what i meant, i didnt understand what this would help.
I do know how to access a share.
Relyt: Firewalls are turned off.
Printable View
foxyloxley: Thats not what i meant, i didnt understand what this would help.
I do know how to access a share.
Relyt: Firewalls are turned off.
Maybe i should add what error message shows up:
Something like that.Code:\\"computername" is not accessable. You may not have access to use this network resource. Contact the administrator of this server to find out if you have accesspermissions.
Source:Quote:
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 blocks the LAN traffic.
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.
The above steps shuld get you into the right direction.
I have had this happen to me a few times, each time I have to reset the master browser.
Be warned sometimes it was software I think the only one I remember is MS Money 2004/5 which broke my internal workgroup.
Here is some info on the error from MS:
http://support.microsoft.com/default...b;en-us;318030
What I had to do was stop the browser service on all the machines and then reboot them all one by one, I took my main desktop up first and then all the others one at a time.
HTH
Are you using any Norton products? Ie: internet security. They are notorious for causing problems with lans such as you're talking about. I've had the same issue, but from my computer I wasn't able to view any of the network. I was allowed internet access through it, but not able to browse the other computers. Ensure that not only is your Windows Firewall off, but run through the exceptions and make sure that File and Printer Sharing is checked as an exception. Ensure that your Norton or or other firewall products are not limiting your File Sharing capabilities.
Again, i have disabled all firewalls, security products etc.
I therefore cant imagine how this would be a problem.
Does this error message show up on your computer or theirs? For only a sharing issue, it's surprising that it isn't resolved with the information provided.Quote:
Maybe i should add what error message shows up:
code:\\"computername" is not accessable. You may not have access to use this network resource. Contact the administrator of this server to find out if you have accesspermissions.
Something like that.
~cheers~
I had the exact same problem about a week ago - tried permissions and everything. This website helped me out:
Quote:
This is in some cases caused by a registry setting named RestrictAnonymous. Go to the computer which you cannot access, start a registry editor and change the following registry value.
HKEY_LOCAL_MACHINE
\SYSTEM
\CurrentControlSet
\Control
\Lsa
Value name: RestrictAnonymous
Value type: DWORD
If the value is 1 or even 2, change it to 0, reboot and retest. If the problem is solved, leave the value at zero. If not, you can change it back if you like.
the "server"service must run