Network Errors     Main Menu

"... is not accessible"
"...not available. The server is not configured for transactions"
"An extended error has occurred" or "Access Denied"
" computername is not accessible. No permission to access the resources"
"M Multiple connections to the server or shared resource are  not allowed"
"Network path not found" in a domain network 1
"Network path not found" in a domain network 2
"Network path not found" in a workgroup network - error 53
"Not accessible. You may not have permission to use this network resource"
"Not enough server storage is available to process this command."
"Not enough storage to Complete Operation"

"No logon server available"
"Resources: \\computername\IPC$"
"System error 6118 has occurred. The list of servers for this workgroup is not currently available."
"The password is incorrect. Try again"

"The network location cannot be reached"
"There are no entries on the list"
"Unable to access Computers Near Me" or "Workgroup is not accessible" errors
"Unable to Browse Network"
"You may not have permission to use this network resource"
"You must provide a password to make this connection."

... 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. The semaphore timeout period has expired."

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 wwin9x, 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) Still need help, contact consultant at http://hidev.com/contactus.asp for the tech support.

"...not available. The server is not configured for transactions"

Type command "net share" on the shared computer. If there is not a share named "IPC$" in the share list, use the command "net share ipc$" to create it.

"An extended error has occurred" or "Access Denied" Symptoms: When mapping a network drive using net use or using the net view command to view a different computer in the domain, you may receive: "An extended error has occurred" or "Access Denied" error messages.
Resolutions: 1) This issue may occur if the workstation doesn't synchronize the time with the server. After verifying that basic network connectivity exists, you can force time synchronization on the client computer manually. To do this, run net time /domain /set command.
2)
Make sure you have granted enough licenses for clients accessing.

" computername is not accessible. No permission to access the resources"

If  both win2000/XP and win9x can see the workgroup but only win2000/XP can access a win 2000/XP computer, and win9x gets the above error, check the group name. If they are the same name,

Check these: 
1) are you sure the logon user has permission to the shared folder?
2) have you tried to logon using the same user name and password of the accessed win2k/XP computer?
3)  the last and risky one, if you enable guest account in the accessed win2000/XP computer, can you access now?

"Multiple connections to the server or shared resource are  not allowed"

Symptom:  when attempting to join a domain, you may receive "Multiple connections to the server or shared resource are  not allowed. Please disconnect all previous connections to the server or shared resource and try again."

Resolution: try using net use /d from a command to clear all your mapped connections before joining the domain. You can also disconnect the mapped drive in Windows Explorer by right-click the mapped drive and select disconnection.

"Network path not found" in a domain network 1

SYMPTOMS: When trying to join a W2K/XP to a Windows 2000 domain by using he NetBIOS domain name, you are successful but not the FQDN and you may receive one of the following error messages:1) The following error occurred attempting to join domain "example.com": The network location cannot be reached. For information about network troubleshooting, see Windows Help.  2) Network path not found.
RESOLUTION: This issue may occur if the TCP/IP NetBIOS Helper Service is not running on the client computer. To start  the TCP/IP NetBIOS Helper Service, go to MMS>Services, double-click TCP/IP NetBIOS Helper Service.

"Network path not found" in a domain network 2

Symptom: some w2k/xp can't join the domain randomly. The DNS server is multihomed server..

Resolution: You can find some computer browser errors on the DNS server. Disable one of two NICs will work. More resolutions can be found in browser Issue page.

Still need help, contact consultant at http://hidev.com/contactus.asp for the tech support.

"Network path not found" in a workgroup network - error 53

RESOLUTIONS:
1) Make sure that File and Printer Sharing is enabled on on the shared computer.
2) Make sure that shared machine has something shared.
3) Make sure that you have created the same workgroup and logon the same username if you try to access w2k/xp network.
4) Make sure that you have enabled NetBIOS over TCP/IP if this is a mixed OS network.

"Not accessible. You may not have permission to use this network resource"

Symptom: Your WinXP,  in a peer-to-peer network,  may receive the following error when you double-click My Network Places/Computers Near Me: <Workgroup Name> is not accessible. You may not have permission to use this network resource. Resolution: 1) Enable NetBIOS over TCP/IP on one or more computers in the workgroup. To do that, go to properties of Local Area Connection>properties of Internet Protocol (TCP/IP)>General> Advanced>WINS, check Enable NetBIOS over TCP/IP (If you have a DHCP-assigned IP address, select Use NetBIOS setting from the DHCP server ). 2) Make sure the Computer Browser service is started.

"Not enough server storage is available to process this command." error.

SYMPTOMS: When accessing shares on a server from a client, you may receive "Not enough server storage is available to process this command." error. You may receive this message and Event ID: 2011 after you install Norton Antivirus for Windows.

