Thanks for all the feedback.  What ended up fixing it, was to start the
remote registry service on the target server.

For anyone who cares to know how I discovered this was to use Netmon while I
tried to establish connection to the server with Event Viewer.  2 things
that stuck out were   "NT Create & X, File = \winreg"  and the reply was "NT
error, System, Error, Code = (52) STATUS_OBJECT_NAME_NOT_FOUND"..

I did a search at Microsoft for "create \winreg", and
"STATUS_OBJECT_NAME_NOT_FOUND", which is equivalent to a win32 error of..
Error file not found.. and the "winreg" search brought me to some
information about network access to the registry.. so 1 + 1 = Remote
Registry Service Not Started!

Thanks again for the feedback.  This seems like a great list and I hope I'll
have some useful contributions in the future.
-Lana

----- Original Message -----
From: "Kevin Lundy" <[EMAIL PROTECTED]>
To: "NT System Admin Issues" <[EMAIL PROTECTED]>
Sent: Friday, August 17, 2001 11:24 AM
Subject: RE: Can't Connect to Remote PC with Event Viewer


> Yes, I can connect thru computer management, file shares, IPC$, etc.
> Everything but event viewer, and then I also get the Network path.
>
> -----Original Message-----
> From: L. Lane [mailto:[EMAIL PROTECTED]]
> Sent: Friday, August 17, 2001 12:10 PM
> To: NT System Admin Issues
> Subject: Re: Can't Connect to Remote PC with Event Viewer
>
>
> That's interesting.  So you can connect through computer management as
well?
> Are you getting the exact same message? .. Network path cannot be found?
>
> Thanks,
> -Lana
> ----- Original Message -----
> From: "Kevin Lundy" <[EMAIL PROTECTED]>
> To: "NT System Admin Issues" <[EMAIL PROTECTED]>
> Sent: Friday, August 17, 2001 10:45 AM
> Subject: RE: Can't Connect to Remote PC with Event Viewer
>
>
> > I have no idea, but I can replicate the problem on a small 3 server lab
> > network - a Win2k AD DC and 2 member servers.  Servers can connect to
each
> > other to do ANYTHING except Event Viewer.  Even the domain admin logged
> into
> > the DC can't connect remotely to the 2 member servers for event viewer.
> >
> > -----Original Message-----
> > From: L. Lane [mailto:[EMAIL PROTECTED]]
> > Sent: Friday, August 17, 2001 11:35 AM
> > To: NT System Admin Issues
> > Subject: Can't Connect to Remote PC with Event Viewer
> >
> >
> > Hello All,
> >
> > I am new to this list, and I am hoping someone can help me with a little
> > annoying problem I am having.  I cannot seem to connect from "Server A"
to
> a
> > remote "Server B" with Event Viewer to view the Event log.  Both
machines
> > are Win2K SP2, no AD, it is an NT 4 Domain.  When I type the remote
> computer
> > Name or IP address in the Select Computer Box, I get the following
> message..
> > "Unable to connect to computer "Servername".  The error was: The network
> > Path is not found."
> >
> > Funny thing is, I can connect to this PC in Computer Management, I can
> stop
> > and start services, view the shares, Local Users and Groups, but if I
> click
> > on Event Viewer, I get the same message.  I can ping the IP, the name,
map
> a
> > drive and everything, so the connectivity is definitely there.  Server B
> can
> > view Server A's event log, but ServerA cannot connect to Server B. Also
on
> > Server A I can connect to all the other NT4 machine's event logs, and I
> have
> > also VPN'd to a home machine, and was able to connect to that event log
> > running on Win2K SP2 also.  I have tried this with my account which is a
> > member of Domain Admins, as well as the Domain Admin Account itself with
> > same results.  Is there some "remote access" type service that's needed,
> or
> > policy or something that may have been configured on Server B that
doesn't
> > allow remote access to the event log?  I've searched KB for this error
> also
> > and came up empty.  Server A is my workstation, so I really would like
to
> be
> > able to view all the other server logs from my desk.  Any ideas are
> greatly
> > appreciated.
> >
> > TIA,
> > -Lana
> >
> >
> >
> > http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
> >
> > http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
> >
>
>
> http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
>
> http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
>


http://www.sunbelt-software.com/ntsysadmin_list_charter.htm

Reply via email to