<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic RIS 2003 troubles! in Windows Server 2003</title>
    <link>https://community.hpe.com/t5/windows-server-2003/ris-2003-troubles/m-p/3264499#M673</link>
    <description>OK,&lt;BR /&gt;&lt;BR /&gt;My company recently approved an upgraded RIS server.  We were using Server 2000.  We put together a nice server and bought Server 2003 for it.  I set up RIS services and went through its whole bit and then afterwards authorized it on our DHCP server.  I also went into AD and set it to respond to clients.  I also at that time unauthorize the previous RIS server and set it not to respond to clients in AD.&lt;BR /&gt;&lt;BR /&gt;Here is my problem:&lt;BR /&gt;&lt;BR /&gt;Client machines on the same subnet constantly get "no reply from the server".  Every blue moon it will receive a reply and ask me to press F12 to boot.  However, it is not consistent and I can barely ever even get it to give me an F12. &lt;BR /&gt;&lt;BR /&gt;I have tried replacing the NIC card and that didn't work.  I was using a leased IP address, so I set it static, that didn't make a difference.  I even in desperationg formatted and installed Win 2000 server and set up RIS and it is doing the same exact thing!  I also have checked the services to make sure they were started each time. &lt;BR /&gt;&lt;BR /&gt;Help please!&lt;BR /&gt;&lt;BR /&gt;-galen</description>
    <pubDate>Fri, 30 Apr 2004 12:56:51 GMT</pubDate>
    <dc:creator>Galen Counselman</dc:creator>
    <dc:date>2004-04-30T12:56:51Z</dc:date>
    <item>
      <title>RIS 2003 troubles!</title>
      <link>https://community.hpe.com/t5/windows-server-2003/ris-2003-troubles/m-p/3264499#M673</link>
      <description>OK,&lt;BR /&gt;&lt;BR /&gt;My company recently approved an upgraded RIS server.  We were using Server 2000.  We put together a nice server and bought Server 2003 for it.  I set up RIS services and went through its whole bit and then afterwards authorized it on our DHCP server.  I also went into AD and set it to respond to clients.  I also at that time unauthorize the previous RIS server and set it not to respond to clients in AD.&lt;BR /&gt;&lt;BR /&gt;Here is my problem:&lt;BR /&gt;&lt;BR /&gt;Client machines on the same subnet constantly get "no reply from the server".  Every blue moon it will receive a reply and ask me to press F12 to boot.  However, it is not consistent and I can barely ever even get it to give me an F12. &lt;BR /&gt;&lt;BR /&gt;I have tried replacing the NIC card and that didn't work.  I was using a leased IP address, so I set it static, that didn't make a difference.  I even in desperationg formatted and installed Win 2000 server and set up RIS and it is doing the same exact thing!  I also have checked the services to make sure they were started each time. &lt;BR /&gt;&lt;BR /&gt;Help please!&lt;BR /&gt;&lt;BR /&gt;-galen</description>
      <pubDate>Fri, 30 Apr 2004 12:56:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/windows-server-2003/ris-2003-troubles/m-p/3264499#M673</guid>
      <dc:creator>Galen Counselman</dc:creator>
      <dc:date>2004-04-30T12:56:51Z</dc:date>
    </item>
    <item>
      <title>Re: RIS 2003 troubles!</title>
      <link>https://community.hpe.com/t5/windows-server-2003/ris-2003-troubles/m-p/3264500#M674</link>
      <description>Where is your DCHP server located? On the same IP-subnet as the client and RIS server also?&lt;BR /&gt;&lt;BR /&gt;If not a local DHCP server or DHCP relay agent may be needed.&lt;BR /&gt;&lt;BR /&gt;If that is OK, then it seems you have checked the other possible DHCP issues (autorization), but anyway double-check it and also refer to point 3 in this&lt;BR /&gt;&lt;A href="http://support.microsoft.com/default.aspx?scid=kb;en-us;284987" target="_blank"&gt;http://support.microsoft.com/default.aspx?scid=kb;en-us;284987&lt;/A&gt;&lt;BR /&gt;for relevant events in the log confirming RIS operation.&lt;BR /&gt;&lt;BR /&gt;Other known issues are mostly with servers that have more than one NIC&lt;BR /&gt;&lt;A href="http://support.microsoft.com/default.aspx?scid=kb;en-us;329839" target="_blank"&gt;http://support.microsoft.com/default.aspx?scid=kb;en-us;329839&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Cheers,&lt;BR /&gt;Rune</description>
      <pubDate>Sat, 01 May 2004 17:27:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/windows-server-2003/ris-2003-troubles/m-p/3264500#M674</guid>
      <dc:creator>Rune J. Winje</dc:creator>
      <dc:date>2004-05-01T17:27:09Z</dc:date>
    </item>
    <item>
      <title>Re: RIS 2003 troubles!</title>
      <link>https://community.hpe.com/t5/windows-server-2003/ris-2003-troubles/m-p/3264501#M675</link>
      <description>Hello&lt;BR /&gt;&lt;BR /&gt;Just my $0.2 cents.&lt;BR /&gt;Make sure in the old RIS server you stop and disable all the services.&lt;BR /&gt;Make sure that the NIC card supports RIS, if not then add the NIC driver.&lt;BR /&gt;Other than that, Rune gave some good advice.&lt;BR /&gt;Good luck</description>
      <pubDate>Sun, 02 May 2004 19:26:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/windows-server-2003/ris-2003-troubles/m-p/3264501#M675</guid>
      <dc:creator>Norman_21</dc:creator>
      <dc:date>2004-05-02T19:26:21Z</dc:date>
    </item>
  </channel>
</rss>

