Great post Alan -- great idea and an intriguing problem. Not that you necessarily suggest it is so, but it doesn't seem very plausible that the CaféNet DHCP server is supplying half-baked or malformed DHCP infos to the iDevices, especially since other toys have no issues. Keith's info supports this.
Following on from Keith's suggestion, you could even note down the CaféNet DHCP-assigned IP addresses for device, DNS, gateway etc. and then hardcode them into yr machine wen you are in a spot where you can't get good connections; this'd work for a while, until the DHCP lease expired and the server gave it to someone else :)
However, in order for DHCP to work it has to see your announcement on the underlying network; switching to a RL analogy, perhaps the volume, voracity and frequency of the announcement from the iDevices are inadequate?
Great post Alan -- great idea and an intriguing problem. Not that you necessarily suggest it is so, but it doesn't seem very plausible that the CaféNet DHCP server is supplying half-baked or malformed DHCP infos to the iDevices, especially since other toys have no issues. Keith's info supports this.
Following on from Keith's suggestion, you could even note down the CaféNet DHCP-assigned IP addresses for device, DNS, gateway etc. and then hardcode them into yr machine wen you are in a spot where you can't get good connections; this'd work for a while, until the DHCP lease expired and the server gave it to someone else :)
However, in order for DHCP to work it has to see your announcement on the underlying network; switching to a RL analogy, perhaps the volume, voracity and frequency of the announcement from the iDevices are inadequate?