I also receive the following error : com.avamar.asn.NetworkException: Unable to connect to a login server when trying to log on to the Avamar Administrator (v5.0) via VPN tunnel. This is a single node v5 system. Has anyone received a resolution to this issue?
Avamar 5.0 relies heavily on DNS and therefore special care should go into setting up DNS properly.
If you are using windows AD for DNS, then make sure that DNS records are setup in the same domain as the domain that Avamar was setup in. If they are and still having this issue, remove duplicate avamar records from subdomains. This should resolve your issue.
If the DNS server is unix/linux based case sensitivity is usually the culperate.
ttavares wrote: "I also receive the following error : com.avamar.asn.NetworkException: Unable to connect to a login server when trying to log on to the Avamar Administrator (v5.0) via VPN tunnel. This is a single node v5 system. Has anyone received a resolution to this issue? "
if your Avamar version is 5.0 SP1 or earlier, and you are trying to launch the Avamar Administrator for an Avamar server with NAT IP, you may have encountered a bug. ( 18726 )
I had that issue, and with a hotfix from Avamar website, it is solved. the detail
yes hotfix works OK for v5sp1, it just no longer available for download from avamar ftp site from today.
just a bit off topic, regarding DNS:
1) indeed DNS can be sometimes an extra layer of problem... In my previous backup deployment, including Avamar, always try avoid using DNS or other name services, instead just use plain hosts file.
2) plain hosts file are ok for most Server backup environments.
3) and with Avamar now supporting DTLT, it is almost impossible to avoid DNS for DTLT clients, that could be the the risk of a lot trouble because DNS is not normally managed by backup team, it is a potential risk if someone causually change DNS entries
Goran1
13 Posts
1325
0
Posted February 3rd, 2009 14:00