It's rare for a wireless AP to require static addressing; I doubt all your patients are using static IPs as that would mean handing a new IP address out to every new patient.

Try using the default settings as you do at home but remove all wireless connections except your home router and then reboot the handset at work. The office router should then show up as available.

 

Try looking in your router settings for an option similar to IP header checksum and disable it.
Also what security setting is your router?

 

What is your DHCP server at work? is it the router itself or a windows server on the network?

 

It may be unrelated to your particular problem but what version firmware are you on, as i seem to remember reading on here some of the older versions had wifi problems.

 

This happens to me every once in a while (I have separate DSL Modem netgearDG834 + rounter DIR-655) and it is usually the DSL modem not the phone or any other device which is connected that has the problem. It looses track of the DNS server which is actually relayed from your ISP ie. even though windows sees DNS server as the primary PC IP address, if you go into the router settings the DNS server will have an address that corresponds to your ISP's server. Suggest you reboot the modem and router and verify all wired connections are working first. After that it may have something to do with the wireless channels the router is using that may need changing to a different one but this is usually automatic.

 

I was having an issue with my SGS2 running 2.3.4 connecting to my Linksys WRT160N running DD-WRT v24-sp2 (08/07/10) vpn-small firmware that use to not have a problem. In the wireless settings I had both Wireless Channel and Channel Width on Auto and the security was WEP. I would see the phone loop from scanning -> connecting -> obtaining IP -> disconnected -> (repeat and repeat). I set the Wireless Channel to 8, the channel width to 20 Mhz and the security to WPA2 (TKIP+AES) and it is now working.

 

The OP has already stated that he has no access to the router's setup, unfortunately.

It may be something fixable with a firmware update, but it could also be that the router is using the TKIP rather than the AES encryption algorithm. Trying to connect to my own router when it was set to use TKIP showed exactly the same symptom - handset would connect but not complete authentication and therefore not obtain a valid network address.