• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 345
  • Last Modified:

Static IP assigned but not connectivity

I've got a Windows 2003 Server that has a static IP that suddenly can't connect to anything, and nothing can connect to it. (ie ping, rdp, etc)

ipconfig /all confirms all setiings, nothing has changed, and the lower right hand icon indicates that the network connection is connected.

Any ideas?  I've disabled/re-enabled, shutdown/restarted, reassigned the same IP settings, etc, but no change.
0
gunschee
Asked:
gunschee
  • 5
  • 3
  • 2
2 Solutions
 
Paul MacDonaldDirector, Information SystemsCommented:
Is the subnet mask correct?

Is the default gateway correct?

Can you try plugging it in to a different port on your switch?
0
 
gunscheeAuthor Commented:
Subnet and gateway are correct.  I'll try a different switch port.
0
 
gunscheeAuthor Commented:
That didn't fix it.
0
Cloud Class® Course: C++ 11 Fundamentals

This course will introduce you to C++ 11 and teach you about syntax fundamentals.

 
Paul MacDonaldDirector, Information SystemsCommented:
Is it single-homed?  That is, it only has one network connection?

Are you certain all the cables are good.  It's rare, but they can go bad.

Can you replace the NIC (or add an alternate)?



0
 
dosdet2Commented:
Do you have more that one NIC card in the machine?

Can you ping out - say to the default gateway?

0
 
gunscheeAuthor Commented:
Can not ping out, can not ping it.  When I ping 127.0.0.1 it returns so it seems that the IP Stack is ok.  Machine is single-homed.  

And now one of the clients (Win 7) on the floor is having the exact same issue.

Could it be a bad windows update?  I searched the forums and couldn't find anything.
0
 
Paul MacDonaldDirector, Information SystemsCommented:
It could be a problem with a driver.  That's why I suggested trying a new NIC.  Can you try rolling back whatever driver you're using?  

There's no chance you're running a local (software) firewall is there?  Either Windows or something else? ZoneAlarm, maybe?
0
 
gunscheeAuthor Commented:
Oh I forgot, popped in a new NIC yesterday.  No change....  :-(
0
 
dosdet2Commented:
The client machine with the same issue is curious.  This may or may not help. but for safety sake, I would install a fresh download (since it can't update) of malwarebytes and run a full scan.  If that turns up clean, then we can continue with other things.

One test you can do if you have the equipment, connect a PC directly to the server via crossover cable or through a small dedicated switch.  There should be nothing else connected.  Set the PC with a static IP that matches your gateway IP & mask.  Set the default gateway (on the PC) to the IP of the server.  Then see if the machines can ping each other.  If they can, then the problem is outside the server box.  If they can't, then it is inside the box.  Make sure that the cable(s) and switch used are known good.

Kind of a pain but it narrows down the possibilities.
0
 
gunscheeAuthor Commented:
Thanks guys.  Tried everything above, and ended up restoring the Windows directories from a recent backup and that did the trick.

it must of restored something that corrupt with some files.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Ruby Fundamentals

This course will introduce you to Ruby, as well as teach you about classes, methods, variables, data structures, loops, enumerable methods, and finishing touches.

  • 5
  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now