connection refused and no such file or directory

[jbarbone]

Hello,

I am running Networker v6.2 on a Windows 2000 server and Novell and Windows clients. However, on two or three clients, I am receiving "connection refused" errors. I have verified the NIC settings (100/FULL), I have verified DNS and reverse DNS, I have verified Aliases, I have restarted the Networker Service, I have verified Domain rights to the particular server, I have also verified the servers file in NSR\RES and I STILL receive "connection refused" errors. Sigh. Can someone please advise?

I also have another problem with a NT 4.0 Server reporting "No such file or directory" when I try to back up the SYSTEM STATE:\ saveset.

Any help would certainly be appreciated. Thanks in advance!

Joe Barbone

 

[wallace88]

In the second question: the saveset should be:

SYSTEM STATE:

For the first question: does manual backups work? Go to the clients that can;t backup and run:

save -vvv -s (server) -b (pool) (file)

If that works, then on the server run:

savegrp -pvvv -c (client) -l full (group name)

Check output.

Are there multiple NIC cards? Are you specifying a Server Network Interface in the client configuration?

 

[jbarbone]

I tried SYSTEM STATE: and it still does not work.

There is only one NIC configured, but I will try the manual backups and let you know the results.

Thank you for your input.

Joe

 

[wallace88]

Regarding the system state: ... what o/s and version is on that client? What version is NetWorker?

If it is you're running NetWorker 5.7 or later, then system state: should work.

 

[605]

SYSTEM STATE refers to Windows 2000 not to Winodws NT. Use
REGISTRY instead.

 

[wallace88]

605: SYSTEM STATE: is used when you have NetWorker 5.7 running on Windows NT.

Prior to 5.7 you would use REGISTRY.

Check your NetWorker admin guide.

 

[wallace88]

jbarbone: regarding the system state issue, is there a reason why you aren't using saveset=all?

Just for a test, change the client saveset to All, then run the following:

savegrp -pvvv -c (client) -l full (group name)

If there is no connection problems, then it should report all the savesets that can be backed up for that client.

 

[jbarbone]

I am running Networker v6.2 and it works on other NT 4.0 Server OSs with SYSTEM STATE: So I am not sure why this one particular client doesnt work. However, I would rather resolve the Connection Refused issue. I can always change the saveset to ALL like mentioned above to resolve the SYSTEM STATE: issue.

 

[wallace88]

have you tried the save and savegrp tests that I suggested then?

 

[jbarbone]

Not yet, I am going to try those as soon as the backups are completed for today. Then I will have time to play with it. I will update you as soon as I try it.

Thanks again.

Joe

 

[jbarbone]

Well, I ran a manual backup from the client and it worked fine. I deleted the client in NetWorker and recreated it and it still says Connection Refused even though I can do a manual backup through the NetWorker User software on the client itself. ?

I have proceeded to tighten the rope around my neck. Now if I could just get that chair a bit closer...

 

[wallace88]

What is the savegrp -vvv output?

 

[michaelw70]

I am having the same issue. Usually a HOSTS file issue or services not started issue. Not this time, HOSTS file is fine and services are running.

I am looking forward to someone giving you a helpful answer also.

Maybe together we can get the chair closer! HA

 

[jbarbone]

What specifically am I looking for in the -vvv output? It has been running for quite a bit now (7-9 minutes) and is still running. Should it take this long?

I agree Michaelw70, I too checked the HOSTS file as well as the service. Everything seems normal regarding those two areas, however, connection is still being refused.

Ok, you get the left side of the chair, I'll grab the right side and we'll slide it under the dangling rope...

 

[wallace88]

so the savegrp is running... in nwadmin, is there there actually data being written to tape?

If this is the situation, then I don't understand where you are getting he connection refused error.

In the output you are seeing, has it completed the probe, and is actually running the save command?

 

[DavinaTreiber]

It's not SYSTEM STATE: it's SYSTEM STATE:\ as first stated. To prove this, run a client with save set of All and see what it comes back with.

 

[oliverk75]

Wallace,

To solve the connection refused:

edit the file c:WINNT\system32\drivers\etc\host, add your Networker server IP Address and name.

That's should solve your pb

 

[wallace88]

Thank's oliverk75, but I wasn't the one having the problem.

Just populating the host tables is not always a solution.