RIS Server Troubleshooting (PXE-E53)

Hello,
I am new to RIS so hopefully I have set something up wrong and someone
will pick up on it quickly. We currently have two domain controllers in our
child domain, one hosting DHCP and the other hosting RIS. The domain
controllers and the PXE client are on the same switch and subnet. The RIS
server is authorized for DHCP but does not have an ip scope. When I start
the PXE it returns "PXE-E53: No boot filename received". I have captured the
network traffic which shows the PXE client sending a DISCOVERY and the DHCP
DC returning an OFFER, but it just repeats that a couple times, not
progressing any further into the handshake. If I give the RIS DC a dhcp
scope, the PXE client will grab an IP from the RIS DC and proceed with the
PXE boot. Unfortunately we want to keep the DHCP service on a separate
server. Any suggestions are greatly appreciated.

*Note* Both domain controllers have teamed NICs in a fail-over configuration.

Thank You,
Ben Grindy
MIS Dept.
Mercy Hospital and Health Care Center

RIS is great fun when it works, but getting there takes a bit of setting up.
I have DHCP on the same server as RIS adn my DC which means the DHCP server
is automatically authorised.

So my firstl question is the DHCP server is definitely authorised? Secondly
have you tried restarting RIS services, DHCP server and even the box after
auhtorisation?

Does the DHCP have enough leases and is giving them out to clients in that
subnet anyway?

The most common problem I see with RIS clients are normally resolved by the
following;
The NIC in the workstations are third party?
How to Add Third-Party OEM Network Adapters to RIS Installations
http://support.microsoft.com/default...en-us%3B246184

I do think it's all down to authorised DHCP server problem.

"Ben Grindy" wrote:

> Hello,
> I am new to RIS so hopefully I have set something up wrong and someone
> will pick up on it quickly. We currently have two domain controllers in our
> child domain, one hosting DHCP and the other hosting RIS. The domain
> controllers and the PXE client are on the same switch and subnet. The RIS
> server is authorized for DHCP but does not have an ip scope. When I start
> the PXE it returns "PXE-E53: No boot filename received". I have captured the
> network traffic which shows the PXE client sending a DISCOVERY and the DHCP
> DC returning an OFFER, but it just repeats that a couple times, not
> progressing any further into the handshake. If I give the RIS DC a dhcp
> scope, the PXE client will grab an IP from the RIS DC and proceed with the
> PXE boot. Unfortunately we want to keep the DHCP service on a separate
> server. Any suggestions are greatly appreciated.
>
> *Note* Both domain controllers have teamed NICs in a fail-over configuration.
>
> Thank You,
> Ben Grindy
> MIS Dept.
> Mercy Hospital and Health Care Center

> So my firstl question is the DHCP server is definitely authorised?

On the RIS machine, there is a green arrow on the server icon next to it's
name in DHCP. Also, it shows up on the "manage authorized servers" list on
the main dhcp server. Does this guarantee that it is authorized?

>Secondly
> have you tried restarting RIS services, DHCP server and even the box after
> auhtorisation?

I have restarted RIS, ran the risetup -check, and rebooted.

> Does the DHCP have enough leases and is giving them out to clients in that
> subnet anyway?

There are more than 250 leases available

> The most common problem I see with RIS clients are normally resolved by the
> following;
> The NIC in the workstations are third party?
> How to Add Third-Party OEM Network Adapters to RIS Installations
> http://support.microsoft.com/default...en-us%3B246184

The PXE client has an integrated NIC on the Intel mobo (D915GEV), so there
shouldn't be any major problems with that. (Remember that I can PXE boot when
I create a DHCP scope on the RIS Server)

> I do think it's all down to authorised DHCP server problem.
I have noticed that in the "Manage Authorized Servers" list, the main DHCP
controller name is in this form "name.domain.org" and the RIS server is in
this form "name.subdomain.domain.org" This may be a remnant from switching
to a child domain. Could this have any adverse effects?

Thanks,
Ben

That sounds authorised to me, but it clearly isn't doing its job. Do you have
admin access to the root domain, preferably the enterprise admin account? I
would try (or ask) to authorise the account from the root domain, and have a
look for unauthorised DHCP server messages on the root DC's.

I'll have another look around to see what else I can find out, I'll be back
on here tomorrow day (for UK anyway).

"Ben Grindy" wrote:

