4 replies to this topic

[oreissig]

Hi there,

I'm having problems booting my old Unix workstations via bootp:

Rcvd BootP Msg for IP 0.0.0.0, Mac 08:00:2B:3D:DD:E5 [04/12 23:40:17.788]

BOOTP: proposed address 192.168.1.200 [04/12 23:40:17.788]

10544 Request 2 not processed [04/12 23:40:17.788]

These messages come up on every retry the booting machine makes.

Here's my configuration: http://pastebin.com/kWCsdEuQ

I hope someone has a solution for the issue

[Sha0]

I'm having problems booting my old Unix workstations via bootp:

Rcvd BootP Msg for IP 0.0.0.0, Mac 08:00:2B:3D:DD:E5 [04/12 23:40:17.788]

BOOTP: proposed address 192.168.1.200 [04/12 23:40:17.788]

10544 Request 2 not processed [04/12 23:40:17.788]

These messages come up on every retry the booting machine makes.

Where did you read about TFTPD32 BOOTP support? DHCP != BOOTP. Maybe your DEC UNIX computer would be happier with a BOOTP service?

[oreissig]

Basically it comes down to the point: Why would it log about bootp requests, if it didn't know anything about bootp?

The problem is that I know of no simple (free, without heavy NT service) bootp service for current windows versions.

Edited by oreissig, 04 December 2012 - 11:15 PM.

[Sha0]

Basically it comes down to the point: Why would it log about bootp requests, if it wouldn't know anything about bootp?

Maybe it does. Did you read about it somewhere?

If you capture the traffic with tcpdump or Wireshark, that might reveal more information.

Is that chocolate, in your picture?

[oreissig]

Maybe it does. Did you read about it somewhere?

I think I already used some older version of tftpd32 to netboot unix workstations, but maybe my memory is wrong on that

If you capture the traffic with tcpdump or Wireshark, that might reveal more information.

The request looks legit on first sight, but there seems to be no answer from the server at all.

Is that chocolate, in your picture?

yes, just some random avatar I found to be funny