Working Pc no longer talking to domain

  • Thread starter Thread starter Kenneth Keeley
  • Start date Start date
K

Kenneth Keeley

Hi,
I have got a pc that was working fine on friday and now it wont talk to
the domain at all. I can ping the pc's Ip address and computer name and it
responds. But it cannot see or be seen from the domain computers.

The system event log is showing lots of these types of messages some of them
appear about every 15 seconds.

7/02/2005 9:12:39 AM Tcpip Information None 4202 N/A ENA183 The system
detected that network adapter Realtek RTL8139(A) PCI Fast Ethernet Adapter
was disconnected from the network, and the adapter's network configuration
has been released. If the network adapter was not disconnected, this may
indicate that it has malfunctioned. Please contact your vendor for updated
drivers.

7/02/2005 9:12:29 AM Tcpip Information None 4201 N/A ENA183 The system
detected that network adapter Realtek RTL8139(A) PCI Fast Ethernet Adapter
was connected to the network, and has initiated normal operation over the
network adapter.

7/02/2005 9:11:07 AM Server Error None 2504 N/A ENA183 The server could not
bind to the transport
\Device\NetBT_Tcpip_{7D1AA570-93D0-406A-B5AE-A795F1D3775B}.

The Application log shows errors like
7/02/2005 8:37:35 AM UserInit Error None 1001 N/A ENA183 Could not locate
the script command lines in the Group Policy Object.

7/02/2005 9:18:17 AM Userenv Error None 1000 NT AUTHORITY\SYSTEM ENA183
Windows cannot access the registry information at
\\MyDomain.com\SysVol\MyDomain.com\Policies\{5D9FABEE-725D-4EC0-B197-E6B8274
5E0C7}\User\registry.pol with (1231).

7/02/2005 10:56:25 AM Userenv Error None 1000 NT AUTHORITY\SYSTEM ENA183
Windows cannot access the registry information at
\\MyDomain.com\sysvol\MyDomain.com\Policies\{31B2F340-016D-11D2-945F-00C04FB
984F9}\Machine\registry.pol with (1231).
 
Kenneth said:
Hi,
I have got a pc that was working fine on friday and now it wont
talk to the domain at all. I can ping the pc's Ip address and
computer name and it responds. But it cannot see or be seen from the
domain computers.

The system event log is showing lots of these types of messages some
of them appear about every 15 seconds.

7/02/2005 9:12:39 AM Tcpip Information None 4202 N/A ENA183 The system
detected that network adapter Realtek RTL8139(A) PCI Fast Ethernet
Adapter was disconnected from the network, and the adapter's network
configuration has been released. If the network adapter was not
disconnected, this may indicate that it has malfunctioned. Please
contact your vendor for updated drivers.
Click to expand...

<snip>

Did you try updated drivers? Try replacing the NIC?
 
Kenneth Keeley said:
Hi,
I have got a pc that was working fine on friday and now it wont talk to
the domain at all. I can ping the pc's Ip address and computer name and it
responds. But it cannot see or be seen from the domain computers.

The system event log is showing lots of these types of messages some of them
appear about every 15 seconds.

7/02/2005 9:12:39 AM Tcpip Information None 4202 N/A ENA183 The system
detected that network adapter Realtek RTL8139(A) PCI Fast Ethernet Adapter
was disconnected from the network, and the adapter's network configuration
has been released. If the network adapter was not disconnected, this may
indicate that it has malfunctioned. Please contact your vendor for updated
drivers.

7/02/2005 9:12:29 AM Tcpip Information None 4201 N/A ENA183 The system
detected that network adapter Realtek RTL8139(A) PCI Fast Ethernet Adapter
was connected to the network, and has initiated normal operation over the
network adapter.

7/02/2005 9:11:07 AM Server Error None 2504 N/A ENA183 The server could not
bind to the transport
\Device\NetBT_Tcpip_{7D1AA570-93D0-406A-B5AE-A795F1D3775B}.

The Application log shows errors like
7/02/2005 8:37:35 AM UserInit Error None 1001 N/A ENA183 Could not locate
the script command lines in the Group Policy Object.

