Navigation

Document
Introduction
Install
Configuration
Installing SME
Testing Connectivity
Testing Updates
Links
Tips & Tricks		 Why Qemu?
Install Qemu and associated software on WinXP
Configure your system to use Qemu
Install SME Server on your virtual host
Test your connectivity to make sure you can work with SME Server
How to use Qemu to test SME updates
More information about Qemu


Testing Connectivity

Updated 05Sep2005 - RonM

ipconfig/ifconfig
1. On the host machine (Windows XP) open a command prompt (Start >> Run >> Type in "cmd" >> click "OK"). Type in "ipconfig /all". Make a note of the results. The "Bridge" network adapter should have full information.

2. On the guest machine (SME Server in Qemu), logged on as root, type "ifconfig". The adapter "eth0" should have the IP address you gave during the SME install.

ping
3. On the host machine, ping (ping -a -n 1 192.168.0.70 for me) the IP address of the bridge. Ping the actual SME Server or default gateway (ping -a -n 1 192.168.0.10 for me). Ping the IP address that you gave the guest SME (ping -a -n 1 192.168.0.175 for me). All pings should get responses.

4. In the guest SME server, ping (ping -c 1 192.168.0.175 for me) the server IP address, the bridge (ping -c 1 192.168.0.70 for me) IP, and the default gateway IP (ping -c 1 192.168.0.10 for me). All pings should get responses. Note: Qemu will hang if any pings fail to resolve.

Server Manager
5. Open a web browser on the host and go to server-manager for the guest SME Server (http://192.168.0.175/server-manager for me). Log on with admin account and password. Make sure that the account password for your user account has been reset. Note: the SME Server name should resolve here; I'm just using IP addresses to reduce complexity: from other hosts sometimes the server name is PC00065.erectech.local, etc. IP addresses will work (if there's connectivity) from anywhere on the local network.

smb - samba
6. On the host machine, in Explorer, map a drive or enter a UNC, to "\\192.168.0.175\updates". You will see a login prompt, unless you logged on to the XP system with the same user account you created in the guest SME Server. You should see the cgi-bin, files, and html folders.

7. Try the same thing (step 6) from another system on the network. You should get the same result.

SSH
8. Make an SSH connection to the guest SME server (192.168.0.175 on port 22 for me). You should be able to log on as root. Try the same thing (step 8) from another system on the network. You should get the same result.

9. Open a connection to the guest SME Server with WinSCP (192.168.0.175 on port 22 for me). You should be able to connect as root and see the file structure of the guest SME Server. Try the same thing (step 9) from another system on the network. You should get the same result.

ftp
10. Finally, you should be able to open your favorite FTP client and connect to the guest SME Server\users/username/home directory (192.168.0.175 /users/ronm/home - using user account and password) from both machines (assuming you've turned FTP on in server-manager). You get the idea, your guest SME Server has full network connectivity when using an IP address or a name that will resolve to one.