Windows 2008 R2 Server Not obtaining IP4 address on existing network

I have a Windows 2008 R2 Server that works fine at the location where the server was configured. It obtains an IP4 address with no problem from our DHCP Server. It functions properly on our network.

We put the server at a different location.  At this location it will not get on the network. It will not obtain an address from the DHCP server. If we hard code a STATIC address it will still not get on the network.   Other new client computers (Win XP) have no problem obtaining ip4 addresses and getting on.  

There is one other Win 2008R2 server that is our main server/dhcp server.   This was working fine until about 3 months ago. We have tried 3 different servers, swapped cables, tried plugging into a different switch.   If the server is put back on the original network, it works fine so we can rule out nay hardware /cfg issues with the server.
jlauriceIT SpecialistAsked:
Who is Participating?
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.

scrabyCommented:
when you assing a static ip to it, how do you know if it's not on the network.  did you try to ping it from another station?
0
Sid6_7Commented:
Try checking your firewall or Router rules.
0

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
jmcmillan227Commented:
try ipconfig /flushdns at the command line to remove any existing DNS info.  Also in the IP4 Network adapter make sure no specific DNS address is specified and everything is set to obtain automatically
0
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!

jlauriceIT SpecialistAuthor Commented:
What am I looking for in my firewall or router?   There should not have been any changes.

When I set static IP  and do IPconfig, it doesn't even show the address.   It shows a 169.x.x.x address.   And no I cannot ping it and it cannot access other network resources.
0
smckeown777Commented:
What do you mean 'when I set static it doesn't show the address'? That makes no sense at all...

When you set the static and click ok - go back in to the settings again - does it still show the static you've set?

How many nic's on this server?

Post output of

ipconfig/all

from the server when you've set the static so we can see thanks...
0
jlauriceIT SpecialistAuthor Commented:
What do you mean 'when I set static it doesn't show the address'? That makes no sense at all...

What I mean is, when I run IPCONFIG it does not show the address I assigned it. It shows the 169.x.x.x address.   However, when I go back in to the configuration, the address is set correctly.

The server has two nics.  I have tried both, I have tried disabling one.
I have to work on getting ipconfig output, I am not onsite. Thanks.
0
smckeown777Commented:
Is there any 'mac-filtering' or the like on the switches on this site? That's about the only thing I can think of that would result in what you are seeing...

You mentioned 'other' servers - so you've multiple servers with the same issue? Or did I misread that sorry?
0
jlauriceIT SpecialistAuthor Commented:
There is another server which is our main DC on site.  It is working fine. No other issues.

No mac filtering is on.
0
smckeown777Commented:
Cool...and none of your switches are managed? Would be useful to login to the switch to see if its reporting even a connection on the port...

I assume the ethernet port on the server and the switch both light when connected yes?

If this server works on another site fine then as you've said that should eliminate the server from the equation...

'We've tried 3 different servers' - again this points to some sort of filtering I would think - are all servers using the same brand nics? Broadcom or Intel?

What make/model are your switches and router as well just for reference?
0
jlauriceIT SpecialistAuthor Commented:
Switches are not managed.  Getting link light on server and switch.

All servers tried are using same NIC.  Broadcom.

The switches are either Dlink or Dell Powerconnect 2824
0
scrabyCommented:
if you're assigning a static ip and still getting a 169 number then something is not right on the server side.  i don't think this has anything to do with firewalls and switches

169 is a self assigned ip because dhcp failed.  can you attach a print screen of your ip v4 setup under ncpa.cpl?
0
smckeown777Commented:
Might try forcing the nic to sync at Full Duplex(usually set to AutoConfig) might help...

Device manager - right click nic, properties - Advanced - look for the Speed/Deplux setting and force to 1G setting...
0
TomRScottCommented:
I would back up.  You wrote that after assigning a static IP, that an "automatic IP" (169...) was displayed by IPConfig.  That indicates a problem on the server itself. If you can't even set a static IP, any LAN/DHCP issues are irrelevant!

The standard network connectivity diagnostic always starts with "self".  Yes, I usually skip pinging the local host (127.0.0.1), as I would here.  However, setting a static IP then finding an auto IP indicates a NIC or OS issue that should be resolved BEFORE diving headfirst into other network diagnostics that, by every indication from other computers on the LAN, are not required.

Make sure you can set and use a static IP BEFORE you bother with any possible dynamic IP issues.

I would disable all but the NIC you wish to work with.  Note: That on many mult-NIC computers the descriptions doe not match up with physical labeling. This can waste more time.  To avoid confusion, be sure they match up before configuring the wrong one or jacking into the wrong one.

Just because the server used to work on another LAN does not mean it still would work even on the old LAN. Maybe a different NIC was used. Maybe a new NIC driver was updated via Windows Update requiring a full shutdown before it would implement and never implemented until the server was shut down for the move. Maybe the move "shook something loose".

If the old LAN is not too far away, you may consider trying the server back there to rule out network as the issue while you run diagnostics on the server.

Bottom line: When performing diagnostics, simplify wherever possible and change only one thing at a time. This means starting with the server issues, solving them first before messing with LAN diagnostics.

 - Tom
0
ButlerTechnologyCommented:
Any possibility of a third party fire wall rule on the server.  I ran in to an issue where the a third party products set a rule that only allowed the system to talk on a particular subnet.

Tom
0
scrabyCommented:
see if this helps

http://social.technet.microsoft.com/Forums/windowsserver/en-US/70762c1c-da6d-45b7-b3bf-b7079abf8469/windows-server-2008-can-not-see-static-ip

you may also go to device manager, delete both nics, search for hardware to refind them, disable the one that you're not using and set the static ip to the ipv4 settings on the enabled nic.  see where that takes you.  you mentioned the other lan worked fine, are you able to plug back in the other lan, what happens then?
0
scrabyCommented:
this link is talking about something very similar to your situation.  read close to the bottom, maybe this will fix your issue

http://www.techsupportforum.com/forums/f103/having-trouble-setting-static-ip-address-on-server-2008-a-559783.html
0
jlauriceIT SpecialistAuthor Commented:
Problem was due to a faulty SonicWall
0
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
Windows Networking

From novice to tech pro — start learning today.