>
> > So my firstl question is the DHCP server is definitely authorised?
>
> On the RIS machine, there is a green arrow on the server icon next to it's
> name in DHCP. Also, it shows up on the "manage authorized servers" list on
> the main dhcp server. Does this guarantee that it is authorized?
>
> >Secondly
> > have you tried restarting RIS services, DHCP server and even the box after
> > auhtorisation?
>
> I have restarted RIS, ran the risetup -check, and rebooted.
>
> > Does the DHCP have enough leases and is giving them out to clients in that
> > subnet anyway?
>
> There are more than 250 leases available
>
> > The most common problem I see with RIS clients are normally resolved by the
> > following;
> > The NIC in the workstations are third party?
> > How to Add Third-Party OEM Network Adapters to RIS Installations
> > http://support.microsoft.com/default...en-us%3B246184
>
> The PXE client has an integrated NIC on the Intel mobo (D915GEV), so there
> shouldn't be any major problems with that. (Remember that I can PXE boot when
> I create a DHCP scope on the RIS Server)
>
> > I do think it's all down to authorised DHCP server problem.
> I have noticed that in the "Manage Authorized Servers" list, the main DHCP
> controller name is in this form "name.domain.org" and the RIS server is in
> this form "name.subdomain.domain.org" This may be a remnant from switching
> to a child domain. Could this have any adverse effects?
>
> Thanks,
> Ben

I am in the process of having it reauthorized from the root domain, I'll also
have the logs checked.

Ben


"Steve Goddard" wrote:

> That sounds authorised to me, but it clearly isn't doing its job. Do you have
> admin access to the root domain, preferably the enterprise admin account? I
> would try (or ask) to authorise the account from the root domain, and have a
> look for unauthorised DHCP server messages on the root DC's.
>
> I'll have another look around to see what else I can find out, I'll be back
> on here tomorrow day (for UK anyway).
>

The RIS server has now been re-authorized from the root domain. The logs
show that authorization was successful, but they don't show any sign of the
PXE Client trying to connect (not sure if they would if nothing is agreed on).


"Ben Grindy" wrote:

> I am in the process of having it reauthorized from the root domain, I'll also
> have the logs checked.
>
> Ben
>
>
> "Steve Goddard" wrote:
>
> > That sounds authorised to me, but it clearly isn't doing its job. Do you have
> > admin access to the root domain, preferably the enterprise admin account? I
> > would try (or ask) to authorise the account from the root domain, and have a
> > look for unauthorised DHCP server messages on the root DC's.
> >
> > I'll have another look around to see what else I can find out, I'll be back
> > on here tomorrow day (for UK anyway).
> >
>

Is the RIS server now functioning?

PS found this in the technical lib;
http://technet2.microsoft.com/Window...a34921033.mspx

Sounds like we chose the right course of action. There is also a
troubleshooting section.

http://technet2.microsoft.com/Window...a34921033.mspx

Let me know if it's working or not.

"Ben Grindy" wrote:

> The RIS server has now been re-authorized from the root domain. The logs
> show that authorization was successful, but they don't show any sign of the
> PXE Client trying to connect (not sure if they would if nothing is agreed on).
>
>
> "Ben Grindy" wrote:
>
> > I am in the process of having it reauthorized from the root domain, I'll also
> > have the logs checked.
> >
> > Ben
> >
> >
> > "Steve Goddard" wrote:
> >
> > > That sounds authorised to me, but it clearly isn't doing its job. Do you have
> > > admin access to the root domain, preferably the enterprise admin account? I
> > > would try (or ask) to authorise the account from the root domain, and have a
> > > look for unauthorised DHCP server messages on the root DC's.
> > >
> > > I'll have another look around to see what else I can find out, I'll be back
> > > on here tomorrow day (for UK anyway).
> > >
> >

The RIS server is not functioning. I have looked through numerous documents
on Microsoft's site, but haven't found anything that has helped yet.


"Steve Goddard" wrote:

> Is the RIS server now functioning?
>
> PS found this in the technical lib;
> http://technet2.microsoft.com/Window...a34921033.mspx
>
> Sounds like we chose the right course of action. There is also a
> troubleshooting section.
>
> http://technet2.microsoft.com/Window...a34921033.mspx
>
> Let me know if it's working or not.
>
> "Ben Grindy" wrote:
>
> > The RIS server has now been re-authorized from the root domain. The logs
> > show that authorization was successful, but they don't show any sign of the
> > PXE Client trying to connect (not sure if they would if nothing is agreed on).
> >
> >
> > "Ben Grindy" wrote:
> >
> > > I am in the process of having it reauthorized from the root domain, I'll also
> > > have the logs checked.
> > >
> > > Ben
> > >
> > >
> > > "Steve Goddard" wrote:
> > >
> > > > That sounds authorised to me, but it clearly isn't doing its job. Do you have
> > > > admin access to the root domain, preferably the enterprise admin account? I
> > > > would try (or ask) to authorise the account from the root domain, and have a
> > > > look for unauthorised DHCP server messages on the root DC's.
> > > >
> > > > I'll have another look around to see what else I can find out, I'll be back
> > > > on here tomorrow day (for UK anyway).
> > > >
> > >

