I experienced a couple of gotchas when I tried to use the Netlab remote
lab for the first time. Fairly obvious in hindsight, but I thought if I
posted the resolution here it might save some of you some pain…
Once you have started your remote lab session, open up a couple of the
Clients. The virtual images are scrubbed each time you begin a new
session. In other words, their config is reset to Cisco defaults. This
is great because you have a consistent starting point, but it also means
you have a bit of housekeeping to do before you can start work.
Firstly check that you NIC is configured for DHCP like this:
Now open a Command Prompty (Start/Run/cmd) and type ipconfig /release (enter). Now type ipconfig /renew (enter). This makes the network configuration take effect and makes a fresh request to the DHCP server for an IP address.
Check your network configuration by typing ipconfig /all (enter). Your local IP address should be something like 172.16.0.1. (Or .2 as it is here, because I’d already configured another Client.) Prove that you can see network stuff by typing ping eagle-server.example.com (enter).
For most exercises you’ll need to download and install Wireshark. Remember that these computers don’t have any public internet access, so you’ll have to download Wireshark from the lab server itself. This is called eagle-server.example.com (192.168.254.254). You could use the old DOS-style FTP package, but it’s easier to use use Internet Explorer to browse the Eagle server’s FTP server and install directly from there.
You will need to perform similar steps on all Clients. You need to do this for most lab exercises.
Hope this helps!