Having issues adding windows 2003 client to legato server

[luctran]

Hello everyone,

Just wondering if anyone has ever cross this issue.

I'm trying to add 3 windows 2003 servers to our pool, but it looks like the clients are having problems contacting the server.

It was able to connect to the server about a month ago, and suddenly my backup server logs are showing rpc errors to that server.

so i tried running networker user on the client and see if it even connects, it tries to connect, but gives an error: "unable to connect to backupserver.x.x.x."

So I've tried adding the -s backupserver.x.x.x. to the shortcut icon. no go

I tried adding the FQDN in the host file. no go

able to ping server fine, able to go to server share fine.

ironically all 3 of these servers are having the same issues.

info: native mode in AD, 2k3 servers, - other servers are able to connect fine.

any info would help

TIA!

luc

 

[605]

Two ad-hoc issues come into my mind:
- make sure that manual backups from the clients are working.
- make sure that the listener (nsrexecd) is started on the clients.

 

[luctran]

thanks for the reply...

manual backups are not working. The client won't connect to server for me to do any manual backups. "cannot connect to backupserver.x.x" "do you wish to try another server" Yes

"You are not a client of any server"

I have created a node with the same name of the server (with the appropriate aliases).

The servcies seems to be running and listening...
servers are pingable

tried running rpcinfo..


C:\>rpcinfo -p servername

program vers proto port
100000 2 tcp 7938
100000 2 udp 7938
390113 1 tcp 7937
program vers proto port
100000 2 tcp 7938
100000 2 udp 7938
390113 1 tcp 7937

i'm not sure what i'm suppose to look at but i read somewhere that porst 7938 and 7937 were what the nsrexecd

wierd huh?

thanks in advance for help.

luc

 

[605]

This points to a name resolution problem. Try to recreate the client.

If the \nsr\index\client_name directory prevents this, simply move it to another diretory for the moment.

 

[luctran]

thanks again for advice,
it still doesn't resolve it

"unable to connect server" (while trying to run network user...

If i try the networker administrator and connect to server it gives an error
"server backupserver: unable to receive"

luc

 

[605]

If the client-initiated backup fails already, don't expect an automatic one to run.

If the name resolution is ok, is there a firewall involved?

 

[luctran]

I checked but firewall is off. (no sp1 installed yet either).

 

[luctran]

I tried a different 2003 server just now and it connects to the backup server fine. so at least i know for sure something is wrong with that particular client.

 

[605]

I still go for a name resolution problem.

 

[kskutt]

I am having the same issue. One 2003 server won't conect with this odd error while others have no problem. In fact this server is a ghost clone of the others with a different name, ip and sid. everything resolves properly and this server just refuses to connect to the tape server which is running on windows server 2003 also.