multiple nics prevent SUA RCP command from working

[troya@hp.com]

Hi Rodney,

"bisnet" is a DNS alias for the "unix1" server, so those should be returning the same IP address (10.2.11.113). We have tried doing an RCP from the wintel box to all 3 (bisnet, unix1, 10.2.11.113) and got the same error on all 3.

Thanks,
Troy

[rodney]

Okay, I got confused with the names.

From the bisnet/unix1/10.2.11.113 machine if you do the nslookup of the the wintel box by name
and then by the IP number returned by the first lookup what are the records returned.

The error message is being generated by the machine running the daemon (rshd) which is on the unix1 box.
The unix1 rshd is giving the error because the forward (name) and reverse (IP) records of the connecting
machine (wintel) don't match. That's why you want to see what the records are from unix1's view.

[troya@hp.com]

Here you go...

intrface@unix1:/home/unix1/intrface#nslookup sql06
Server: 10.2.10.90
Address: 10.2.10.90#53

Name: sql06.kc.bv.com
Address: 10.2.10.127


intrface@unix1:/home/unix1/intrface#ping sql06
PING sql06.kc.bv.com: (10.2.10.127): 56 data bytes
64 bytes from 10.2.10.127: icmp_seq=0 ttl=128 time=1 ms
64 bytes from 10.2.10.127: icmp_seq=1 ttl=128 time=0 ms
^C
----sql06.kc.bv.com PING Statistics----
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 0/0/1 ms


intrface@unix1:/home/unix1/intrface#nslookup 10.2.10.127
Server: 10.2.10.90
Address: 10.2.10.90#53

127.10.2.10.in-addr.arpa name = sql06.kc.bv.com.

intrface@unix1:/home/unix1/intrface#

[rodney]

The wintel machine, with the 3 NIC's, is named "sql06".
The forward and reverse RR's look like they match for the at least the one NIC.

The other 2 NIC's have different IP addresses.
What do the DNS records look like for those ones by IP and then by whatever name appear with those?
(Narrowing down where the issue is.)

[troya@hp.com]

Hi Rodney,

The other 2 NICs on the wintel box do not have DNS entries. The nic on the "sql06" wintel server that does have a DNS alias is "sql-prod-crm":

===========

ping sql-prod-crm

Pinging sql06.kc.bv.com [10.2.10.127] with 32 bytes of data:

Reply from 10.2.10.127: bytes=32 time=74ms TTL=120
Reply from 10.2.10.127: bytes=32 time=135ms TTL=120
Reply from 10.2.10.127: bytes=32 time=78ms TTL=120
Reply from 10.2.10.127: bytes=32 time=83ms TTL=120

Ping statistics for 10.2.10.127:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 74ms, Maximum = 135ms, Average = 92ms

====================

nslookup sql-prod-crm
Server: kaci-pwpdcna-01.na.bvcorp.net
Address: 10.182.14.20

Name: sql06.kc.bv.com
Address: 10.2.10.127
Aliases: sql-prod-crm.kc.bv.com



nslookup 10.2.10.127
Server: kaci-pwpdcna-01.na.bvcorp.net
Address: 10.182.14.20

Name: sql06.na.bvcorp.net
Address: 10.2.10.127


========================

[rodney]

> The other 2 NICs on the wintel box do not have DNS entries.

That'll be the reason for failure then.
The rshd (daemon) tries to get a DNS RR based on the IP connecting.
If DNS responds with "can't find" that IP then in the rsh protocol that counts as a DNS spoof.

You can read all of the steps rshd goes through on the rshd man page.
If the unix1 box doesn't have it on its man page then the Interix version does.
It's there in 8 step explanation. It's the first part of step 4 that fails.

The most straight-forward thing to do is add a DNS entry for each NIC with it's own unique IP and
a unique name as well. Then the forward and reverse RR's will match.

[troya@hp.com]

Thanks for this information Rodney! We are investigating this on our end. I'll update to let you know what we find.

Thanks,
Troy

[troya@hp.com]

Hi Rodney,

I wanted to follow up with you on this, to close the loop -- We got it to work!!!

The solution was to add the FQDN to the ip address in the unix .rhost file. That allowed the RCP to work correctly.

So it now resembles:

10.2.10.127.kc.bv.com cmssrv

whereas before it showed:

10.2.10.127 cmssrv

Adding the fqdn (kc.bv.com) made all the difference! This works regardless of how many NICs are enabled on the wintel sql server box, too!

Thanks so much for your help with this! I really appreciate the time and effort you invested to help us solve our problem!

Troy