If you are working on proctorlabs gear is sounds like you have run into the same problem as I had plenty of times the last week. In that case you are experiencing problem with vmware where acs runs. Verify this in a top-down order:
1) Make sure that your routes are properly configured (route print, route add...). Still doesnt work? 2) Reboot the ACS-machine. Still doesn´t work? 3) Start wireshark and capture traffic on student nic. That has made magic for me a couple of times. STILL doesn´t work (been there!)? 4) Page Proctor labs after hours support and ask them to reboot the ESX host. Refer to Tyson. If they cant because of that would interfere with other studens/pods you are scr*w*d for that session. I think that Vol1 Lab 2 uses original ip-settings on ACS (10.1.1.100) and this problem only shows upp when re-addressing the student nic of ACS, but it might be that ACS hasnt been reverted correctly or something.. /Jimmy 2010/7/11 Johan Bornman <[email protected]> > Hi, > > > > I cannot ping the ACS server from R2. The ACS and R2 are directly > connected. A sh arp on R2 shows the ACS server, there is no arp entry for R2 > on the ACS. The routes are good on the ACS. The switch configurations are > fine, although none is required in the lab. > > > > I also removed the configs on all the devices but I am having the same > problem. > > > > Am I missing anything or is it possible that there is a problem on the > rack? > > > > Thanks > > > > Johan > > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com > > -- ------- Jimmy Larsson Ryavagen 173 s-26030 Vallakra Sweden http://blogg.kvistofta.nu -------
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
