Solaris DHCP Windows RIS


T

theboards

We have the following setup;

Server A - Solaris DCHP Server configured to supply IP address only (we
do not use DHCP options 60, 66 (TFTPSrvn) or 67 (OptBootF) as per this
article; http://support.microsoft.com/?kbid=259670).
Server B - Windows RIS Server.
Client A - Windows Desktop not on the same subnet as the DHCP or RIS
servers.
All appropriate routers are configured with IP helper addresses for
both the DHCP and RIS
servers.

As far as I am aware the DHCP and RIS Boot process goes like this;

Client A sends DHCP DISCOVER (asking for IP address and PXE boot
server)
Server A (DHCP Server) sends DHCP OFFER (offers IP address)
Server B (RIS Server) sends DHCP OFFER (offers PXE boot server)
Client A sends DHCP REQUEST to Server A (DHCP server) (requesting IP
address)
Server A (DHCP Server) sends DHCP ACK to Client A (offering an IP
address)

Client A now has IP address.

Client A sends DHCP DISCOVER (client now has an IP address, but is
still looking for a PXE boot server)
Server A (DHCP server) sends DHCP OFFER (will re-offer the same IP
address)
Server B (RIS server) sends DHCP OFFER (will offer a boot server)
Client A sends DHCP REQUEST to RIS server (requesting the boot server)
Server B (RIS server) sends DHCP ACK to client A (this ACK contains the
address of the RIS server, then the name of the RIS server, and the
first file the client should send a TFTP request for to start the boot
process ie startrom.com)

(From; http://support.microsoft.com/kb/244036/)

A snoop on the Solaris box shows the following during a RIS boot from
Client A

Server A # snoop -i /tmp/banjo | grep -i dhcp
75 0.16940 switch1.company.co.uk -> storm DHCP/BOOTP
DHCPDISCOVER
85 0.08926 serverA -> 192.168.101.254 DHCP/BOOTP DHCPOFFER
97 0.07923 switch1.company.co.uk -> storm DHCP/BOOTP
DHCPREQUEST
99 0.01384 serverA -> 192.168.101.254 DHCP/BOOTP DHCPACK

It is clear from the messages on Client A that the DHCP server has
supplied the IP address so we know that the first part of the process
is complete.

What we do not see is the 2nd DCHP DISCOVER that I would have expected
to see as Client A tries to discover RIS info.

The error we get is TFTP Access Violation;

PXE-E3C: TFTP error - Access violation.

The request file was found on the TFTP server. The TFTP service does
not have enough access rights to open/read the file.

(From; http://www.emboot.com/faq-pxe.shtml)

I am a bit lost what are we doing wrong?
Why does Client A not try to obtain RIS info???
 
Ad

Advertisements


Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

RIS and DHCP 1
RIS & DHCP 1
RIS / DHCP on WAN 4
RIS - DHCP & Resolve 4
RIS, DHCP and VLANS 0
RIS and Cisco for DHCP 0
RIS DHCP Router 2
RIS with non-MS DHCP 1

Top