Virtual Machine Redhat 9 networking issue
I know this looks like a lot to read, but I really need help with this issue.
I am having a weird issue with Redhat 9. I am using Virtual Machines. I have created a Windows Server 2003, gave it the necessary roles to become a router. I can use the server as a router efficiently with a Windows XP machine, but not with my Redhat 9. I can ping the NIC on the same network as my Redhat 9, and I can ping the NIC that is bridged, but it is as if my Server doesn't know how to route my Redhat 9 machine. In hope to resolve the issue, I tried to take the Server out of the picture. I bridged the Redhat 9's NIC and attempted to connect to the internet, and the issue continued. I looked for information about this problem and found this information: To work around this problem, become root (su -) and use a text editor to edit the following files in the guest operating system. If only one of these files exist, make the change for that file only. /etc/sysconfig/network-scripts/ifcfg-eth[n] /etc/sysconfig/networking/devices/ifcfg-eth[n] In both cases, [n] is the number of the Ethernet adapter - for example, eth0. Add the following section to each of these two files: check_link_down () { return 1; } This did not fix the issue. I need some major help to fix this issue. I appreciate your input, and please don't tell me to upgrade to a more current version of Linux like Fedora 11. This is for my job and it is a training exercise. |
Hello lordofall20 :)
Difficult to answer without more informataion. Which is the host and which the guest(s)? What type of networking is configured on the host for the VMs to use (default of VBox acting as a NATting router or bridged)? How do all the NICs (real and virtual) get their IP addresses? Which network nodes you want to communicate with which other network nodes, on the Internet, the real LAN and (if you have one) on the virtual LAN -- and via port forwarding or directly? Probably more later but that's a good start. Best Charles |
Question 1:Neither is the host, they are both VMs on another server in which I do not no the OS. I beleive it is like Server 2005.
Question 2: The server is acting as a bridged router. Question 3: The Windows Server 2003 leases DHCP. Question 4: I beleive the way I need to answer this question is, the Linux box is on a VMnet that only has that Linux box and one of the NICs from the Server. The server is bridged and set to bypass a proxy, which would then send the connection through a firewall, then to the internet. The proxy is set to not block anything, but it will give a suffix if the if the computer does not have one in its domain. The proxy will also block the connection if the suffix is not of its domain, so I took the suffix off of my Redhat 9. Thanks! |
Hello lordofall20 :)
Quote:
Best Charles |
Ok... I have tried something different on another VM. I installed Fadora 11, and I attempted to bridge(with a fresh install, the only thing that has been configured is both of the proxies, and i activated the network service). I am lost on getting Fadora on the internet through VMWare
|
Hello lordofall20 :)
Quote:
The new situation is you have some version of Fedora running in a virtual machine provided by some version of VMware running on an unspecified host (which may be like "Server 2005") using bridged mode networking between guest and host with two proxies somehow involved and an unspecified configuration of the virtual adapter and you are unable to "get Fadora on the internet" presumably hoping to do so over an unspecified link to the Internet from the host. It is not clear whether "get Fadora on the internet" means accessing nodes on the Internet from Fedora or it means access Fedora from a node on the Internet and what sort of connection is being attempted: ping, HTTP, FTP etc? That's kind of vague. Maybe that's why nobody else is pitching in. Try posting in the ESP and Clairvoyance forum. Best Charles |
I was trying to just access the internet via web browser from the Fedora 11 OS. I discovered the problem this morning though. :D (<--HAPPINESS) For some dumb reason, when the Fedora was receiving a DHCP address, it wasn't receiving the DNS information. The way I figured this out is because, as a last resort, I put an entry(the proxy server) in the hosts file. I then proceeded to access the internet via Firefox, and it worked. I hope this helps others that are having this very stupid error in with the DHCP not supplying the DNS information to Fedora 11. Co-workers think that the cause of this error is marketing, so that people will get frustrated with Fedora and go to Redhat Enterprise for the support.
Thank you for replying Charles! WOOT! (the other team was Fedora!) <--LOL |
This was the fix!
Thank you so very much, for posting that reply.
Although my RHEL 5.10 isn't a virtual, I was having the same problem, then I read your post. I edited those files (which was weird because after I edited the first, the second already showed what I put in on the first, and the files aren't linked).... I rebooted and no longer having that issue... Just wanted to tip my hat to you and thank you for your solution: it works! Tom |
All times are GMT -5. The time now is 07:36 PM. |