Failed to initialize the network. Check if another instance of agent is

Question

Out of the blue a small number of my Windows XP PCs get the following error
when logging in. Usually appears while login script page is on screen:-
Failed to initialize the network. Check if another instance of agent is
running. Contact the system administrator
Once XP has loaded ok I can manually start the Remote Management service.
Some PCs are intermittent and don't seem to get it again but a couple get it
every login. I removed the client and reinstalled. I removed the Remote
Management service and re-installed. Re-registered the PC Workstation but no
change for those who get it every day.
I did find this:-
Failed to initialize the network. Check if another instance of agent is
running. Contact the system administrator
Source: Remote Management Agent
Severity: Critical
Possible Cause: The Remote Management Agent is unable to bind to the IPX or
IP port that is being used for Remote Management service, or the ports are
being used by some other application running on the managed workstation.
Action: Uninstall any third-party remote control agent or remote control
application using these ports from the managed workstation.
Possible Cause: The protocol stack is corrupted.
Action: Reinstall the protocol stack.
Possible Cause: The managed workstation is not connected to the network, or
the network is down.
Action: Connect the managed workstation to the network.
I don't have any third party remote control agent installed and I've tried
the refresh of the IP protocol stack. Surprised this has started as we have
not made any changes to the network or software. We run NW Client 4.83sp1
and NW5.1 sp5.
Anybody else had this and cleared it completely?

Answer 1

Further developments:
It looks like it's a fault in the nic. it's a Compaq NC3120 Fast Ethernet
card. It used to work, but since I've wiped out the card drivers that were
in use, I'm at HP's mercy. They are telling me that the card is no longer
under warranty and won't even tell me what driver to look for. Anything I've
managed to find has the exact same symptoms:
Client works, ping to IP addresses work, ping to www.yahoo.com (etc) doesn't
work, although winipcfg shows a DNS server the same as every other machine I
have.
Internet explorer doesn't work, even with IP addresses to local servers.
And of course, zenrc32 doesn't work, wsreg32 doesn't work.
Does anyone know of a way of making the NC3120 work on a win98 machine?
Shall I just go buy a couple dozen netcards from a more reputable company
than compaq?
Chris Denby
IT Coordinator
Rainy River District School Board
Fort Frances, Ontario
Canada
"Chris Denby" <[email protected]> wrote in message
news:[email protected]...
> I have this message on windows 98. In addition to that, the wsreg32.log
> reads work station import error -1 (UNKNOWN).
> This happened after ghosting down to the machine and finding that it had a
> different card. The client adapted easily to a new card, but the
zenrc32.exe
> won't run.
>
> I've checked to make sure it wasn't running by renaming the zenrc32.exe to
> zenrc32.ex so it wouldn't run on start up. Then after the machine was
> started up, I changed it back and ran it and it died immediately with the
> same error.
>
> I have uninstalled the client through admin\unc32 and removed all traces
of
> the client then reinstalling, but no luck.
>
>
> <[email protected]> wrote in message
> news:1XuQc.3739$8%[email protected]...
> > Did you ever get this solved?
> > I've got the same thing going on with one Win2000 machine in my
> > department. He can log into the network just fine but can not get to the
> > internet.
> > I've tried re-installing the protocol stack; no luck. I've searched hi
and
> > low for any other agent running on the machine with no luck. I've
searched
> > the registry for hours for all keys that would start programs or agents
at
> > start. Can't find anything. I've check for services, checked for fire
wall
> > problems, viruses. No luck. Since its only one machine I can re-image it
> > with no problem, but I'm curious and want to find out whats going on in
> > case the problem reapears or grows to other machines.
> > Any help out there???
> >
> > > Out of the blue a small number of my Windows XP PCs get the following
> > error
> > > when logging in. Usually appears while login script page is on
screen:-
> > >
> > > Failed to initialize the network. Check if another instance of agent
is
> > > running. Contact the system administrator
> > >
> > > Once XP has loaded ok I can manually start the Remote Management
> service.
> > > Some PCs are intermittent and don't seem to get it again but a couple
> > get it
> > > every login. I removed the client and reinstalled. I removed the
Remote
> > > Management service and re-installed. Re-registered the PC Workstation
> > but no
> > > change for those who get it every day.
> > >
> > > I did find this:-
> > >
> > > Failed to initialize the network. Check if another instance of agent
is
> > > running. Contact the system administrator
> > >
> > > Source: Remote Management Agent
> > >
> > > Severity: Critical
> > >
> > > Possible Cause: The Remote Management Agent is unable to bind to the
IPX
> > or
> > > IP port that is being used for Remote Management service, or the ports
> > are
> > > being used by some other application running on the managed
workstation.
> > >
> > > Action: Uninstall any third-party remote control agent or remote
control
> > > application using these ports from the managed workstation.
> > >
> > > Possible Cause: The protocol stack is corrupted.
> > >
> > > Action: Reinstall the protocol stack.
> > >
> > > Possible Cause: The managed workstation is not connected to the
network,
> > or
> > > the network is down.
> > >
> > > Action: Connect the managed workstation to the network.
> > >
> > > I don't have any third party remote control agent installed and I've
> > tried
> > > the refresh of the IP protocol stack. Surprised this has started as we
> > have
> > > not made any changes to the network or software. We run NW Client
> 4.83sp1
> > > and NW5.1 sp5.
> > >
> > > Anybody else had this and cleared it completely?
> > >
> > >
> > >
> > >
> > >
> >
>
>