Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 199
  • Last Modified:

Problems with NIC - Server 2003

We have a Fujitsu Server running Windows 2003 Server SP2.  For some reason the server has become unavailable on the network.  You cannot ping in or out of the network.  Only pinging 127.0.0.1 works.  
Things we have tried: -
1.      Driver update
2.      Firmware update
3.      BIOS Reset
4.      Uninstall the Network adaptor/ Reinstalled
5.      Changed switch ports
6.      Checked firewall/AV
The server does see the the PXE server and gets an ip address during a reboot so it looks like a OS issue.
Any ideas?
0
badabing1
Asked:
badabing1
1 Solution
 
GovvyCommented:
Is the switch port on the correct VLAN to be routable? If it sees the PXE server that sounds as though it picks up DHCP details however typically you would move server to non-PXE VLAN once its deployed...
0
 
badabing1Author Commented:
Other servers are fine plugged into this switch.  Also tried other switches and same problem exists. in the event log it logged that Explorer.exe re-initiated which looked to have caused the server to reboot. Since then we have had a problem with the NIC.
0
 
Miguel Angel Perez MuñozCommented:
Has the server another NIC to try? Maybe this is damaged.
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
badabing1Author Commented:
OK - it works in safe mode only
0
 
vivigattCommented:
I guess you mean "Safe mode with Networking support".

So it seems it S some software issue... If you want to be sure, you can boot off some kind of LiveCD (Ubuntu, UBCD4Win) and check the network connectivity then.

It could be some kind of malware. Or the firewall (try to disable it completely), or some network component (filter driver, monitor driver, helper of some kind...). Check all what is bound to the NIC in question and keep only what is really needed (TCP/IP, Windows Network Client, File and Printer sharing, Packet Classifier for instance).

0
 
badabing1Author Commented:
it was the ipsec that was corrupt and blocking inbound and outbound traffic- as work around disabled ipsec service.
0
 
badabing1Author Commented:
as i had to find the solution myself, i have assigned points to myself.
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now