I would suspect the printers also. One other thought I had was that it would be possible to misconfigure routers such that there was a "helper address" loop!
The helper address should point to the actual server (or a directed broadcast for the network that a server is on). But a newbie Cisco person might think it should point to the next-hop router. Then that router could point backwards due to a misconfiguration. And you could get a loop and see a result like your 16 hops. I doubt that this is your problem, but it could be. Please let us know what you discover. This is an interesting quandary. Thanks. Priscilla At 08:05 AM 3/27/02, kevhed wrote: >Yea, that "16 hops" statement had me suspicious too, since that e-net >interface is the first hop for that printer. I'm guessing that the printer >has some issues with bootp. >Thx >-- >Kevin Keay (N+,CNE,CCSE,CCDP,CCNP) >Sr. Network Specialist >Ondeo-Nalco >One Ondeo-Nalco Center >Naperville, IL 60563 >(630) 305-2557 >""Priscilla Oppenheimer"" wrote in message >[EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > > At 10:54 AM 3/26/02, kevhed wrote: > > >Hi all, > > >I'm having a problem with bootp. I have a remote site that is connected > > >back to corp via frame relay circuit. The clients at this remote >location > > >are using bootp successfully to get network settings, but the printers > > >(tektronics 740;s) can not. When sniffing the frame circuit, I am not > > >seeing any bootp packets (from printers) coming from the e-net int of >that > > >router. I have the ip helper config'd on the e-net int, as the clients >are > > >working successfully. > > > > > >Doing a debug on an access list for udp, I get this: > > >5w6d: UDP: rcvd src=0.0.0.0(68), dst=255.255.255.255(67), length=564 > > >5w6d: BOOTP: opcode 1 on interface FastEthernet0, 46053 secs, 16 hops > > > > Is the debug showing the packet from the printer? That 16 hops looks > > awfully strange. The client should set the BOOTP hop field to zero. A > > router can increment it, but I doubt that the packet has really been > > through 16 routers. Maybe the printers have a buggy implementation of > > BOOTP. Did they ever work? My guess is that a router won't forward a BOOTP > > with hops as large as 16 already. > > > > My next step would be to sniff on the Ethernet side and compare BOOTPs > > coming from the clients to BOOTPs coming from the printers. > > > > This is going to be a tricky one. Please let us know what you discover. > > Thanks. > > > > Priscilla > > > > > > >The bootp requests never gets to serial int. Any ideas what this error >is? > > > > > >Thx > > > > > >-- > > >Kevin Keay (N+,CNE,CCSE,CCDP,CCNP) > > >Sr. Network Specialist > > ________________________ > > > > Priscilla Oppenheimer > > http://www.priscilla.com ________________________ Priscilla Oppenheimer http://www.priscilla.com Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=39659&t=39532 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
