Sometimes the RIS server works fine and other times it doesn't seem to do anything

I am presently hired on as a contractor and they had a RIS sever their prior to me coming on board.  Sometimes the server works just great and other times it doesn't do anything. The RIS server is a Windows Server 2003 Standard Edition. I usually start the client machine up and hit F12 to go to onboard network controller.  It starts by going to client mac address, dhcp and than can't find the RIS. I end up getting a PXE -MOF:  Exiting Intel Boot Agent.  I set the client machine up for PXE prior to doing the F12.  Any ideas on what I'm doing wrong or what could be wrong with the RIS?
Who is Participating?
PberConnect With a Mentor Solutions ArchitectCommented:
What is setup to use DHCP (RIS)?

The DHCP and RIS servers should have static IP's.  The clients will need to be running DHCP in order for RIS to work.
PberSolutions ArchitectCommented:
This can be cause by a number of reasons:

DHCP server not running
RIS server not running
Subnet isn't forwarding boardcast traffic (i.e. DHCP relay)
NIC settings on client do match switch. (i.e. Auto/Auto on client, 100/FULL on switch).

If it is random, it probably isn't the DHCP or RIS server.  If it happens only on certain areas (i.e. This building), I would suspect the network gear isn't confiigured with a DHCP proxy.  I would suspect that it might be related to hard coded Client NIC settings conflicting with how the port on the switch is configured.  You might want to confirm the port settings with the networking group .

wgallipeauAuthor Commented:
Right now its set up to use DHCP (RIS) and doesn't have a static IP address at all.  Should this be changed?
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.