Re: RIS Stopped Working Last

From: NIC Student (nospam_at_nospam.land)
Date: 03/19/04 

Date: Fri, 19 Mar 2004 10:56:38 -0800

Hi Brian,

For the test, let's also try and get the DHCP/RIS/Client all attached to the
hub so DHCP requests won't be timed out by the Cisco if that's the problem.
Did you try pausing the RIS client for 20 secs as I suggested earlier? 

-- 
Scott Baldridge
Windows Server MVP, MCSE
"NIC Student" <
> Brian, this is a frustrating one.  I still am thinking it's the Cisco that
> is the problem.
>
> Can you try one more test:
>
> Plug the Risserver into a hub.
> Plug your client into the same hub.
> Plug the hub into the usual switch to which the RIS server is normally
> connected.
> Check connectivity from RISServer>hub>rest of network.
> Test RIS with the 3Com disk, F12 on startup , and the windows RBFG boot
> floppy.
>
> Let me know.
>
> -- 
> Scott Baldridge
> Windows Server MVP, MCSE
>
>
> "Brian Anderson"
> > I'll answer all of this is the same order you presented it.
> >
> > Yes - ran the RISETUP -CHECK and is verified that everything was all
> right.
> > Even ran it from the GUI in case it did something different and it also
> said
> > the RIS implementation was fine.
> >
> > Yes - if I delete a lease and then try to RIS it fails.  If I don't
delete
> > the lease and try to RIS it fails.  When I boot normally the system
> > connects, refreshes the lease and works normally.
> >
> > Yes - the server only has one NIC.
> >
> > Yes - the server had SP4 applied.  I also applied all other patches
> > including the patch for the ASN1 problem  This is the point at which the
> RIS
> > communications stopped working.  I tried backing that out but no luck.
> >
> > Yes - I used the 3Com floppy at the link you list.  I had discovered
this
> > link as a recommendation in another thread.
> >
> > No spanning tree - it is a Cisco switch which has been set universally
to
> > portfast.  And it should be noted that the port in use haven't changed
> > anywhere along the line.  It also doesn't matter which port I use.
> >
> > I could forward you the log files but there is nothing to see.  I never
> get
> > a message on the server except for the standard 1003 BINL started
> > successfully messages.  All I get are the PXE-E51 "No BOOTP or DHCP
offers
> > received" messages which occur only on the client.  It appears that the
> > clients never see the server.
> >
> > I have had to convert 1 of the last 2 systems manually because it had to
> be
> > deployed.  It is possible (even likely) that the last system will also
> have
> > to be deployed in the next couple weeks.  If this happens it will render
> the
> > RIS configuration useless.  I have a feeling I will never know what
> happened
> > to RIS after 18+ successful deployments.
> >
> > "NIC Student"
> > > OK, let's make sure of:
> > >
> > > You have run Start>Run>RISETUP -CHECK>OK on your RIS Server and it
says
> > > there are no problems.
> > >
> > > You can delete the DHCP lease for a client, then after attempting to
> RIS,
> > > you can see a lease has not been given.
> > >
> > > Your RIS server has only one nic. *important*
> > >
> > > RIS, DHCP and clients are on one subnet.
> > >
> > > You have applied Service Pack 4 to the RIS Server.
> > >
> > > Try booting from the 3Com boot floppy instead of the Windows one, get
it
> > > from here:
> > > http://www.mvps.org/serverstuff/
> > >
> > > Do you have spanning tree turned on your switch/router between the
> clients
> > > and RIS?  Pause your clients by hitting the pause button on the
keyboard
> > as
> > > it is searching for DHCP.  Wait 20 seconds and hit any key to resume.
> Let
> > > me know if spanning tree is enabled.
> > >
> > > You can email the system and app logs from the RIS server to me at
> > > sbaldridge@NOSPAMmvps.org (remove NOSPAM).
> > >
> > > -- 
> > > Scott Baldridge
> > > Windows Server MVP, MCSE
> > >
> > >
> > > "Brian Anderson"
> > > > I just tried this again with a new system and got the same errors.
On
> > > > the workstation that I am trying to RIS I get an error which says
> > > >
> > > > "PXE-E51 No BOOTP or DHCP offers received."
> > > >
> > > > Some other notes:
> > > > - I have 2 other laptops from vendors that were brought in to this
> > > > network for the first time today and they both received DHCP
> addresses.
> > > > - I have already Unauthorized and Re-authorized DHCP.  No Change
> > > > - I have 50 addresses set aside for DHCP and only 23 in use.  Just
for
> > > > kicks I added 20 more to the scope with no change.
> > > > - I took a couple of the systems that had been previously configured
> > > > using RIS and tried to re-run the RIS install and got the same
error.
> > > > - PXE boot disk using the USB floppy got the same error.
> > > >
> > > >
> > > > NIC Student wrote:
> > > > > Well, if you are not getting a DHCP address, there is something
more
> > > going
> > > > > on than a RIS problem.  We need to find out why the machines are
not
> > > getting
> > > > > DHCP first.  You said your have checked that DHCP is authorized.
> Have
> > > you
> > > > > unauthorized, then reauthorized the DHCP server?
> > > > >
> > > > > Is this server multi-homed?  Make sure the server is authorized by
> ip
> > > > > address rather than by computer name.
> > > > >
> > > > > Do you have enough addresses in the DHCP scope to allow for more
> > leases?
> > > > >
> > > > > Are you sure the nics are functional in the two workstations?
> > > > >
> > > > > Do you have a USB floppy to put on the machines so they can boot
> from
> > > floppy
> > > > > instead of the PXE nic for these tests?
> > > > >
> > > > > What is the exact error 1003 message you are receiving?
> > > > >
> > >
> > >
> >
> >
>
>
Loading