jkramer55 wrote on Tuesday, March 08, 2011:
I can’t seem to get my virtual machine to talk to the internet. When I start the OpenEMR appliance in VMPlayer, I enter the given address into my browser (doesn’t matter which browser I use) and it says it cannot connect to the site. When I admitted I was a wimp and attempted desktop installation, I got a lot of “Could not resolve ‘us.archive.ubuntu.com’” messages. Any ideas?
tmccormi wrote on Tuesday, March 08, 2011:
The link you need to browse to on the virtual machine will be a IP Address, like http:/192.168.1.100/openemr/, Look at the bootup screen and it will give you the address to use.
-Tony
jkramer55 wrote on Tuesday, March 08, 2011:
Oh would that it were that simple.
yehster wrote on Tuesday, March 08, 2011:
Log into the virtual appliance and type:
ifconfig
from terminal/console/bash
That will tell you the IP Address the machine is using.
jkramer55 wrote on Tuesday, March 08, 2011:
I know the IP address. It’s that I’m getting “Unable to connect”.
yehster wrote on Wednesday, March 09, 2011:
Check your network adapter settings in the VMWare player virtual machine settings. What is it set to? It needs to be either bridged or NAT for the virtual machine to be able to get to the rest of the world.
Your description of your problem doesn’t make it clear if the problem you are having is with the virtual machine getting to the rest of the world, or your host machine simply can’t access the virtual machine, or both.
jkramer55 wrote on Wednesday, March 09, 2011:
Kevin,
The reason it is unclear is that I don’t know. It just seems to me that my virtual machine cannot access the internet. My network settings are Bridged with the “Replicate physical network connection state” box checked. I’ve tried all of the settings to no avail.
Thanks, Joe
yehster wrote on Wednesday, March 09, 2011:
Start a command prompt and then issue the command
ping <Virtual Machine IP Address>
i.e.
ping 192.168.1.101
and let us know what happens. That should give you information about whether the host machine sees the vm at all.
Similarly, from a console in your virtual machine try pinging the hostmachine’s ip address and then try pinging something off on the internet.
e.g.
ping 18.241.0.1
jkramer55 wrote on Thursday, March 10, 2011:
When I ping an IP address, I get “Network is Unreachable”. When I ping my openemr IP, I get a string of “64 bytes from 127.0.0.1: icmp_seq=NN ttl=64 time=N.NNN ms”. It just kept doing (in a loop) that until I shut it down. By then it had reached icmp_seq=500.
yehster wrote on Thursday, March 10, 2011:
What is your host OS? and is 127.0.0.1 the address you think is your openemr IP? did you try to use that in the url to reach the webserver from your browser?
that is definitely not the correct ip address as that is the loopback address.
http://en.wikipedia.org/wiki/Localhost
jkramer55 wrote on Thursday, March 10, 2011:
I am running Windows 7 on the host. When I start the appliance I get “The IP address of this appliance is:127.0.0.1”.
yehster wrote on Thursday, March 10, 2011:
Log on to the appliance and from the command line issue the command
ifconfig
you should get something like this:
the inet addr for eth0 is what you need to use for the ipaddress. If there is no eth0, then I’m not sure what to do.
yehster@openemr:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:0c:29:7e:07:58
inet addr:192.168.75.129 Bcast:192.168.75.255 Mask:255.255.255.0
inet6 addr: fe80::20c:29ff:fe7e:758/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:44445 errors:0 dropped:0 overruns:0 frame:0
TX packets:13977 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:5905182 (5.9 MB) TX bytes:5231373 (5.2 MB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:95267 errors:0 dropped:0 overruns:0 frame:0
TX packets:95267 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:94041747 (94.0 MB) TX bytes:94041747 (94.0 MB)
bradymiller wrote on Thursday, March 10, 2011:
hey,
First, try this within the appliance (as the root user) and then restart the appliance (sometimes when you move the appliance to another directory it can cause issues that this will solve):
rm -f /etc/udev/rules.d/61-net_config.rules
If above does not work, then likely a network issue. The appliance is like another computer (in bridged mode), so your network will treat it like a computer. In most situations, this means it gets assigned an IP address via DHCP (from a router). Some work environments may not be as forgiving (ie. not allow new computers on the network by not providing IP addresses to them). Provide a quick description of your network.
-brady
jkramer55 wrote on Thursday, March 10, 2011:
Kevin, I ran the ifconfig and got no eth0
Brady, I ran the rm command to no avail. I’m at home. My computer is wired to a router which is wired to a cable modem.
yehster wrote on Thursday, March 10, 2011:
What this means is that your VM has no ethernet adapter configured to the outside world. I suggest that you try switching the network connection to NAT from bridged mode, reboot the VM and try ifconfig again and see if it can detect a virtual ethernet adapter in that mode.