I did more testing and came to a very interesting situation, if I connected
the BOOTP client to a HUB and then to the Ethernet Switch , everything works
just fine however if I connected the BOOTP client directly to the
Also, I have tried to turn off auto-negotiating on the Ethernet Switch and
forced the BOOTP port to 10MB but didn't make any difference.
Moreover ...yes when I connected the BOOTP client directly to the Ethernet
Switch, both LED indicators at both devices indicate that the physical layer
Please note that the BOOTP server was connected directly to the Ethernet
switch in all cases.
help...Ethernet gurus out there ??
> I would presume if the 333T can't pass the BOOTP/DHCP requests to that
> service, they must be on seperate VLANs, or the service is on the other
> of a router. In which case, that router should be set to forward the
> requests. If that service is on a different VLAN, then you might be able
> to place both VLANs onto that server link, and the DHCP/BOOTP server
> Where is your BOOTP/DHCP server with respect to the clients??
> > The 333T is a layer 2 switch and does not have DHCP/BOOTP relay
> > The 333R does have this function though, unfortunately 333T cannot be
> > upgraded to 333R through software. Probably you need to get the other
> > > Hi there,
> > > I wonder if someone can help me with this problem,
> > > The problem is passing DHCP and BOOTP frames through Cajun the P333T
> > > switch!. Does Cajun P333R solve the problem? Is it possible to upgrade
> > from
> > > P333T or P333R? If yes is it software or firmware or hardware?
> > > Your prompt response is highly appreciated.
> > > Wael Menyawi