Dam, have all RIS and DHCP services restarted?

I'll try and recreate the problem on my test rig tonight. We essentially
have one problem, the RIS clients are PXE booting, it asks for the network
service boot and you press F12, but were not picking up anything at all
apart from the message below?

What version of PXE boot are you using? What kind of NIC do the clients
have? Did we verify that there are no errors in the logs on the DHCP server?

"Ben Grindy" wrote:

> The RIS server is not functioning. I have looked through numerous documents
> on Microsoft's site, but haven't found anything that has helped yet.
>
>
> "Steve Goddard" wrote:
>
> > Is the RIS server now functioning?
> >
> > PS found this in the technical lib;
> > http://technet2.microsoft.com/Window...a34921033.mspx
> >
> > Sounds like we chose the right course of action. There is also a
> > troubleshooting section.
> >
> > http://technet2.microsoft.com/Window...a34921033.mspx
> >
> > Let me know if it's working or not.
> >
> > "Ben Grindy" wrote:
> >
> > > The RIS server has now been re-authorized from the root domain. The logs
> > > show that authorization was successful, but they don't show any sign of the
> > > PXE Client trying to connect (not sure if they would if nothing is agreed on).
> > >
> > >
> > > "Ben Grindy" wrote:
> > >
> > > > I am in the process of having it reauthorized from the root domain, I'll also
> > > > have the logs checked.
> > > >
> > > > Ben
> > > >
> > > >
> > > > "Steve Goddard" wrote:
> > > >
> > > > > That sounds authorised to me, but it clearly isn't doing its job. Do you have
> > > > > admin access to the root domain, preferably the enterprise admin account? I
> > > > > would try (or ask) to authorise the account from the root domain, and have a
> > > > > look for unauthorised DHCP server messages on the root DC's.
> > > > >
> > > > > I'll have another look around to see what else I can find out, I'll be back
> > > > > on here tomorrow day (for UK anyway).
> > > > >
> > > >

> Dam, have all RIS and DHCP services restarted?

Yes, RIS/DHCP have been restarted

> We essentially have one problem, the RIS clients are PXE booting, it
> asks for the network service boot and you press F12, but were not
>picking up anything at all apart from the message below?

Pressing F12 lets the bios jump to the "B4 D0 Yukon PXE" boot device, which
then runs PXE v2.1. It states the Client Mac Addr and GUID and then shows
DHCP..., after 15 seconds or so it changes to "PXE-E53 No boot filename
received"

> What version of PXE boot are you using? What kind of NIC do the clients
> have? Did we verify that there are no errors in the logs on the DHCP server?
>
The client has a built-in NIC (Marvell Yukon gigabit) on the Intel
Motherboard (d915gev) with PXE version 2.1

Quick google found this article

http://www.intel.com/support/network...e3/ba_msgs.htm

"Ben Grindy" <BenGrindy@discussions.microsoft.com> wrote in message
news:11838E7F-10FC-4C4C-98DF-16475DAB1BBC@microsoft.com...
>
>> Dam, have all RIS and DHCP services restarted?
>
> Yes, RIS/DHCP have been restarted
>
>> We essentially have one problem, the RIS clients are PXE booting, it
>> asks for the network service boot and you press F12, but were not
>>picking up anything at all apart from the message below?
>
> Pressing F12 lets the bios jump to the "B4 D0 Yukon PXE" boot device,
> which
> then runs PXE v2.1. It states the Client Mac Addr and GUID and then shows
> DHCP..., after 15 seconds or so it changes to "PXE-E53 No boot filename
> received"
>
>> What version of PXE boot are you using? What kind of NIC do the clients
>> have? Did we verify that there are no errors in the logs on the DHCP
>> server?
>>
> The client has a built-in NIC (Marvell Yukon gigabit) on the Intel
> Motherboard (d915gev) with PXE version 2.1

I'm like that, Ben can we upgrade to the latest PXE boot enviroment and test
again?

http://downloadfinder.intel.com/scri...leName=proboot


"Kevin Longley" wrote:

