C
cathalo
Greetings,
History:
I've replaced a PC at work that previously had Windows 2000 on it with
something a little faster with XP. The soul purpose of this machine is it
monitors a Controlled Atmosphere system and records room information to a
backend access DB.
The previous machine had issues connecting to network resources; but could
always be connected to via our main server. This worked as I pulled the
Access DB from this machine to a folder daily to make sure it was on the tape
backup.
Problem:
With the replacement of the machine - I started to see the errors (listed at
end of msg) after about 2 days of uptime. The machine would not be reachable.
When going the machine I would see the following messages + AutoEnrollment
ones. A reboot would fix the machine for 2 days.
Troubleshooting Attempted:
I was reading all sorts of goodies on this. I wasn't sure where to start. I
did a few LANSERV property changes in the registry, I turned off
autoenrollment. I forced a gpupdate /force after a release/renew every couple
hours - still no change.
The machine has a serial based application that also authenticates through
an 25-pin WBKEY. I thought this is the problem directly; but did not have
spare to troubleshoot with.
I ripped the Network Card and modem out of the machine - as I thought maybe
the driver for each had memory leakage. This seemed to resolve the problem.
However I needed network connectivity for backup and remote monitoring.
I purchased a new Intel Nic and driver to replace the cheap DLink. Installed
the NIC and left the network cable unplugged. Ran for 3 days without any
errors in event log or noticable issues.
2 days ago I plugged the network cable back in - and now I have the errors
again.
With a reboot fixing.
Conclusion Thus Far:
I have two thought,
a) Active Network Card and WBKEY driver (which also has network
features) are causing a conflict or memory resource issue.
b) Bad network drop / or interferance on the line causing the machine
to crap out.
Any suggestions?
---------------------------------------------------------------------------------
Event Type: Error
Event Source: Srv
Event Category: None
Event ID: 2019
Date: 8/13/2009
Time: 8:34:13 AM
User: N/A
Computer: CA-HEADOFFICE
Description:
The server was unable to allocate from the system nonpaged pool because the
pool was empty.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 04 00 01 00 54 00 ......T.
0008: 00 00 00 00 e3 07 00 c0 ....ã..À
0010: 00 00 00 00 9a 00 00 c0 ....š..À
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: 02 00 00 00 ....
Event Type: Warning
Event Source: Dhcp
Event Category: None
Event ID: 1003
Date: 8/13/2009
Time: 9:56:09 AM
User: N/A
Computer: CA-HEADOFFICE
Description:
Your computer was not able to renew its address from the network (from the
DHCP Server) for the Network Card with network address 001B213E236C. The
following error occurred:
An operation was attempted on something that is not a socket. . Your
computer will continue to try and obtain an address on its own from the
network address (DHCP) server.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 36 27 00 00 6'..
History:
I've replaced a PC at work that previously had Windows 2000 on it with
something a little faster with XP. The soul purpose of this machine is it
monitors a Controlled Atmosphere system and records room information to a
backend access DB.
The previous machine had issues connecting to network resources; but could
always be connected to via our main server. This worked as I pulled the
Access DB from this machine to a folder daily to make sure it was on the tape
backup.
Problem:
With the replacement of the machine - I started to see the errors (listed at
end of msg) after about 2 days of uptime. The machine would not be reachable.
When going the machine I would see the following messages + AutoEnrollment
ones. A reboot would fix the machine for 2 days.
Troubleshooting Attempted:
I was reading all sorts of goodies on this. I wasn't sure where to start. I
did a few LANSERV property changes in the registry, I turned off
autoenrollment. I forced a gpupdate /force after a release/renew every couple
hours - still no change.
The machine has a serial based application that also authenticates through
an 25-pin WBKEY. I thought this is the problem directly; but did not have
spare to troubleshoot with.
I ripped the Network Card and modem out of the machine - as I thought maybe
the driver for each had memory leakage. This seemed to resolve the problem.
However I needed network connectivity for backup and remote monitoring.
I purchased a new Intel Nic and driver to replace the cheap DLink. Installed
the NIC and left the network cable unplugged. Ran for 3 days without any
errors in event log or noticable issues.
2 days ago I plugged the network cable back in - and now I have the errors
again.
With a reboot fixing.
Conclusion Thus Far:
I have two thought,
a) Active Network Card and WBKEY driver (which also has network
features) are causing a conflict or memory resource issue.
b) Bad network drop / or interferance on the line causing the machine
to crap out.
Any suggestions?
---------------------------------------------------------------------------------
Event Type: Error
Event Source: Srv
Event Category: None
Event ID: 2019
Date: 8/13/2009
Time: 8:34:13 AM
User: N/A
Computer: CA-HEADOFFICE
Description:
The server was unable to allocate from the system nonpaged pool because the
pool was empty.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 04 00 01 00 54 00 ......T.
0008: 00 00 00 00 e3 07 00 c0 ....ã..À
0010: 00 00 00 00 9a 00 00 c0 ....š..À
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: 02 00 00 00 ....
Event Type: Warning
Event Source: Dhcp
Event Category: None
Event ID: 1003
Date: 8/13/2009
Time: 9:56:09 AM
User: N/A
Computer: CA-HEADOFFICE
Description:
Your computer was not able to renew its address from the network (from the
DHCP Server) for the Network Card with network address 001B213E236C. The
following error occurred:
An operation was attempted on something that is not a socket. . Your
computer will continue to try and obtain an address on its own from the
network address (DHCP) server.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 36 27 00 00 6'..