Kleaverjr, I have the exact same problem. I hope somebody replies to your post, since it seems that we are the only two. I once bypassed my router, used tcp-com and hamachi, and got it to work. Just once. Two days later, we tried to actually get some gameplay in, and no matter what we tried, after four hours NOTHING lol. My friend could see my game in tcp/ip, but couldnt join it. It was serial that actually worked. Modem won't help, I'm quite sure. Of course IPX is an old protocol that I know nothing about, and there's no input option in game for particulars like addresses. Some study gave me the implication that IPX should be set up through windows settings, but I'm convinced it will never work in any way, for anybody. I'm quite sure that tcp-com has lasting effects when you create virtual com ports, such that it eats up the ports permanently. There's no instruction in the help files for undoing the tcp-com effects, and no options exist in the program. What ended up happening involved me doing some intense reading of the help file, understanding tcp-com front to back, and then finding that the serial com port I select is the exact one that Rebellion won't let me create a game on, no matter what I did. No error message from the game, it just acts like you never pushed teh arrow and clicked "ok" when you choose the serial port that you need. Seemed Reb. and T-C didn't want to share ports, although that's the premise of the solution. So far we've probably logged ten hours of persistence and experimentation. Grinds the nerves, but solving computer troubles is a favorite passtime of mine so it's not so bad.