|
|
|
|||
|
Home | Troubleshooting | Quick Setup | Cisco How to | Data Recovery | Forums | Blog | IT Exam Practice | Services | About Us | Chicagotech MVP | Search | Contact Us | |
|
Troubleshooting Basic Connectivity
Access permission issue |
|
1. Ensure that all computers have the same protocol installed. This should be
TCP/IP normally. 2. The IP addresses on the same network adapter for each computer should be in the same range. 3. Verify that the ICF doesn't block the File and Printer Sharing. 4. Use the ping IP or computername to test connectivity between two computers on the network. If you can ping IP but not computername, this is name resolution issue. 5. if you can ping ip and computername, but you can't map any network drive, use net view \\remotecomputer to find out the problem. If you get error 5, this is permission issue. If you get error 51, make sure that you have enabled file and printer sharing and have some folders to be shared. If you get error 53, this is name resolution issue. 6. All network access to a W2K/XP computer in a workgroup can use the Guest account without creating a username for other computer logon. So, make sure that the Guest account is set up for network access. 7. Virus - No transportation error. |
Still need help, contact consultant Your feedback and contributions to this web site
Can't connect to shared resources on one of networking computers
Symptoms: you keep receiving the following message from My Network Places on one of three computers: "The list of servers for this workgroup is not currently available." when trying to access the shared folders. Also the shared drives shows red x. The internet access work fine.
Resolutions: 1) The Internet Connection Firewall (ICF) should not be enabled on the adapters that you use to connect the computers to the home network. If ICF is enabled on these adapters, you cannot connect to shared resources on other computers in the network.
When W2K/XP doesn't recognize the user who wants to access its shared disks or printers, you may see the below symptoms.
1. When win9x tries to access a w2k/xp computer shared folder, the IPC$
prompt. No password will be accepted. Resolution: you need to create the user
account on w2k/xp for win98 logon.
2. When W2K tries to access a w2k/xp computer shared folder, Enter Network
Password screen with Connect As and Password prompt. Resolution: type a username
and password were created on the w2k/xp, you should be able to access the shared
folders. Or create the user account on w2k/xp for remote computer logon.
3. When xp tries to access a w2k/xp computer shared folder, Connect to
computername screen with Username and Password prompt. Resolution: type a
username and password were created on the w2k/xp, you should be able to access
the shared folders. Or create the user account on w2k/xp for remote computer
logon.
Any users can access to my shared folders even they don't have user accounts on my computer
Symptom: If this is domain network and the shared folders are assigned permission to everyone, any one logon the domain can access to your computer, even you logon locally. However, if some one logon locally (no domain) on a remote computer, he/she should not be able to access to your shared folders.
Resolution: remove everyone from the security of the folders and add user accounts you want to access to your computer.
Sometimes, XP's built-in Firewall may enable after running network setup wizard on LAN connections. You can't ping or access the XP computer. To disable the XP firewall on the connection, go to the properties of the Connections, select Advanced, and deselect the firewall.
Disconnect from the network while process Access data
Symptoms: you are disabled from the network while process an Access data. Ipconfig shows you lost the ip is 169.254.x.x. Rebooting or disable/re-enable NIC may reconnect to the network.
Resolutions: 1. Modify hardware settings.
2. Check the hardware connection.
3. Upgrade the new drive if it is available.
|
Symptoms: When you attempt to connect to a Windows NT/W2K/XP Workstation system that already has ten connected to it, you may receive the following error message: No more connections can be made to this remote computer at this time because there are already as many connections as the computer can accept or Error 71. The network request was not accepted.
Causes: The maximum access sessions that are
permitted to simultaneously connect over the network to Windows NT/W2K/XP host
are ten (five for XP Home). This limit includes all transports and resource
sharing protocols combined. In other words, one machine may uses more than one
session. To find out how many sessions are using, use "net statistics server"
command on the host. That will show Sessions Accepted. To check the status of
the connection or which machine is connecting, use "nbtstat -s" command on the
host.
|
How to connect to a shared folder using different user accounts
As administrator, you may want to access to a administrative shared folder from a client computer. You can do this by using net use h: \\servername\c$ /user:domain/administrator.
How to enable and
disable the network connection
To enable/disable the network connection to local computer, go to administrative
tools>services, start/stop server service. To enable/disable the network
connection to remote computers, start/stop workstation service. You may want to
use task schedule to enable/disable it automatically.
How to enable/disable LAN from command line temporally
You can created a batch file that include ipconfig /release or ipconfig /renew, and use schedule to run it. If you use static IP, you may use netsh instead of ipconfig command. If you want to one way access, you may manage it by using server service and workstation service.
How to fix browsing problem in a mixed OS workgroup
|
SYMPTOMS: in a peer-to-peer network environment with mixed Windows OS such as win9x, NT, ME, W2K and XP, you may experience one or more of the following behaviors: 1) You cannot access shared folders or files. 2) You cannot browse other computers in the workgroup. 3) You receive the following error message when you double-click the workgroup in My Network Places/Network Neighborhood: Workgroup Name is not accessible. You may not have permission to use this network resource. Resolution: 1) make sure that NetBIOS over TCP/IP is turned on. 2) make sure the Computer Browser service is running on each computer in the workgroup. Note: the Computer Browser service maintains an updated list of computers on the workgroup, and it supplies this list to computers that are designated as browsers. If this service is stopped, the computers may not be seen from My Network Place/Network Neighborhood. |
For consultants, refer to browser issue page.
To access pre-2000/XP computers from w9x, NT and ME on a peer-to-peer network, you may need to enable NetBIOS over TCP/IP on the win2000/XP. To do that, go to the properties of My Network Places>network connection>Properties of TCP/IP>Advanced >WINS, select "Enable NetBIOS over TCP/IP".
Symptom: For some reasons (such as using domain profile when logon locally and accessing to different workgroup/domain or logon different workgroup/domain while trying to establish a remote access connection), you may logon a W2K/XP computer using cache credentials and the computer may be unable to access the network resources. You may receive this error message: System Error: (1311) There are currently no logon servers available to service the logon request when click the network resources.
Resolution: to fix the problem 1) use net use \\computername\sharedfolder /users:username command, When prompting for a passwordm, type the password. 2) If you use XP, elect Connect using a different user name when mapping a network drive. To do that, go to My Computer>Map Network Drive, click Connect using a different user name. and enter the credentials in the universal naming convention (UNC) "Domain\Username" format and password.
How to show or close all network connections
To close all network connections, use net session /delete. To show all network connections, use net session.
How to view a list of current active connections
Q: Is there a way with Win2000 Server that I can view a list of current active connections (i.e. which users are logging onto the network and using which files)?
A: 1. go to MMC>Shared Folders>Sessions. 2. Use cconnect.exe from resource Kits.
How to disable autodisconnection
Symptom: The mapped drive may be disconnected after inactivity for while.
Resolution: you may need to do these two to disable autodisconnection. 1) You may want to disable autodisconnection by using "net server /disconnect:-1" on the server hosting the mapped drives. 2) If you are running W2K/XP client, you may also want to use non-persistent mappings to connect the drives. For example, you use "net use h: \\shared /persistent:no" instead of "net use h: \\shared". Note: The persistent is default.
Still need help, contact consultant Your feedback and contributions to this web site
NIC speed can't go up to 100MB
Symptoms: All the same computers connecting to a 10/100 switch work fine except one. If you lower to the speed to 10MB, it works.
Cause: It may be caused by the bad cable.
NIC status displays send only but receive
Cause: Hardware issue such as NIC and switch.
One new computer doesn't talk to a good hub
Symptoms: Just bought a new XP replacing a win98 computer. The XP don't talk to this hub. Other computers use the same cable and hub without problem
Cause: It may be caused by hardware configuration.
1. Try to disable
autodisconnection feature first.
2. If disabling autoconnection doesn't fix the problem and other workstations
don't have the same issue, check the hardware settings, for example, configure
the computer' network cards for half duplex. Most Hubs don't support full
duplex.
For consultants, refer to XP disconnection issue page.
You cannot connect to shared resources on other computers in the network after enable ICF
A: The Internet Connection Firewall (ICF) should not be enabled on the adapters that you use to connect the computers to the home network. If ICF is enabled on these adapters, you cannot connect to shared resources on other computers in the network.
|
This web is provided "AS IS" with no warranties.
Copyright © 2002-2018
ChicagoTech.net,
All rights reserved. Unauthorized reproduction forbidden.