Support
| DS Clinic: Frequently Asked Questions Why can’t I login to a server? What if none of the virtual machines are responding? Why do my Virtual machines hang on bootup (usually when the NIC card is loading)? |
| Why can’t I login to
a server? 1) Check to ensure that the Microsoft Loopback Adapter is the network adapter for the Virtual Switch. Do this by clicking on the File menu/Preferences/Virtual Switch. If the Microsoft Loopback adapter is not one of the adapters displayed, check to ensure that this driver is installed, working properly and is enabled. |
| 2) Sometimes while unloading and reloading DS, your connection information gets jumbled. It may require that you login again but sometimes even that is not possible. The signature of this problem is when one server will not map properly during login. To solve this problem, go to the N in the systray, right mouse click and display NetWare Connections. |
| Detach from the server that won’t map properly and re-login using the IP number for the server in the Server: field of the Advanced Login page. You may want the Clear Current Connections selection box, unselected. If this box is not on your Advanced Options page, right mouse click on the N in the systray and select Novell Client Properties. Next select the Advanced Login tab and ensure Clear Connections tab is selected. The IP numbers of each server are easy to remember: NDS1 – 10.0.0.1 NDS2 – 10.0.0.2 NDS3 – 10.0.0.3 |
| 3) Make sure your Microsoft Loopback Adapter is configured properly; see the installation manual for configuration parameters. 4) Disable any firewall. A personal Firewall on the machine running DS Clinic may hinder ICMP traffic from the virtual environment to the local workstation and should be disabled while using DS Clinic. (A personal Firewall on two development machines during the initial programming phase of DS Clinic cost several hours of development time—we got our troubleshooting practice in as well.) 5) If you receive the message: |
| This condition can be caused when DS.NLM isn’t loaded on NDS2 and NDS3—the servers that hold the Admin object. If that doesn’t solve the problem, you may have to restart each server and possibly reset the Microsoft Loopback Adapter. 6) If you receive the following message from the DSCLINIC.EXE application: |
| It may be possible that your machine has “snagged” an IPX attachment. Click on the N in the systray and select NetWare Connections. If one of the servers is communicating via IPX, then this may be the problem. |
| Disconnect the server by highlighting the server and select “Detach”. Try logging in again. If this is unsuccessful, ping the server from the workstation –and- from the server to the workstation to ensure IP communications are possible. |
| What if none of the virtual machines are responding? It has been found that in some isolated incidents, all three virtual machines will stop responding. Sometimes, this is temporary due to other background processes, however, sometimes the machines stop responding completely. To resolve this, you will need to stop Virtual PC without saving the session and restart. However, due to timing issues within Connectix still under investigation, the machines will hang but can be released if one of the NDS servers is paused. See “Why do my Virtual machines hang on bootup (usually when the NIC card is loading)?” Why do my Virtual machines hang on bootup (usually when the NIC card is loading)? Due to some issues in timing, you may have to pause one of the virtual machines during the loading process which will allow the other machines to load. This may have to be done on each of the virtual machine in sequence. The cause of this problem is currently unknown but we are investigating. |
