I still find it odd that the 622 says it wasn't connected yet it talked to other machines on my network. I don't claim to be an IP expert, nor play one on TV, but here's generally what happens.
The device needing an address puts out a DHCP (Dynamic Host Configuration Protocol) request, sending a frame from it's MAC (unique Ethernet hardware address) to FF:FF:FF:FF:FF:FF (broadcast/everybody) with an IP of 0.0.0.0 (I don't have one yet) to 255.255.255.255 (IP broadcast). If a DHCP server hears the request, it then offers to lease an IP address to the device. The device responds "yes" and the DHCP server acknowledges. The device now has an IP, a subnet mask (used when comparing the destination IP address to determine if it is local or not), a DNS (to resolve URL's to IP's) address, the network's gateway address (to get from the local Ethernet LAN to Internet), and the length of time of the lease. There is usually no further communication between the device and the DCHP server until halfway through the lease when the device begins to request to renew the lease. If at any time the device reboots, if the lease is still valid it will do a "gratuituous ARP", in essence, to ask if anyone is using the IP it thinks it has. If there is no response it is happy and continues to use the IP address.
I'm not sure if Dish Network follows the protocol rules or does a DHCP renewal request after every reboot. It's hard to tell because most DHCP servers will give the device the same address it already had if it hasn't been reissued to anyone else.
If a device loses physical network connectivity, Mr. DHCP server still maintains a lease for that device. This is the point missed by many folks troubleshooting connectivity problems.
A good way to test if your receiver is "OK" is (for Windows machines) Start / Run / type in the three letters: CMD . In the command window type in PING X.X.X.X (the address your receiver thinks it has. To reconcile MAC and IP addresses, just type in the command ARP -a within 2 minutes or so of the PING. If you suspect DHCP server problems, go to a machine you can do without and type: IPCONFIG / ALL you can then type IPCONFIG / RELEASE followed by: IPCONFIG / RENEW . If you get a renewal, then Mr. DHCP is fine. If you don't get a renewal, you know your DHCP is not working and can "thank" me for prematurely losing connectivity before your PC's lease expired.
I put this out as a starter. Please feel free to correct/clarify anything I've just described -- I'm guessing we can't know too much about IP.