Alexandre,
 
Networker could be hinting at a DNS problem, or another problem regarding your 
network. An easy workaround is to use host files. I believe Networker looks to 
the host files before it tries to do a DNS lookup.
 
 
David M. Cohen
Technical Consultant
Cambridge Computer Services, Inc.

        -----Original Message----- 
        From: Alexandre Déry/dgt/sct [mailto:Alexandre.Dery AT SCT.GOUV.QC DOT 
CA] 
        Sent: Wed 7/14/2004 3:03 PM 
        To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU 
        Cc: 
        Subject: [Networker] Multiple virtual IPs slowing down Networker client 
on winnt ?
        
        

        Hi,
        
        I've just added 8 new winnt boxes to my backup server (migrated off an 
old
        Backup Exec platform to my centralized Networker server).
        
        7 of the 8 boxes backed up just fine, but one of them (the most 
important)
        has issues... The most important being that the backup is very slow to
        start. Normally, when I start a group, it takes about a minute before 
some
        data starts to backup... but in this server's case, it took almost 15
        minutes before the backup started...
        
        One thing I noticed in the clients daemon.log are these messages :
        
        07/14/04 14:10:28 nsrexecd: Diagnostic: Reverse DNS lookup failed for 
host
        null, address 172.19.2.61
        07/14/04 14:10:32 nsrexecd: Diagnostic: Reverse DNS lookup failed for 
host
        null, address 172.19.2.62
        07/14/04 14:10:37 nsrexecd: Diagnostic: Reverse DNS lookup failed for 
host
        null, address 172.19.2.63
        07/14/04 14:10:41 nsrexecd: Diagnostic: Reverse DNS lookup failed for 
host
        null, address 172.19.2.64
        [...]
        07/14/04 14:12:56 nsrexecd: Diagnostic: Reverse DNS lookup failed for 
host
        null, address 172.19.2.95
        
        It seems that the client tries to do reverse lookup of all my virtual
        IPs... of course it won't find anything because these private IPs are 
not
        in DNS.
        
        I also see the the server does some requests on port 514 (blocked at
        firewall) which is the old port that networker was using before they 
went
        to 793x I think...
        
        Why does the client looks up all these IPs ? Is it necessary ? Could I
        disable it ?
        
        Why would my server try to connect to the client on port 514 ? Is it
        related ?
        
        Here are the specs :
        
        Server : Windows Server 2003 + Networker server 7.1 with 3 nics
        Client : Windows NT4 Server + 2 teamed nics (compaq) with 1 "main ip" 
and
        ~40 virtual IPs Networker client 7.1
        The firewall is a Checkpoint Firewall NG
        
        Thanks !
        
        
        
        Alexandre Déry
        Technicien, SCSA, CCNA
        Direction générale des technologies de l'information et des 
communications
        1500E, rue Jean-Talon Nord 1er étage
        Sainte-Foy (Québec) G1N 4T6
        Téléphone: (418) 646-9273
        Télécopieur: (418) 528-0418
        
        --
        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.
        =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=