Hi, all.First, allow me to say that I am not new to squawkbox. I was on-line with this in 2000. However, I've been away for several years, my equipment and software is relatively current, and I'm in the process of moving to high speed internet via D-Link cable modem and a D-Link router with a direct attach to my primary pc on a lan. My initial attachment was via a D-Link wireless adapter, but I could never get good, quality reception for connection to the internet.I can't figure where or what is causing my problem. I have taken the time to read most of the posts here on squawkbox issues, but have not been able to find anyone else that has experienced the same problem.I am running windows xp home edition on a 2.4g pentium 4. SP2 was installed via auto update a couple weeks ago. Did a file search for directx 9.0 on this system and it is not there. Have disabled the windows firewall. Have disabled Norton's Internet Security firewall.And I understand that the DLink router has its own firewall that I can't seem to locate. I am also still running fs2002 versus fs2004. You might say that I'm just a little stubborn in that regard, but I'm still pleased with fs2002 and haven't seen the benefit of making the change. So SBrelay is not part of this problem.I've followed two tutorials that have pretty much taken me to the same place - connect! I've followed advise from several of you reference the route/steps to take to get through the process; to no avail. The steps I've followed:1. ISP is always on.2. Activate FS20023. Select aircraft & flight4. Select Alt-key to access the menu bar in full screen mode5. Select File-Multiplayer-connect6. In the dialogue box, enter aircaft callsign-choose tcp/ip-press the host button7. Enter session name-set number of players-click ok8. Select Alt-Tab key to return to pc desktop9. Click start-programs-squawkbox for FS2002 and select SB HOST for 200210. Click start-programs-squawbox for FS2002 and select SB MAIN PROGRAM..Right click in the squawkbox window for the drop down menu.Select FMS, highlight the plan you want to submit, and click ok.Right click in the squawkbox window again and click connect.Check all info on menu is accurate and hit the ok button.IT IS AT THIS POINT WHERE THE SYSTEM DELAYS FOR APPROXIMATELY 30 SECONDS AND THEN RETURNS AN ERROR MESSAGE - "WSAETIMEDOUT" 'Attempt to connect timed out without establishing a connection'.I am then at the end of the line.Thanks for reading all this, and any assistance would be welcomed.Burdette

> And I understand that the DLink router has its own firewall> that I can't seem to locate. I don't know anything about your detailed issues, and I use FS2004.However as I understand, if you have a router you must open requiredports in that router or you will fail.Sometime named "virtual server" in router-menu.What type of DLink router do you have ?Lennart Vedin SAS202

>> And I understand that the DLink router has its own>firewall>> that I can't seem to locate. >>I don't know anything about your detailed issues, and I use>FS2004.>>However as I understand, if you have a router you must open>required>ports in that router or you will fail.>Sometime named "virtual server" in router-menu.>>What type of DLink router do you have ?>Lennart Vedin SAS202It is an Airplus Xtreme G, Model DI-624 Wireless.Burdette

> It is an Airplus Xtreme G, Model DI-624 Wireless.My D-LINK DI-604 not wireless, could be similar.I locate D-LINK DI-604 from any computer at the LAN,using a web-reader enter the router's address 192.168.0.1If doubt check http://www.dlink.com/Default login is user=admin and password=If default login is changed, the D-LINK can be complete reset as from factory by reset-hole using pencil.Just note you will reset ALL setting to default.The rest conserning settings se previous topic:"Router D-LINK DI-604 setting. Oct-04-04 06:17 AM"Lennart Vedin SAS202

I have a Dlink DI-624 router at home, what PORTS need to be opened to use the full SquawkBox with AVC voice?

Se next new topic "Router D-LINK DI-604 setting." this forum.I added a message to this old topic.

I don't think its your router.with that error its most likely the server you are trying to connect to is no longer there.Go to your SB folder and find the fileipaddr.txt and open itDelete everything in it and paste this in its place152.104.96.225 ASIA-S200.223.140.250 BRAZIL-C137.56.244.9 EUROPE-C212.47.22.26 EUROPE-CE212.112.234.46 EUROPE-CW195.205.20.162 EUROPE-E1195.78.48.15 EUROPE-E2212.205.81.22 EUROPE-SE210.15.254.125 OCEANIA213.194.111.99 TURKEY80.249.98.88 UK-166.98.168.65 USA-S166.221.192.84 USA-S3208.224.174.24 USA-SE216.93.170.44 USA-WThat should fix you right up