Resolution:
1) The registry value IRPstackSize may be not explicitly present. To increase the value of the parameter, go to the key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ LanmanServer\Parameters. If the key is not present, choose Add Value in the Registry Editor. The Value Name should be IRPStackSize and the Data Type is REG_DWORD.
2) Remove any unnecessary entries from this value in the registry, HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters\NullSessionPipes.
3) Disable Norton antivirus to see if that will fix the problem.

Refer to MS Q106167 and Q177078 for more details.

 "Not Enough Storage to Complete Operation"
SYMPTOMS: When you try to open the Printers folder, you may receive the following error message "There is not enough storage to complete this operation". This is because the size of the registry has exceeded the maximum size set in the virtual memory settings. RESOLUTION: Increase the maximum registry size. To do that, go to Start>Control Panel>System>Performance> Change (In Windows 2000, click the Advanced tab, click Performance Options, and then Change). Type a larger value in the Maximum Registry Size box.

"No logon server available"

Symptoms: you can ping the server by ip and name but can't map the shared drive by using net use \\ip or \\servername.  If you try, you may receive the "No logon server available".

Resolutions: This sounds like cache credential issue. 1) make sure the computers in the same network, the same workgroup/domain and have created the same username. 2) use net use \\servername\sharename password /user:username to cache the credential.

Still need help, contact consultant at http://hidev.com/contactus.asp for the tech support.

"System error 6118 has occurred. The list of servers for this workgroup is not currently available." Symptoms: When using the net view \\computername command, you receive the following error message: System error 6118 has occurred. The list of servers for this workgroup is not currently available.
Resolutions: 1) disable ICF if you don't need it.
2) Open port # (UDP and TCP) from 135 through 139 and/or 445. To do this, go to the properties of the connection>Advanced>ICF>Settings>Services. For Microsoft file sharing SMB: add  (UDP and TCP) ports from 135 through 139. For direct-hosted SMB traffic without network basic input/output system (NetBIOS) uses port (TCP and UDP) 445. Note: the external and internal port numbers should be identical.

"The password is incorrect. Try again"

Symptom: While trying to access a win2000/XP computer and type administrator password on Enter Network Password screen in the same peer-to-peer workgroup, you may get Error: The password is incorrect. Try again.

Resolution:
1) You need to setup every user that needs access to the shared folder on every computer they have to connect to. Then give the proper user proper permission to the shared folder.
2) logon the same user and password.
3) as always,  you can try to enable a guest account on the accessed machine.

"There are no entries on the list"

Symptom: when using net view \\remotecomputer command, you may receive "There are no entries on the list". And you may have a problem to access the remote computer.

Resolution: 1) If there are no file or print shares on the computer, the net view command displays a "There are no entries in the list" message. So, make sure there are file or print shares on the computer. Or to use net share command to check sharing status.
2) Make sure no firewall running because the firewall may block sharing.

"Unable to access Computers Near Me" or "Workgroup is not accessible" errors

Symptom: When several Win2000/XP computers are configured as members of a workgroup in a peer-to-peer network environment and you click on Computers Near Me in My Network Places or workgroup name Entire Network, the following error message may appear: "Cannot Access 'Computers Near Me' " or "Workgroup is not accessible" errors.

Resolution: 1) NetBIOS over TCP/IP. To do that, go to the properties of TCP/IP>Advanced>WINS. If you are using a static Internet Protocol (IP) address, click Enable NetBIOS over TCP/IP. If you have a DHCP-assigned IP address, click Use NetBIOS setting from the DHCP server.
2) No Master Browser or too many browsers may cause this issue. Check Browser issue.

"Unable to Browse Network"

Symptom: When you attempt to browse your network by opening Entire Network in My Network Places/Network Neighborhood, you may receive the following error message: Unable to Browse Network.

Check Lists: 1) have you loaded the NIC or is it working?
2) have you loaded common protocol, TCP/IP?
3) does the Computer browser work?
4) have you enable file and printer sharing in the accessed computer?
5) is the workstation service running?

"You may not have permission to use this network resource"

Refer to ... is not accessible

 and "Resource: \\<computername>\ipc$"

"You must provide a password to make this connection." and "Resource: \\<computername>\ipc$"

Whenever you  receive "Enter network password. You must provide a password to make this connection." and "Resource: \\<computername>\ipc$", it is permission and workgroup issues. This behavior can occur for any of the following reasons: 1) The Windows 9x computer is not a client of a domain environment but the Log On To Windows Domain option is enabled. 2) The user name and password you are using to log in to the Windows 9x are not contained in the local user accounts database of the Windows NT/2000/XP computer you are attempting to browse. 3) The Windows 9x host is configured with user-level authentication to a domain.
Resolutions: To resolve this issue, use the appropriate method:
1) Disable the Log On To Windows Domain Option.
2) Log on to the Windows 9x with the local user accounts database of the Windows NT/2000/XP computer you are attempting to browse.
3) Disable User-level Authentication on the Windows 9x.

  Main Menu