Network problem on POWEREDGE T110, OS Win server 2008

Nobody has an idea ? :emotion-6:

Are you running Server 2003?  How did you install it?

I am having this exact same issue, and I would dearly love to hear a solution.

Dell says to take it up with my ISP.  My ISP says it's working fine, and I should call Dell.

This is a new Poweredge T110 that has never worked.  I've been trying to set it up for a week now.  When I use DHCP, it can connect to all network resources, including the Internet.  When I use static IP, it loses all network connection, as if the network cable were unplugged.

Running Windows Server 2008 R2 Foundation Edition.  Originally preinstalled by Dell, but when my attempts to fix the issue (under guidance of Dell's tech support) got to the point where it could no longer connect to the network even using DHCP, I reinstalled from the DVDs packed with the server.

Now I'm back to the original problem.  No network connection at all when configured for static IP.

Actually, Dell has not suggested anything other than that it's a problem for my ISP to solve.  I've called my ISP three times,and come away each time more convinced that it's not their issue.

Firmware on the NIC is next on my list.

I get the impression that Dell tech support believes:

1. It's a new computer (mfg date 12/13/2010), therefore there can be nothing wrong with it.
2. If it powers up and displays its desktop and the NIC's light is on, it's not their problem.

Maybe I need a computer without a "13" in its manufacture date.

Having spoken with Dell, I would assume you have tried most of this:

Firmware updates (BIOS/ESM and NIC, particularly on the Broadcom's)?
Driver updates (chipset and NIC in particular)?
Have you tried setting static with an add-in NIC?
Has Dell replaced the motherboard?

So, your ISP is providing DHCP services?  If so, does the DHCP server require a device to obtain an IP from the DHCP server? 

Do you have another router/hub floating around?  If so, can it speak to another computer connected to that router/hub with static IP's?  If so, I would assume your ISP's DHCP server has a setting to restrict non-DHCP devices from using the network.  If you still have the same type of issue with network connectivity, then I would assume it is your server (most likely hardware, if everything is updated).

Try updating the drivers (chipset then NIC), then update the firmware (BIOS, then ESM, then NIC).  If that doesn't work, then pursue a hardware issue with Dell.  Escalate it for review by an analyst.

My ISP (Comcast digital cable) provides static IPs all the time.  They're the ones who assigned it, so yes, they support non-DHCP devices all the time.

My next "troubleshooting" steps (in quotes because I expect to have no trouble) are:

1. Assign the Comcast-generated static IP to another computer on the network, just to prove that our router does indeed allow such a device on the network.
2. Plug the server and one other PC into an isolated router (no internet, no connection to any other network or devices) to prove that the server fails to connect to even the most rudimentary network when set for static IP.  (Of course, I'll first have to prove that it works correctly on this network with DHCP.  With no attached DHCP server, it should just use its "default" IP address.)

But the next real step is to check for new firmware for the NIC.

Tomorrow.  Working on other crises tonight.

Had this issue with 2008 a few times....

I ended up uninstalling the driver/management software. Then went into the registry, removed all entries referring to Broadcom, rebooted, added just the bare driver.

The other fix is to get a mature NIC, such as an Intel, disable the onboard, and install the Intel. Really don't know why Dell uses a wanna be like Broadcom. Do they really save that much money with all the tech calls?

I have no idea why, but the problem suddenly went away.

Before any of my "testing" that I planned to do, I simply set the static IP one more time and confirmed that I couldn't see any network resources.  Pinged the gateway, the DNS server, etc.

One thing I did this time that I had not done before was that I pinged my loop-back address: 127.0.0.1.

I got replies, and no losses!

Suddenly, I noticed that the network icon in the tray had changed from "no network" to "local and internet."

Repeated my pings, and all resources replied.  I was now able to access the Internet, and file shares on the LAN.

Set the NIC back to dynamic IP, checked everything again, then set back to the static IP.

Everything worked, without my having to ping the loop-back.

Rebooted the server, and everything still worked.

I can't believe that simply pinging 127.0.0.1 really fixed it, but it suddenly started working as advertised, without my having to update drivers or firmware or anything.

Now I can't replicate the malfunction.

I dunno!

Were your servers built on the 13th, too?

Maybe it the same Broadcom phenomenon I ran into a couple time. I was able to get past the problem on a couple of servers without cleaning the registry, just by reinstalling the driver, but i took 2-3 reboots for the issue to clear up; good part is once it clears up, your good for gold..... It the Twilight Zone.

Was that the date or the assembly line number?

Nothing to do with the build, just with 2008 and the driver, never had this with win 2000 or 2003.

I bought a Dell PowerEdge T110 Tower Server.
I have some Programs still run under windows 2000 server.
I tried to Install Win2000 Server but i can not.
( Plz see the Blue Error Window ==> attached Pic.  )

So please help me to find way to install windows 2000 server

Please help me

Thanks too much