>I don't think its your router.>>with that error its most likely the server you are trying to>connect to is no longer there.>>Go to your SB folder and find the file>>ipaddr.txt and open it>>Delete everything in it and paste this in its place>>152.104.96.225 ASIA-S>200.223.140.250 BRAZIL-C>137.56.244.9 EUROPE-C>212.47.22.26 EUROPE-CE>212.112.234.46 EUROPE-CW>195.205.20.162 EUROPE-E1>195.78.48.15 EUROPE-E2>212.205.81.22 EUROPE-SE>210.15.254.125 OCEANIA>213.194.111.99 TURKEY>80.249.98.88 UK-1>66.98.168.65 USA-S1>66.221.192.84 USA-S3>208.224.174.24 USA-SE>216.93.170.44 USA-W>>That should fix you right upThanks for the responses, gentlemen.I am trying all suggestions from you both. And so far, still no success. I've changed settings on the router in every combination possible. It is a bit strange - set up a virtual server alone and it doesn't work. set up a virtual server and firewall config allowing access and it doesn't work. Firewall config shows but not accessible. Disable the virtual server and the firewall config goes away....etc.By the way, after each config chance, restarted the router. And Dave, thanks for the server list. However, I am currently using the usa-se 208.224.174.124 server and getting the same result.Will keep trying.Burdette

> I am currently using the usa-se 208.224.174.124 serverIt's 208.224.174.24By the way "Virtual Server" is a firewall.It's just an other name just to confuse us users(!)"Firewall" in DI-604 is an alternative more detailed firewallthan "Virtual Server".That's why you expere it strange.You shouldn't need "Firewall" in DI-604.Lennart Vedin SAS202

I may be able to shed a little light on where turn off your D-Link firewall. It is on your setup page at 192.168.1.1. As regards the est, I am more lost than you are.:)

A similar model of D-Link "Modem" use default address 192.168.1.1But the D-Link "Router" DI-604 use default address 192.168.0.1Lennart Vedin SAS202

>> I am currently using the usa-se 208.224.174.124 server>It's 208.224.174.24>>By the way "Virtual Server" is a firewall.>It's just an other name just to confuse us users(!)>"Firewall" in DI-604 is an alternative more detailed firewall>than "Virtual Server".>That's why you expere it strange.>>You shouldn't need "Firewall" in DI-604.>>Lennart Vedin SAS202I'M IN!!!! THE CONNECTION PROBLEM IS SOLVED!!!! Thanks to Lennart the router settings were changed to configure a Virtual Server: Disabled Name Squawkbox Server HTTP Private IP 192.168.0.100 Protocal Type Both Private Port 6809 Public Port 6809 Schedule AlwaysApplications: Enabled Name Squawkbox and RW (Roger Wilco) Trigger Port 6809 Trigger Type Both Public Port 6809,1900,6073,2345,3290 Public Type BothFirewall: Rules can be used to ALLOW or DENY traffic from passing through the DI-624 Enabled Name Squawkbox Server Action Allow Interface IP Range IP Range Protocal Port Range Start End Source WAN * Destination LAN 192.168.0.100 TCP 10 20 Schedule AlwaysThis rule generated 4 firewall configs with different protocols. Don't know what that means, but it works!Thought I would share these configs in case someone else can use the visual reference.Thanks to both Dave and Lennart, I finally got the right server number in place. As you could tell from my response to Dave, I had put too many numbers in the last section.When that number was in and I hit the connect button, the response I got suggested that my password may be wrong. So I checked through vatsim lost password, got a return email with a new password, tried connecting again, and walla..... it worked.So thanks a million. You have no idea how many days I struggled with this issue. And after all this, don't know that we can really blame the D-Link 624 router at all. It is performing very well right now.Burdette