Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Server timing out Connecting to Client

Status
Not open for further replies.

bobbtran

MIS
Sep 17, 2002
1
US
I am running Networker 5.5.2. My Servers and Clients have been running fine until I installed a new GNAT "NAT" Software firewall. Now my Server (automated backup) no longer sees my Client. When I setup my firewall I used the original alias names for the external names (using NAT Alias) forwarding that alias through the firewall to a new internal IP and IP Alias. Funny thing is, I can manually backup my Client from the Client machine to the Server just fine.

Original Server and Client info:

Server Name=Bob
Server/Alias=bob.domain.com
Client Name=Steve
Client/Alias=steve.domain.com

When I setup my new firewall my Server and Client Windows name did not change but my "Internal" Clients IP Alias changed.

Internal Server and Client info:

Server Name=Bob
Server/Alias=bob.domain.com
Client Name=Steve
Client/Alias=steve2.domain.com

External (NAT) Server and Client info:

Server Name=Bob
Server/Alias=bob.domain.com
Client Name=Steve
Client/Alias=steve.domain.com

I know Legato does not support NAT firewalls (and I do not want to use static IP’s at this point) so I was hoping to try and get the Server to see the Client using the Internal alias only. I have tried adding the new alias in the Client properties “aliases” area on the Networker Server but it still times out. I am sure the Server is still looking for the external alias.

Has anyone run across this before or have any suggestions?

Bobb
 
Networker checks IPs and Names while working. If you initiate a backup ob Steve it connects to the internally known IP.

When the answers from the client come back to the server they are changed by the NAT Server, so the Networker Server does not know that they are from the client. It waits for a response and does not get one, so the timeout occurs.

We had some similar problems with multiple Interfaces on a machine, when the client responded with a different IP than it was connected.

My suggestion would be to add the name of the NAT server to the aliases in Networker. Maybe that could fix the problem.

Johanes
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top