Hello,
I am extremely green to virtualization. I understand I need an ip address to be able to use trac, only when I try to connect, the ip address that is given to me doesn't open a page or connect in any way. It gives me the "Action Cancelled" error page. Has anyone run into this problem? and if so how did you get a working IP address?
Thank You
IP address doesn't work.Submitted by choicesplacemen... on Fri, 11/02/2007 - 1:05pm |
JumpBox Collections
|
IP address doesn't work
A small trick is that virtualistion software may need a network cable plugged into the port on the computer, and also terminated onto an active connection such as a switch. Otherwise the NIC will not enable, and the virtualistion software will not be able to use the NIC for the virtual networking.
have similar problem -- also a newbie
I'm on a network and the Jumpbox virtual cosole gives me a real address in a 10.x.x.x range (so not a default ip), but I still can't access the jumpbox with my browser. I have tried multiple browers and pinging the ip also but no luck. I tried setting the virtual machine to host only and that didn't seem to make a difference. Ultimately I'd like to access it over the network, but for now I'd settle for local machine access.
Any help would be appreciated.
Thanks!
april
have similar problem -- also a newbie
Is the JumpBox accessible from a different computer on the same network? What is the host OS and virtualization software you are using? Many times, problems like these are strange and intermittent, and the person who reports it comes back saying that it worked after a reboot or unzipping a new JumpBox.
Also, check if you have some sort of firewall running and temporarily disable it and see if that helps.
Austin
IP address doesn't work.
Hi,
I bet your IP address begins with something like 169....? Is that correct? The JumpBox by default is set to get its IP address from the local network your host computer is attached to (this is known as bridged mode). If you aren't on a network and just want to access the JumpBox from your local computer, you can switch the network to "Host Only" or "NAT" mode, then the JumpBox will only be available to that computer.
If you are on a network and want to manually set an IP address (since you perhaps don't have a DHCP server), you can do so on the console of the virtual machine. There is a text based interface that makes this possible.
Good luck, let me know if you need any additional clarification.
Austin
IP, network outbound BUT NOT INBOUND!!!
I'm having a similar issue. We've got a GLPI jump box setup that I just inherited. It was working fine the other day, yesterday it was a bit spotty and today it's gone off the deep end. It has a real IP address (yes Austin, just like the other cat it has a real IP 10.x.x.x not 169, JUST LIKE HE SAID!) and from the jump box console I can ping yahoo.com, I can ping an external IP for Yahoo and I can even ping internal hosts but I can't ping or access the jump box from our LAN. It's almost as if there is a firewall blocking all inbound traffic...but I know there isn't!
It just makes no sense.
If I reboot the machine it pings for 8 or 9 replies then the console fully comes up and it stops all ping replies right when I see the grey jump box console. I can do a: "/etc/init.d/networking restart" and the same thing happens, maybe 3 ping replies and it dies again.
What's going on? It's a virtual machine, I can't physically touch the dang thing and there is no backup. I have thought about mapping a drive and placing the backup there then redoing it old school without the JB interface BUT I'm going to have to figure that out because of some fstab problems and it not allowing me to mount a network drive.
Anyone have a solution? It's Ubuntu 8.0.4 I think.
IP, network outbound BUT NOT INBOUND!!!
Is there another machine with the same IP or MAC address on the LAN? Does the host report anything strange network wise? There isn't a whole lot on the JumpBox itself that would explain this behavior. Your virtualization software is responsible for connecting the JumpBoxes network interface to your actual network and your network configuration is either statically set or assigned by DHCP. If its static and you didnt change it, its not changed. If its DHCP, then has the DHCP server been misconfigured?
Like you said, there should be no firewall, because we don't enable it by default.
Austin