Hi guys (and ladies).  I need some help here.

I am having a problem with a particular FSHost flight server and I can't seem to figure it out.  Been trying for a few days.  Another guy and I played with this a bunch last night....to no avail but we isolated the "symptoms" a bit.

So there I am connected on the flight server in multiplayer in the fs2004 flight sim.  Teamspeak is connected and doin' fine too on that server (everyone there uses Teamspeak when flying.....I hate using the chatbox when flying).  If there is NO ONE online, I can then get my copy of AIBridge 3.0 to connect just fine, and get the AIBRidge "connected" message on the machine window that it is running on, and can minimize it to the tray.  

HOWEVER, if someone else tries to connect once my AIBridge is connceted he gets the evil, "All players were not able to connect" message. If I disconnect my copy of AIBridge, the other person can now connect just fine.  If HE then tries to connect HIS copy of AIBridge, he gets AIBridge on just fine!  Curious!  And I can connect my fs2004 sim just fine when his fs2004 sim and his copy if AIBridge are both connected.  I can't connect my AIBridge when both he and his AIBridge are connected.

Once the other person is connected in JUST his flight sim (no AIBridge) if I try to connect AIBridge to the server, it connects (shows in the chat box in fs2004) for a SHORT while but then hangs and goes unresponsive.  I have to CTRL+ALT+DEL and endtask to close it...... and it sends the typical message to good ole' Uncle Bill.  I also tried running it in Win 2000-ME mode instead of XP..... to no avail.

FS2004 is on my #1 machine.  My copy of AIBridge is located on my #2 computer which is on a 100 mbit switched hardwired LAN with the other pit machines.  The LAN machines have fixed IP addresses set up.  I use an Actiontec GT704 -WG DSL modem (wired, not wireless) for net access and the machines are hooked to it on the LAN.  The network sim communications are supported by FSUIPC and WideFS and all computers "see" each other just fine (all gauges work).

I have the usual 23456, 23457, 23458, 6073, and 8767 udp/tcp open on the DSL modem and in both the #1 machine and #2 machine's firewall.  I do not run FSNav...so no port opened for that.  I have NOT opened the "alternate DirectX" range of 2300-2400 yet.  I have the AIBridge and FS2004 programs both set as "exceptions" in Win XP firewalls on both machine #1 and #2.

After experiencing this issue a couple of days ago, I was recently told by someone that you also need to have 47624 TCP/UDP open for AIBridge..... and I have opened that on the #1 and #2 machines and DSL modem too.

This same symptom happens if I try to use the copy of AIBridge 3.0 I have on the #1 machine too.  So this SEEMS to point to the DSL modem.

AIBridge works reasonably well for me on many other FSHost flight servers ..... although it has always been plagued by "erratic behavior" on FSHost servers in general (I understand that others have the same issues).

Are there any other CONFIRMED ports that AIBridge needs opened?  Do you have any other suggestions for me?  I love flying on this particualr server, and I REALLY want to have my FreeFD ND TACAS display working for multiplayer.

Any help appreciated.  


best,

......................john