> Quick google found this article
>
> http://www.intel.com/support/network...e3/ba_msgs.htm
>
> "Ben Grindy" <BenGrindy@discussions.microsoft.com> wrote in message
> news:11838E7F-10FC-4C4C-98DF-16475DAB1BBC@microsoft.com...
> >
> >> Dam, have all RIS and DHCP services restarted?
> >
> > Yes, RIS/DHCP have been restarted
> >
> >> We essentially have one problem, the RIS clients are PXE booting, it
> >> asks for the network service boot and you press F12, but were not
> >>picking up anything at all apart from the message below?
> >
> > Pressing F12 lets the bios jump to the "B4 D0 Yukon PXE" boot device,
> > which
> > then runs PXE v2.1. It states the Client Mac Addr and GUID and then shows
> > DHCP..., after 15 seconds or so it changes to "PXE-E53 No boot filename
> > received"
> >
> >> What version of PXE boot are you using? What kind of NIC do the clients
> >> have? Did we verify that there are no errors in the logs on the DHCP
> >> server?
> >>
> > The client has a built-in NIC (Marvell Yukon gigabit) on the Intel
> > Motherboard (d915gev) with PXE version 2.1
>
>
>

Ignore that, you are already the latest PXE. Are you the latest BIOS flash
version as well? Your kit is pretty new so I presume so, but it wouldn't hurt
to try.

http://downloadfinder.intel.com/scri...submit= Go%21

Do we see the same problem on more than one client machine?

"Steve Goddard" wrote:

> I'm like that, Ben can we upgrade to the latest PXE boot enviroment and test
> again?
>
> http://downloadfinder.intel.com/scri...leName=proboot
>
>
> "Kevin Longley" wrote:
>
> > Quick google found this article
> >
> > http://www.intel.com/support/network...e3/ba_msgs.htm
> >
> > "Ben Grindy" <BenGrindy@discussions.microsoft.com> wrote in message
> > news:11838E7F-10FC-4C4C-98DF-16475DAB1BBC@microsoft.com...
> > >
> > >> Dam, have all RIS and DHCP services restarted?
> > >
> > > Yes, RIS/DHCP have been restarted
> > >
> > >> We essentially have one problem, the RIS clients are PXE booting, it
> > >> asks for the network service boot and you press F12, but were not
> > >>picking up anything at all apart from the message below?
> > >
> > > Pressing F12 lets the bios jump to the "B4 D0 Yukon PXE" boot device,
> > > which
> > > then runs PXE v2.1. It states the Client Mac Addr and GUID and then shows
> > > DHCP..., after 15 seconds or so it changes to "PXE-E53 No boot filename
> > > received"
> > >
> > >> What version of PXE boot are you using? What kind of NIC do the clients
> > >> have? Did we verify that there are no errors in the logs on the DHCP
> > >> server?
> > >>
> > > The client has a built-in NIC (Marvell Yukon gigabit) on the Intel
> > > Motherboard (d915gev) with PXE version 2.1
> >
> >
> >

I am moving to a different location (and job), so I won't be dealing with
this issue any more. For now the RIS server will have a separate scope for
PXE clients which are reserved for the specific MAC address of the machine.
In this configuration all of our PXE clients successfully boot.

Thank you for all your help,
Ben Grindy

"Steve Goddard" wrote:

> Ignore that, you are already the latest PXE. Are you the latest BIOS flash
> version as well? Your kit is pretty new so I presume so, but it wouldn't hurt
> to try.
>
> http://downloadfinder.intel.com/scri...submit= Go%21
>
> Do we see the same problem on more than one client machine?
>
> "Steve Goddard" wrote:
>
> > I'm like that, Ben can we upgrade to the latest PXE boot enviroment and test
> > again?
> >
> > http://downloadfinder.intel.com/scri...leName=proboot
> >
> >
> > "Kevin Longley" wrote:
> >
> > > Quick google found this article
> > >
> > > http://www.intel.com/support/network...e3/ba_msgs.htm
> > >
> > > "Ben Grindy" <BenGrindy@discussions.microsoft.com> wrote in message
> > > news:11838E7F-10FC-4C4C-98DF-16475DAB1BBC@microsoft.com...
> > > >
> > > >> Dam, have all RIS and DHCP services restarted?
> > > >
> > > > Yes, RIS/DHCP have been restarted
> > > >
> > > >> We essentially have one problem, the RIS clients are PXE booting, it
> > > >> asks for the network service boot and you press F12, but were not
> > > >>picking up anything at all apart from the message below?
> > > >
> > > > Pressing F12 lets the bios jump to the "B4 D0 Yukon PXE" boot device,
> > > > which
> > > > then runs PXE v2.1. It states the Client Mac Addr and GUID and then shows
> > > > DHCP..., after 15 seconds or so it changes to "PXE-E53 No boot filename
> > > > received"
> > > >
> > > >> What version of PXE boot are you using? What kind of NIC do the clients
> > > >> have? Did we verify that there are no errors in the logs on the DHCP
> > > >> server?
> > > >>
> > > > The client has a built-in NIC (Marvell Yukon gigabit) on the Intel
> > > > Motherboard (d915gev) with PXE version 2.1
> > >
> > >
> > >