At 03:53 PM 1/22/99 -0500, Ross, Mitch wrote:
>The server doesn't keep a record of the client's IP addresses- only the node
>name.  (This is handy for desktops using DHCP, among other things.)  The
>only way the ADSM server knows how to contact a client is to reply back to
>it.  That's why the scheduler service contacts the server upon startup.
>
>It's important to remember that different network cards use different IP
>ranges.  In our case the backup network is 10.0.0.x and the production
>network is 38.x.x.x.  The ADSM server has *two* IP addresses- one for each
>card.  If a client contacts the server over the backup network, it's using
>10.0.0.x addresses for the server and itself.  Default route settings
>shouldn't play into this at all.

Sounds like you have two separate networks that do not have connectivity to
each other.  I didn't catch that.  You must also have explicit routes in
place on the server to route 10.x addresses to one interface and 38.x
addresses to the other.  This is the way IP works.

>>Can you expand on the recommendation to not use name resolution?  I don't
>>see what the problem would be, and not using it can introduce other
>>headaches in managing your systems.
>
>Name resolution is the process of resolving a name (say, SERVER1), to an IP
>address (say, 10.0.0.1).  When you have a machine with two network cards, it
>therefore has two IP addresses. (say, 10.0.0.1 and 38.1.1.1)  With NT it's
>not real clear which IP address you should get when you say "SERVER1".
>
>A good example of this is to type "PING SERVER1".  What IP address will it
>use? Well, it depends...

Not at all.  It will use whatever IP address SERVER1 translate to in DNS.
SERVER1 is a DNS name if you are using it as an argument to the ping
command.  If you have to IP addresses you should be able to give each one a
unique DNS name.  We do this, albeit not on NT.

>You can get around this by using a LMHOSTS file, but that's a lot of manual
>work.  The idea there is to have two names for the server, each with a
>unique IP address.  Another option is to remove the second address from WINS
>and DNS, so that it always resolves to the first address.  The only time the
>second address is used is if you explicitly use that IP address.
>
>-Mitch

It sounds like WinNT (netbios) concepts are getting muddled together with
TCP/IP concepts.  I've been assuming (above) that you are using TCP/IP for
your network protocol between ADSM server and ADSM clients.  If not, then
ignore the above.  If you are using TCP/IP, then there shouldn't be any
reason to not use DNS names to refer to IP addresses.  It's a simple
mapping of names to numbers.

Regards,
..Paul