I fixed the problem, I disabled the second nic card in my machine and am
only using one now =D
-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTMAIL.TEMPLE DOT EDU]
On Behalf Of Wayne A. Fischer
Sent: Tuesday, November 18, 2003 8:27 AM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] RPC Error: Unable to send
Thanks for the tip Pat and Conrad,
I've also tried your recommendations, I put my backup server's info
into my clients %winnt%\system32\drivers\etc\host file and restarted
the client server and tried to backup again but it still fails.
The same errors occur as previously stated. Perhaps it's a reverse
lookup thing. I believe at one point or another I read of a method to
start networker from the command line and if the method worked it
indicated a DNS issue. Anyone know this command line?
-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTMAIL.TEMPLE DOT EDU]
On Behalf Of Pat OBrien
Sent: Tuesday, November 18, 2003 5:54 AM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] RPC Error: Unable to send
right wong or indifferent, I see this problem only on windows clients,
and fix most of these issues by putting the ip address of the server in
the client local host file. I have contemplated replacing the server
name in the local client nsr/server file with ip addr, but once working
solution works, on to next issue. I do not know why we have had recent
rashes of this on all windows clients, but suffice to say the minions
have been at work implementing ad, ms dns, etc.
-----Original Message-----
From: Wayne A. Fischer [mailto:wafischer AT ECON.UCDAVIS DOT EDU]
Sent: Monday, November 17, 2003 4:46 PM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: [Networker] RPC Error: Unable to send
I'm having difficulty backing up a client to my Networker server.
[CLIENT]
The client is a Dell PowerEdge running Windows Server 2003.
I have Legato Networker User version 7.0 Build 322 installed.
The client runs SQL Server 2000, fully patched and I am running
Legato SQL module version 3.22 installed on this client.
[SERVER]
The server is a Dell PowerEdge running Windows Server 2003.
I have Legato Networker Administrator version 7.0 Build 322 installed on
this machine.
I've had problems with the client in the past (incorrectly configured
DNS).
The Client has 2 NIC's in it, 10.0.0.11 and 10.0.0.12. I only use
10.0.0.12 to backup and in DNS I have all host names and aliases
pointing to 10.0.0.12 except one host name which
points to 10.0.0.11. I've already done the following:
Things I've Tried:
Opening networker user on Client cannot find a server
RPCINFO -P from Networker Server to Client and Client to Networker
Server works fine.
Pinging Shortname, Longname and a reverse on IP address from Server to
Client works fine
Pinging Shortname, Longname and a reverse on IP address from Client to
Server works fine
Checking for all Aliases for 10.0.0.12 in DNS, all aliases for 10.0.0.12
are under the client object in Networker Administrator.
Restarted Networker Services on Server and Client.
The actual Error messages are reported below:
Unsuccessful savesets
*yn.econ.ucdavis.edu:All 1 retry attempted
*yn.econ.ucdavis.edu:All nsrexec: authtype nsrexec
*yn.econ.ucdavis.edu:All savefs: RPC error: Unable to send
*yn.econ.ucdavis.edu:All savefs: cannot retrieve client resources
savefs yn.econ.ucdavis.edu: failed
In addition the SQL Server group also failed and I received the
following errors
Unsuccessful savesets
*yn.econ.ucdavis.edu:MSSQL: 1 retry attempted
*yn.econ.ucdavis.edu:MSSQL: Database MYDB backup level forced to full
*yn.econ.ucdavis.edu:MSSQL: Database MYDB1 backup level forced to full
*yn.econ.ucdavis.edu:MSSQL: Only full backup is supported on master
database
*yn.econ.ucdavis.edu:MSSQL: Database MYDB2 backup level forced to full
*yn.econ.ucdavis.edu:MSSQL: Database MYDB3 backup level forced to full
*yn.econ.ucdavis.edu:MSSQL: Database MYDB4 backup level forced to full
*yn.econ.ucdavis.edu:MSSQL: Database MYDB5 backup level forced to full
*yn.econ.ucdavis.edu:MSSQL:nsrsqlsv: Invalid group name SQL Server Group
Any ideas out there in Networker land?
W. Fischer
--
Note: To sign off this list, send a "signoff networker" command via
email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
--
Note: To sign off this list, send a "signoff networker" command via
email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
--
Note: To sign off this list, send a "signoff networker" command via
email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
