Are you using DHCP or static addresses? ...in the office where networking works? ...in the office where the networking doesn't work?
Are you using the wired NIC or the wireless NIC? ...in the office where networking works? ...in the office where networking doesn't work?
I suspect that you are using the wired NIC with static addresses in the office where networking works. That would prevent your machine from automatically configuring itself on a new LAN (in the office where networking doesn't work). If that is true then the reason that the add route command doesn't work is that you have a different subnet than the one in the office where networking works. (192.168.0 vs. 192.168.1)
If you use DHCP in both offices then it seems that your machine is not being autoconfigured in the office where networking doesn't work. If that is true then find out if anyone else in that office uses DHCP for their computers. If every other machine in that building uses static addresses then the DHCP server may not be sending valid information to your computer. Some building LANs are configured to only give addresses to computers with specific hardware addresses. This is a good security measure because it makes visitors unable to get a network address when they plug into the network. This is a good thing. See if the LAN administrator in the building where networking doesn't work has restricted DHCP service to known computers and see if you can get on the list of computers authorized to recieve a DHCP address.
Check to see if you have an IP address when you issue the ifconfig command. See if the ifconfig command reports any packets transmitted and received.
eth0 Link encap:Ethernet HWaddr 00:09:5B:BB:F1:ED
inet addr:192.168.1.222 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:291369 errors:0 dropped:0 overruns:0 frame:0
TX packets:162321 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:430071793 (410.1 Mb) TX bytes:11400821 (10.8 Mb)
Interrupt:201 Base address:0xc000
Try turning off the wireless card. Notebook computers usually/always have a physical switch somewhere on the computer case to turn the wireless circuit off. Boot the computer in both offices with the wireless NIC turned off and see what happens. This will at least help to determine what part of the system (wired or wireless NIC) you are using in the office that works.
I also noticed that your route command is applied to eth1. Most computers will start numbering ethernet cards at eth0. Also, the eth? name will USUALLY apply to wired NICS while wireless NICS will have some other name like ath0 for Atheros based wireless NICS. Of course all of this is configurable so it depends on your Linux distro and on how you or your sysadmin set your system network up.
Please give these ideas a try and report back what you find.