I second this. Also, if anything was added to the network stack, it loads the
drivers from the original NT software so the service pack levels are out of
sync. I'd rebind the protocol stack, reboot, and then re-apply the latest NT
service pack and reboot.
--
Matthew Huff | One Manhattanville Rd
Director of Operations | Purchase, NY 10577
OTA LLC | Phone: 914-460-4039
mailto:mhuff AT ox DOT com | Fax: 914-460-4139
-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
On Behalf Of Skinner,Alan C(Contractor)
Sent: Friday, December 09, 2005 8:06 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] AW: [Networker] Networker Problem: Unable to Receive
from Cli ent side and Unable to send from server side
Every time I have an RPC error on a Windows box it has always come down to the
clients TCP/IP protocol, usually a winsocks error. If I read correctly your
client is a NT box. You will have to go into the TCP/IP configuration and
change something so that when you go to exit it will prompt you to bind the
protocol stack. Say yes and then reboot. No guarantee's just a thought
Alan Skinner
Network Administrator
RAM, Inc.
609-562-6039
alan.skinner AT dix.army DOT mil
alan.skinner AT us.army DOT mil
-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
On Behalf Of YUUNI, OSAY OSMAN
Sent: Friday, December 09, 2005 7:56 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: AW: [Networker] Networker Problem: Unable to Receive from Client
side and Unable to send from server side
Hi,
There are no firewalls involved with this client. Nsradmin -p nsrexecd -s
<clientname> with print, prints out the following information about the
client:
nsradmin> print
type: NSRLA;
name: <clientname>;
version: "Legato NetWorker 7.1.3.Build.404 ";
servers: <servername>;
administrator: "group=Administrators,host=localhost",
"group=Administrators,host=<clientname>",
"isroot,host=<servername>";
arch: Windows 2000;
CPU type: INTEL_PENTIUM;
machine type: server;
OS: Windows 2000 5.0;
NetWorker version: 7.1.3.Build.404;
client OS type: Windows NT Server on Intel;
CPUs: 1;
MB used: 17147;
IP address: 192.168.140.28;
This confirms that the server talks to the client but I don't understand why I
keep getting the rpc error. What is strange is that it had been working for
months and with no changes made to either side it stopped working.
------------------------------------
African Development Bank
YUUNI, Osay Osman
Snr Network Engineer
o.yuuni AT afdb DOT org
oyuuni AT ieee DOT org
13 Avenue du Ghana
BP 323
1002 Tunis Belvedere
Tunisia
tel: (216) 71102581
mobile: (216) 97 47 87 60
------------------------------------
-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
On Behalf Of Grohal, Klaus
Sent: Friday, December 09, 2005 12:19 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] AW: [Networker] Networker Problem: Unable to Receive from
Client side and Unable to send from server side
any firewals involved?
try from the server side: nsradmin -p nsrexecd -s <clientname>. then "print",
you should the the client resource now. If not the nsrexecd on both side can't
talk to each other.
regards
Klaus
-----Ursprüngliche Nachricht-----
Von: Legato NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
Im Auftrag von Osay Osman Yuuni
Gesendet: Freitag, 9. Dezember 2005 11:21
An: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Betreff: [Networker] Networker Problem: Unable to Receive from Client side and
Unable to send from server side
Hi,
I'm having a bizare problem with my set up here. Networker 713 for windows has
been working well but suddenly I'm unable to backup one of the clients.
It always fails with a message of unable to send (RPC). I've tried rpcinfo -p
from both server and client and the necessary ports are listed. I've tried
connecting from the client side and I get an unable to receive error.
I re-installed the client and I still get the same error. Can anyone throw
light on this for me please?
TIA.
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems wit this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or via RSS at
http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems wit this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or via RSS at
http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems wit this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or via RSS at
http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems wit this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or via RSS at
http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu
if you have any problems
wit this list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|
