Ok, I know I'm not the only one who has this one and I know this has to be a Vista bug.BBIAgent Firewall/Router on an IBM 306 1RU server. One ethernet port attached to our domain network. The other ethernet port with a crossover cable attached to our Linux FTP box.Works great in XP with no issues when routing to it. Under Vista, no sir!Here's what's happening. Static route entered with a persistent switch. Route Print shows it and entered correctly. Ping the IP that is the destination but it won't respond. Always times out. I have disabled AutoTuning, disabled IPv6. Ran a trace capture while attempting to ping the address and noticed that the ARP is returning the ethernet physical address as 00:00:00:00:00:00. So I get the physical address and enter it as a static ARP entry. Of course the only way to do this is to delete the persistent route first then do an arp -d to delete the invalid entry that is listed when I do an arp -a -v command. Even after all of that it doesn't work. So I look at the tracking in the BBIAgent and notice that an XP machine uses port 1138 and up whereas Vista wants to use ports 49500 and up! WTF?! Why is that so? Not only that but I notice that the destination IP address is going to the gateway that is entered in the static route and not the actual destination address it needs to go to! Why? What is so different in Vista when it comes to static/persistent routing? It should be so simple yet it's such a friggen PITA! Microsoft, I really hope you are reading these posts and making SP1 as soon as possible to fix these issues. Home users are ok with most stuff but us IT people are getting bloody foreheads trying to figure out your bugs! I can't believe that you even would think of charging us for support on this OS since it's so bug ridden in the advanced networking side.