Debian network issue

Overview:
I have an old Debian 3.1 server running vmware server and several VM's.  It has been working fine for years with absolutely no issues.  Yesterday we had to shut it down to move it to a different location.  When we brought it back up, it is able to ping on the local network but not get to the internet.  My predecessor was fanatical about security and notorious for "quick fixes" so I am thinking that he either made a change that wasnt committed and thus lost on reboot or he has some hard-coded MAC address somewhere thats keeping this machine from getting to the internet.  

Symptoms:
The machine cannot get a DHCP address from the DHCP server (even though it can ping it)
The Machine can PING the gateway and all machines on the LAN but cannot get to the internet
I forgot to add that upon reboot we were getting this error: "tg3 tg3_stop_block timed out"

I googled till my fingers bled but couldnt find a good solution.  

Troublehooting so far:
This is usually a gateway or subnet mask issue and I have quintuple checked both
PS -aux does not show iptables or ipchains running
issuing an Iptables command results in "command not found"
issuing an ipchains command results in a "not compatible with this kernel"
I have not been able to find any other firewall related configuration
Multiple other machines plugged into the same switch can successfuly receive DHCP addressing
Those machines can also get to the internet just fine

Does anyone have any advice at all? I have been working on this for about 42 hours straight and am at my wits end.  Are there any other services that could be stopping the box from getting to the internet? I would be so appreciative for any nudge in the right direction!
wintlandAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

neubdaCommented:
I would troubleshoot like this...
1. checking /etc/network/interfaces for some funny configuration
2. starting "tcpdump -i any -n port 67" on the failing pc and dhcp server - are the dhcp requests even reaching the dhcp server? maybe there is a reservation configured on the dhcp?
3. checking "/sbin/iptables -L" or maybe even "/sbin/iptables -t nat -L" for missconfiguration
4. dont remember if debian 3.1 had already udev but if it has, try clearing the network entry in "/etc/udev/rules.d/70-persistent-net.rules"
5. checking "ps aux" for some unwanted services
6. checking if only icmp to other hosts is working or tcp or udp too

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
berlincountCommented:
Please make sure that both the DHCP server and the virtual machine are connected to the same virtual LAN, and that the DHCP server is actually running on the (virtual) interface connected to this virtual LAN.

The DHCP server has to be in the same broadcast domain as the DHCP client. Reachable via routing isn't enough, i.e. you'd need to use 'arping' instead of 'ping' to verify correct connectivity for this usecase.
Syngin9Commented:
It the gateway hardware isn't the same identical hardware, I'd compare the configs on both.
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

furettoCommented:
I believe that posting the output of:

netstat -nr
ifconfig
iptables -L -n
iptables -L -n -t nat

will help any of us to get a better idea of what's going on.

To me it looks like the gateway paramete is not correct.
Syngin9Commented:
Or post the contents of /etc/network/interfaces
wintlandAuthor Commented:
I ifdownd eth0 and brought up eth1 and it works perfectly...no idea what was going on but I am not going to troubleshoot further since this is a temporary install.  

Thanks very much for all the responses and help.

-Brian
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Linux

From novice to tech pro — start learning today.