7/02/2005 9:18:17 AM Userenv Error None 1000 NT AUTHORITY\SYSTEM ENA183
Windows cannot access the registry information at
\\MyDomain.com\SysVol\MyDomain.com\Policies\{5D9FABEE-725D-4EC0-B197-E6B8274
5E0C7}\User\registry.pol with (1231).

7/02/2005 10:56:25 AM Userenv Error None 1000 NT AUTHORITY\SYSTEM ENA183
Windows cannot access the registry information at
\\MyDomain.com\sysvol\MyDomain.com\Policies\{31B2F340-016D-11D2-945F-00C04FB
984F9}\Machine\registry.pol with (1231).
Click to expand...

I would try a different network adapter.
 
Pegasus (MVP) said:
I would try a different network adapter.
Click to expand...
If it is the network adapter why has it just strated doing this today?

Will this fix the problem as the office this computer is in is 100 km away
and I don't want to drive all the way out there to find out that there is
more wrong than just that.

Thanks
 
Kenneth Keeley said:
If it is the network adapter why has it just strated doing this today?

Will this fix the problem as the office this computer is in is 100 km away
and I don't want to drive all the way out there to find out that there is
more wrong than just that.

Thanks
Click to expand...

There is no guarantee that replacing the network adapter will
fix the problem. This is why I have lots of things in my tool
case: Network adapters, Win2000 installation CDs, CDs
with lots of drivers and diagnostic tools, a laptop with network
sniffing software loaded, a spare disk, a Bart CD, a power
supply, CAT5 cable tools etc. etc. My own clients are within
a radius of 20 km. In view of the distance, your tool kit should
be even more comprehensive. I wouldn't go travel to your
remote site without a spare PC or without disk cloning tools.
 
Pegasus (MVP) said:
There is no guarantee that replacing the network adapter will
fix the problem. This is why I have lots of things in my tool
case: Network adapters, Win2000 installation CDs, CDs
with lots of drivers and diagnostic tools, a laptop with network
sniffing software loaded, a spare disk, a Bart CD, a power
supply, CAT5 cable tools etc. etc. My own clients are within
a radius of 20 km. In view of the distance, your tool kit should
be even more comprehensive. I wouldn't go travel to your
remote site without a spare PC or without disk cloning tools.
Click to expand...
I do carry a large amount of stuff with me when I go out to this site, the
only problem is that it normally means that I am away from my base site for
at least the whole day. At the moment I cannot afford to be away from the
base Site for that long.

Thanks
 
I suspect that your basic problem is the loss of connection/restored
connection messages. When you find out why this particular PC keeps popping
on and off the network and fix that problem you will most likely resolve all
the rest. A bad network card, bad cabling, or bad network device
(router/hub/switch/etc) is the mot likely cause.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm
 
Kenneth said:
I do carry a large amount of stuff with me when I go out to this
site, the only problem is that it normally means that I am away from
my base site for at least the whole day. At the moment I cannot
afford to be away from the base Site for that long.

Thanks
Click to expand...

Since the cause of the problem is most likely something physical (NIC,
cabling, etc), there isn't much choice, unless you can get someone else into
that office to do the work. Is there another PC in that office that the user
can use in the meantime? Always good to have a spare or two.
 
Kenneth,

Sometimes things break.. It happens...

SO... Start working this up the Stack..

Start with the Physical layer... Check the Cable, then the card then the
port it is plugged into...

Once you know that is all working, move to the drivers and configurations...
 
Ryan Hanisco said:
Kenneth,

Sometimes things break.. It happens...

SO... Start working this up the Stack..

Start with the Physical layer... Check the Cable, then the card then the
port it is plugged into...

Once you know that is all working, move to the drivers and
Click to expand...
configurations...

If it is a hardware issue then why can I ping the device with good response
times and no drop outs. I would have through that the card would be dropping
out ping packets as well.
 
Kenneth said:
If it is a hardware issue then why can I ping the device with good
response times and no drop outs. I would have through that the card
would be dropping out ping packets as well.
Click to expand...

Not necessarily. You'll really never know what's going on unless you can get
your hands on this PC directly & do isolation testing.
 
Back
Top