This is a multipart message in MIME format.
--=_alternative 007AE9AE85256DAC_=
Content-Type: text/plain; charset="us-ascii"
This can be tricky. If your client keeps the same IP DNS name and changes
IP addresses, it could be a reverse lookup issue Are you using DHCP to
get the IP address?
Try checking if the reverse lookup gives the right address. I think
NetBackup does a reverse
lookup on the IP address to get the name so it can match the client. Check
your hosts file
on the Solaris system for that system.
Hope this helps
Regards,
Carl
=============================
Carl Stehman
PHI Services Company
202-331-6619
Pager 301-765-2703
ckstehman AT pepco DOT com
Wayne T Smith <WTSmith AT maine DOT edu>
Sent by: veritas-bu-admin AT mailman.eng.auburn DOT edu
09/25/2003 01:50 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
cc:
Subject: [Veritas-bu] Client multiple IP addresses?
My (Solaris V4.5MP5) Netbackup has trouble with a client (Win2000) that
has 1 IP name (xxx.maine.edu) and 2 IP addresses (130.111.xxx.yyy and
130.111.aaa.bbb). This client doesn't have dual network attachments,
but moves between areas using one of the IP addresses, then the other.
Netbackup times out.
The (Solaris, I guess) PING command results differ depending on the case
of the IP name entered! (PING from other systems doesn't).
If Netbackup chooses the IP address where the client machine resides,
things should work (but haven't). If Netbackup chooses the "wrong" IP
address, it must timeout ... but since things (such as client properties
on the client from the backup server GUI) stop there, I guess Netbackup
fails for this client setup. :-( Anyone know of an approach to this
problem?
(The problem comes from the client having a permanent IP address at its
home base, but getting assigned another as it roams about the campus).
Thanks in advance for any suggestions, wayne
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
--=_alternative 007AE9AE85256DAC_=
Content-Type: text/html; charset="us-ascii"
<br><font size=2 face="sans-serif">This can be tricky. If your client
keeps the same IP DNS name and changes</font>
<br><font size=2 face="sans-serif">IP addresses, it could be a reverse lookup
issue Are you using DHCP to get the IP address?</font>
<br><font size=2 face="sans-serif">Try checking if the reverse lookup gives the
right address. I think NetBackup does a reverse</font>
<br><font size=2 face="sans-serif">lookup on the IP address to get the name so
it can match the client. Check your hosts file</font>
<br><font size=2 face="sans-serif">on the Solaris system for that system.
</font>
<br>
<br><font size=2 face="sans-serif">Hope this helps</font>
<br>
<br><font size=2 face="sans-serif">Regards,</font>
<br>
<br><font size=2 face="sans-serif">Carl</font>
<br><font size=2 face="sans-serif"><br>
=============================<br>
Carl Stehman<br>
PHI Services Company<br>
202-331-6619<br>
Pager 301-765-2703<br>
ckstehman AT pepco DOT com</font>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>Wayne T Smith <WTSmith AT maine DOT
edu></b></font>
<br><font size=1 face="sans-serif">Sent by: veritas-bu-admin AT
mailman.eng.auburn DOT edu</font>
<p><font size=1 face="sans-serif">09/25/2003 01:50 PM</font>
<br>
<td><font size=1 face="Arial"> </font>
<br><font size=1 face="sans-serif"> To:
veritas-bu AT mailman.eng.auburn DOT edu</font>
<br><font size=1 face="sans-serif"> cc:
</font>
<br><font size=1 face="sans-serif"> Subject:
[Veritas-bu] Client multiple IP addresses?</font></table>
<br>
<br>
<br><font size=2 face="Courier New">My (Solaris V4.5MP5) Netbackup has trouble
with a client (Win2000) that <br>
has 1 IP name (xxx.maine.edu) and 2 IP addresses (130.111.xxx.yyy and <br>
130.111.aaa.bbb). This client doesn't have dual network attachments, <br>
but moves between areas using one of the IP addresses, then the other.<br>
<br>
Netbackup times out.<br>
<br>
The (Solaris, I guess) PING command results differ depending on the case <br>
of the IP name entered! (PING from other systems doesn't).<br>
<br>
If Netbackup chooses the IP address where the client machine resides, <br>
things should work (but haven't). If Netbackup chooses the
"wrong" IP <br>
address, it must timeout ... but since things (such as client properties <br>
on the client from the backup server GUI) stop there, I guess Netbackup <br>
fails for this client setup. :-( Anyone know of an approach to this <br>
problem?<br>
<br>
(The problem comes from the client having a permanent IP address at its <br>
home base, but getting assigned another as it roams about the campus).<br>
<br>
Thanks in advance for any suggestions, wayne<br>
<br>
_______________________________________________<br>
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu<br>
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu<br>
</font>
<br>
<br>
<br>
--=_alternative 007AE9AE85256DAC_=--
|
