On 21/05/13 14:40, Brett Parker wrote:
Not using ufw, but apparently you should be able to get it to work by adding: -A ufw-before-input -p udp --sport 68 --dport 67 -j ACCEPT To the file: /etc/ufw/before.rules Cheers,
Thanks Brett, it's not that I'm afraid. I suspect it's not actually a DHCP at all.
I ran dhcpdump on the server whilst trying to connect, once with the firewall on, and once with it off. The output was identical, apart from the time stamps. Part way through the process, while the firewall was on, the drive started signalling DHCP error, whilst it was still being granted leases etc.
I suspect it's after something else, like the DCOM port, or samba ports or something like that. I'll give that a try. But in the meantime, any suggestions for any good, simple to understand (use of and output of) traffic monitoring apps so I can see what the drive is trying to connect to? Wireshark comes to mind. Am I right?
Cheers!
Steve