Network Troubleshooting - Windows
Revision as of 11:43, 3 August 2008 by Christopher Hunt (talk | contribs)
midd_secure
If user can't connect to midd_secure:
- Does the connection repeatedly ask for the user's credentials? Check whether user can get onto webmail. If not, might be using wrong PW/UN or account could be locked out. Try logging on to Novell.
Common error messages
- "Trust relationship with server could not be established." The computer likely needs to be re-added to the domain or needs its name checked. Usually this message will only happen with lab computers, which are under DeepFreeze so we can't make any meaningful changes - Networks will have to deal with it. Get any information you can think of (Is it just one computer, or all in a specific area? MIDD numbers? Does it go away on restarting?) and assign to SR.
General network troubleshooting steps
- Run ipconfig then look for the message under “Media State” (if there is one) and check IP addresses[1].
- Message: “Media is disconnected” – NIC[2] thinks it’s unplugged. Possible solutions:
- Loose cable (“ensure that both ends of the cable are firmly connected”)
- Wrong jack (red jack or “Data” jack = GOOD; blue jack is turned OFF, usually)
- Bad cable (try a different cable), bad jack (try another jack or connect another computer to the original jack), bad network card (invite customer to LIB202)
- See Network Troubleshooting for what some IPs may indicate. In ANY case, here are some generic steps to try:
- [ ipconfig /release followed by ipconfig /flushdns and ipconfig /renew ] [3]
- Disable the connection in Control Panel, wait 5 seconds, re-enable it.
- Unplug jack, wait 5 seconds, plug back in. Doesn’t help? - Reboot.
- Try disabling 3rd party firewall software (e.g. Norton, McAfee, etc. may interfere with our network). Also, check to see if the browser has a proxy server configured.
If you still can't resolve the issue after these steps, get some information from the customer:
- Name and location (building, room #). Make sure we have their extension or cell #.
- Jack ID (it’s on a silver or white tag around or ON the jack, e.g. “A-0-12”).
- The customer then should run ipconfig /all and tell you the message under “Media State” (if there is one), the IP address, Physical (aka MAC) address and the DHCP server address.
- Customer should ping the DHCP server address, run arp -a and tell you the output of arp.
- Record all of the above and create a ticket for SR.