<corporate network>-<my router>-<my switch>-<my hosts>
my desktop is also on the corporate network side of the router. I have static IP addresses for the hosts inside the router. Let me know if you need anything else.
rdp was working but now it seems it is not. I haven't changed anything on the router so I am not sure where to start. Here is debugging output showing me trying to RDP from my desktop to my server which has the external IP of 10.61.32.52 and the internal IP of 192.168.220.3. My desktop is...
Well, that didn't help. Basically, I have to point the vSphere Client to the ESX server and I can see the VMs console that way. I just can't see the consoles when I have logged into the vCenter Server via the vSphere Client and try to see the VM consoles via the Console tab. Works fine when...
Actually, I think I am the one that is drunk. I think I am still running the old 192.196.220.4 IP address on the ESX server. DOH! I'll check tomorrow and let you know my findings.
Well, now I get the dialog box asking me to verify the authenticity of the specified host when connecting from the cSphere Client to the ESX server via the ESX server's external IP of 10.61.32.55. It's trying to verify the SSL certificate. If I click yes, it just keeps coming up. If I click...
Here is the latest config:
Current configuration : 1653 bytes
!
version 12.3
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname hostdp01
!
boot-start-marker
boot-end-marker
!
enable secret 5 $1$I.4r$MG4o5inCNijBkCQ1VDl551
!
no aaa new-model...
Ok, I still am getting an error when trying to click on the console tab for the VMs within the vSphere client:
Unable to connect to the MKS: Failed to connect to server 192.168.220.4:902.
Well, I hit another speedbump. I can't bring up the consoles on the VMs when I am looking at the ESX server/VMs from the VSphere client. Any idea on what ports to forward for that? I can provide a 'deb ip nat' output if needed. Here is my latest config output:
Current configuration : 1616...
SUCCESS! I can now RDP and I can ping from the Windows box and ping from the router. Here is the final configuration less the NAT stuff for the Vcenter client and the ESX server stuff. Working on that now...
Current configuration : 1462 bytes
!
version 12.3
service timestamps debug uptime...
I figured it out:
ip route 0.0.0.0 0.0.0.0 10.61.32.1
hostxx01#ping google.com
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 72.14.204.103, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 36/36/36 ms
hostxx01#
I can't ping google.com from the router. It was working before I set the address on f0/0 from dhcp to 10.61.32.58. I am guessing there is a static route missing. Here is the latest configuration:
Current configuration : 1347 bytes
!
version 12.3
service timestamps debug uptime
service...
Should I upgrade the 2621's IOS? I had asked this before and didn't get an answer. I am still working on the configuration and will hopefully have that in the next couple of hours (gotta head home shortly and will log back in once there).
Please see my previous message on which versions are...
I mean, without all the mapping crap, I had everything working except for RDP and Vcenter Client. I really don't see why what I am trying to do is so difficult especially when I have static IP addresses for everything now. :shrug:
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.