Equipment: 1. wireless router: Linksys WRT54G v.4, Firmware Version: v4.20.6 (2005-05-26) 2. wireless printserver: D-Link DP-G321, Firmware Version: 2.00 (2005-06-27) Intranet settings: 1. default gateway (router address): 192.168.1.1; subnet mask: 255.255.255.0 2. DHCP server enabled, IP address range: 192.168.1.2 - 192.168.1.100 3. The printserver firmware allows me to assign the printserver static IP address (static IP addressing is needed to make printing easy). This used to work fine - and the router would show that the print server (identifiable by name and MAC ID) was indeed assigned the requested IP address, even though the requested IP address was within the range used by the DHCP server. The 3 other devices on the network are all automatically assigned IP addresses. Issue: Now however, the printserver is no longer being assigned the requested IP address. I.e., the manual assignment setting is requesting 192.168.1.20, but the router shows that the printserver has been assigned 192.168.1.3. This also happens if the requested IP address is outside the DHCP address range - i.e., the static IP requested is 1.110, the printserver gets assigned an address inside the DHCP range, e.g., 1.3. In fact, if I type in the URL http://192.168.1.3, the printserver home page appears. Since the printserver thinks it has been manually assigned 1.20, but in fact has been assigned 1.3, it no longer allows me to print. I have tried changing the manually assigned IP address to no avail. For example, if I change the manually assigned IP address to 1.3 and reset the printserver, it now thinks it has been assigned 1.3, but the router shows that the printserver has been assigned 1.5 (my computer was sitting at 1.4, so presumably that's why it jumped over 1.4). If I then change the manually assigned address to 1.5, the actual address assigned by the router becomes 1.6. Why is the Linksys router not assigning the static IP address requested by the printserver? Any thoughts or suggestions? I emailed Linksys about this 2 days ago, but no response as of yet.