NIC stops working when hosting a server.

March 24, 2011 at 05:57:37
Specs: Windows XP, AMD Phenom II X2 555
On Windows XP, my integrated NIC stops working after hosting a server. The server starts fine, ports are forwarded, firewall is down, modem is fine, but when I receive a connection, it shows they have made a connection, but then they drop, as do I. I can't browse or ping anywhere. I have to physically disconnect, then reconnect the ethernet cable to the port, or restart the computer. Upon ipconfig, the adapter is set with the Windows default ip (169.x.x.x) and cannot be /release'd or /renew'd. What could be causing this to happen?

See More: NIC stops working when hosting a server.

Report •

#1
March 24, 2011 at 06:55:08
Some ISPs block port 80.

How do you know when a politician is lying? His mouth is moving.


Report •

#2
March 24, 2011 at 12:47:50
That's not the problem. I can host the server fine on my laptop wirelessly.

Report •

#3
March 24, 2011 at 14:37:52
Look at the event viewer for errors.

How do you know when a politician is lying? His mouth is moving.


Report •

Related Solutions

#4
March 24, 2011 at 14:49:41
During a test, I started the server and attempted to connect to it using my laptop to reproduce the error. Event viewer only gave me this when I lost connection:

Event Type: Failure Audit
Event Source: Security
Event Category: Policy Change
Event ID: 615
Date: 3/24/2011
Time: 5:44:57 PM
User: NT AUTHORITY\NETWORK SERVICE
Computer: SHUPC
Description:
IPSec Services: IPSec Services failed to get the complete list of network interfaces on the machine. This can be a potential security hazard to the machine since some of the network interfaces may not get the protection as desired by the applied IPSec filters. Please run IPSec monitor snap-in to further diagnose the problem.


Report •

#5
March 24, 2011 at 14:57:50
Actually, I don't think IPSec has anything to do with it. After looking at the Event Viewer again, the same error occurred sometime after the test, so it must not be related. Also I stopped and disabled the IPSec service in services.msc for testing purposes. Same result, same issue.

Report •

#6
March 24, 2011 at 16:58:48
If you don't think that IPSEC has anything to do with it, what other firewalls or security programs are running? Norton is good to kill everything.

How do you know when a politician is lying? His mouth is moving.


Report •

#7
March 24, 2011 at 18:03:40
Firewalls are down, and Microsoft Security Essentials is disabled.

Report •

#8
March 24, 2011 at 18:25:08
I'm running out of ideas. Go to the device manager, network adapters, double click on the adapter & go to the power management tab. Make sure that the box is not checked to allow this device to be shut to save power.

How do you know when a politician is lying? His mouth is moving.


Report •

#9
March 24, 2011 at 18:56:19
EDIT: False alarm. It works longer than before, but produces the same error.

Report •

#10
March 24, 2011 at 22:01:58
Try it again & watch the performance screen in the task manager when you do it. Does the memory or CPU jump?

How do you know when a politician is lying? His mouth is moving.


Report •

Ask Question