Ok, here's the deal, me and a friend are going to be linking up eachothers local networks with eachother via an ad-hoc link. The ad-hoc link is with 2 cisco 350 aironet pci cards (100mW), eventually we will be attaching parabolic antenna's to these but that's a way's off yet. So I brought my server to his house, set it up and attached a computer to it so we could figure out how to ping my client computers from his and vice versa. So first step is create an ad hoc network (same as using wireless bridges) with the two cisco cards with static ip's 192.168.0.252 and 253. That went perfect, the servers could see eachother, all was happy. Then came the time to set up routing and remote access with static routes (windows 2003) so that we could forward requests from my local network (on a different ethernet card of course) across the ad-hoc link to his local network. After some head-banging we finally got the routing right and could see that routing requests were being fulfilled when we pinged, but the requests would always time out. That made no sense, finally by dumb luck I happened to look up at our switch and notice that activity on the network was pegged. I found that if I disabled the rf radio (the ad-hoc network) then network traffic would stop. This leads me to believe that somehow something is causing an internal loop in the intranet we are trying to set up because once the ad-hoc link is up I can't even ping my client computers from my server. So, basically, I have come to the point of not being able to look beyond my own nose at this problem, it's driving me bonkers (we spent 12 hours straight working on it last night only to run into this). So I'm going to provide you a visual representation of what we want to do hoping that someone better at this than me (or with a clearer head) can shed some light on the issue. Thank you very much, if anyone figures this out I owe them a coke .