I rock...no, I take that back, I f@#$ing rock!  There's no more rewarding a moment then when I figure out the answer to a problem that has plagued me for months!!!!  We have two networks at work..a dedicated T1 and a business class cable modem, the developers are supposed to be on the cable modem and the rest of the office using the T1.  Well while that's all fine and good, it doesn't really solve the issue of connecting to services on the adjacent network...  You must go out to the internet world (down to atlanta actually) and back just to hit a machine 5 feet from you.  That's simply ludicris..so I've been trying to figure out a way to use the routers we have to join the two networks.  Basically you should be able to go from one network to the other and stay within our internal network, but still be able to get to the internet when needed.  Sounds easy enough right?  Well it isn't...in fact I've been working on this off and on since April...that's almost half a year.  Well as of this moment, I have solved the problem...and it was actually quite easy, once I got on the right track.  Basically I needed to enable Cisco's Express Forwarding...that was the missing link.  That allowed the router to forward packets from one interface to the next...once I got that the rest was merely setting up a policy that defines a route for each network based on the machine that made the request.  So if you are on the T1, you'll hit the internet via one route 1 (passing through our router), but of you're on the cable modem you'll go out via route 2 (again, passing through our router).  This, of course, would have been worlds easier if the wonderful folks at Time Warner would just let me modify the routing table of our cable modem, but..they won't.  So I had to work around them...I'll be patting myself on the back for the rest of the day...That is all...