Hi all,

I'm having an issue where my Jumpstart boot prompts for a name service 
even though it is configured already.

Before prompting I see this in snoop:

172.30.172.209 -> (broadcast)  ARP C Who is 172.30.172.209, 172.30.172.209 ?
172.30.172.209 -> (broadcast)  ARP C Who is 172.30.172.209, 172.30.172.209 ?
172.30.172.209 -> (broadcast)  ARP C Who is 172.30.172.209, 172.30.172.209 ?
172.30.172.209 -> 172.30.172.255 NIS+ C FindDir "Engineering.NIS"
172.30.172.209 -> 172.30.172.255 NIS+ C FindDir "Engineering.NIS" 
(retransmit)
172.30.172.209 -> 172.30.172.255 NIS C DOMAIN_NONACK Engineering.NIS
172.30.172.209 -> 172.30.172.255 NIS C DOMAIN_NONACK Engineering.NIS
   KeyMaster -> 172.30.172.209 NIS R DOMAIN_NONACK OK
   KeyMaster -> 172.30.172.209 NIS R DOMAIN_NONACK OK
172.30.172.209 -> (broadcast)  ARP C Who is 172.30.172.122, KeyMaster ?
   KeyMaster -> 172.30.172.209 ARP R 172.30.172.122, KeyMaster is 
0:14:5e:2b:a5:75
172.30.172.209 -> KeyMaster    NIS C DOMAIN Engineering.NIS
   KeyMaster -> 172.30.172.209 NIS R DOMAIN OK
172.30.172.209 -> KeyMaster    NIS C MATCH 1023/udp in services.byname
   KeyMaster -> 172.30.172.209 NIS R MATCH No such key
172.30.172.209 -> KeyMaster    NIS C MATCH 172.30.172.122 in ipnodes.byaddr
   KeyMaster -> 172.30.172.209 NIS R MATCH No such key
172.30.172.209 -> KeyMaster    NIS C MATCH 172.30.172.122 in hosts.byaddr
   KeyMaster -> 172.30.172.209 NIS R MATCH OK
172.30.172.209 -> 172.30.172.255 NIS C DOMAIN_NONACK Engineering.NIS
   KeyMaster -> 172.30.172.209 NIS R DOMAIN_NONACK OK

Which, to my (only partially educated) eyes, appears to be working?

Then it asks me if I want to enter new info.
If I elect to enter new info, and choose NIS, and 'Find One', I see this 
in snoop:

172.30.172.209 -> 172.30.172.255 NIS C DOMAIN_NONACK Engineering.NIS
   KeyMaster -> 172.30.172.209 NIS R DOMAIN_NONACK OK

And it reports that it failed - even though again it looks successful.

Again it asks me if I want to enter new info.
If I elect to enter new info, and choose NIS, and 'Specify One', It has 
the NIS Domain, Server Name, and Server IP all set correctly again. When 
I accept that info, and proceed, snoop shows:

172.30.172.209 -> KeyMaster    RPCBIND C GETADDR prog=100004 (NIS) vers=2
   KeyMaster -> 172.30.172.209 RPCBIND R GETADDR  Uaddr=172.30.172.122.3.255
172.30.172.209 -> KeyMaster    NIS C DOMAIN Engineering.NIS
   KeyMaster -> 172.30.172.209 NIS R DOMAIN OK

Which is different than before, but still appears to be working.

Again it asks me if I want to put in new info, and if I say 'no' it 
proceeds and snoop shows this:

172.30.172.209 -> KeyMaster    NIS C DOMAIN Engineering.NIS
   KeyMaster -> 172.30.172.209 NIS R DOMAIN OK
172.30.172.209 -> KeyMaster    NIS C MATCH Engineering.NIS in 
timezone.byname
   KeyMaster -> 172.30.172.209 NIS R MATCH OK
172.30.172.209 -> KeyMaster    NIS C MATCH timehost in ipnodes.byname
   KeyMaster -> 172.30.172.209 NIS R MATCH No such key
172.30.172.209 -> KeyMaster    NIS C MATCH timehost in hosts.byname
   KeyMaster -> 172.30.172.209 NIS R MATCH OK

Which still makes me think it worked.

Also For some reason, even though it was able to look up 'timehost' in 
hosts.byname,
and contact it:

172.30.172.209 -> KeyMaster    TIME C port=34295
   KeyMaster -> 172.30.172.209 TIME R port=34295
172.30.172.209 -> KeyMaster    TCP D=2049 S=1022 Fin Ack=3464764269 
Seq=47562437 Len=0 Win=49640
   KeyMaster -> 172.30.172.209 TCP D=1022 S=2049 Ack=47562438 
Seq=3464764269 Len=0 Win=49640
   KeyMaster -> 172.30.172.209 TCP D=1022 S=2049 Fin Ack=47562438 
Seq=3464764269 Len=0 Win=49640
172.30.172.209 -> KeyMaster    TCP D=2049 S=1022 Ack=3464764270 
Seq=47562438 Len=0 Win=49640

It is also still prompting me to set the time and date?

What's going wrong here?

Other info:

BootServer is running sNV b74. It is the NIS Master, and DHCP server.
Client is attempting to PXE boot and install sNV b76.

If there's anything else anyone needs to know to help with this, please ask.

Thanks for all your help!

   -Kyle







_______________________________________________
opensolaris-discuss mailing list
[email protected]

Reply via email to