Newbie Alert Setup sequence sb3 & widefs

[Patrick Snyder 998078]

Apologies up front. i am in need of consulting services for setting up sb3 on a laptop linked to my sim machine running FS 2004 using a linksys wrt54gs. both are XP o/s and it appears I need widefs here. Currently reading the Vatsim 103g sb3 setup guide. Question is: In what order do I install sb3 and widefs? I did see an overview illustration on either Vatsim or Squawkbox. Like i have heard b4 "no one likes to read the flipping manuals" (guilty). Any one live in Connecticut USA? Thanks in advance, Pat Snyder

[Marcel Tjoeng 977157]

I use FSInn and is the better choice imo

but with SB3 do

1. FS9 box, FSUIPC.dll also WideServer.dll and .ini's, installs in /modules, run FS9 dropdownmenu, register Both, restart FS9

2. start WideClient.exe on the laptop, has to do 'connected', or chk .log (reconfig the faster protocol later) this has to work first.

3. SB3 (also FSInn). First install on FS9 box (has a choice menu, FSInn first instll Copilot, then FSInn) only installs the dll in /modules (FSInn will install wholly)

4. SB3 (also Copilot,FSInn) on the laptop, straight forward, connect with ID/P[Mod - Happy Thoughts], set up your plane and flightplan Squawk on Standby!

 

With WideFS working you can now run ActSky, FDC FSflightkeeper etc from the laptop.

 

FSInn looks complicated (and is) but you'll have Rain! (and radar, and lots of goodies)

For rain in SB3 disable Weather and use a weather prog on the laptop

[Patrick Snyder 998078]

Thanks Marcel, I have done parts 1,2 and 3 of your tutorial. I do have ActiveSky 6.5 and will move that and an additional Flt. Planner onto the laptop. I do believe that my connect issue to the desktop is firewall related or with the Portforwarding config on the WRT54GS router. I will keep the FSInn program in mind. Regards, Pat Snyder

[Lennart Vedin]

A router should not have any firewall protecting the local LAN side. (i.e. WideFS<>WideFS)

 

Since you do have a router with firewall for the WAN (internetconnection), make sure you have no software firewall in any PC (it is not required).

 

Disable uPnP in the router is just general recommended.

 

The order you install SB3/WideFS should not matter (if doubt i should install WideFS first). After install you must start FS/WideFS first , then start SB3.

 

WideFS must be installed at both machines.

[Lee Hetherington 822071]

What you state is not exactly true if your router also has WiFi. WiFi is on the LAN (behind the WAN firewall), so if rogue WiFi access is a possibility, your WAN firewall will be of no help.

[Lennart Vedin]

What you state is not exactly true if your router also has WiFi

Thanks a lot for some input in this matter.

 

Can you explain a few details more. There is always a firewall at WAN receiveing , isn't it ?

 

Is this "WiFi" a firewall protecting communication between two LAN connections ?

Is is only applicable for wireless ?

Can the LAN firewall be disabled somehow ?

[Guy Finney 997250]

The other problem with trusting the router to stop inbound attacks is that it does nothing to stop *outgoing* connections that you don't intend. If you pick up a virus/worm somewhere which makes outgoing connections from your PC, the inbound firewall won't stop it. This is the most common form of attack currently. The main reason we all get so much spam e-mail is because of the hordes of "zombie" computers worldwide. The malware installed on someone's PC makes an outgoing connection to the zombie master's server, which tells it what to do. Mostly it tells your PC to send e-mail, which will also not be stopped by your outward-facing firewall.

 

Everyone should run a firewall on every machine they have.

[Patrick Snyder 998078]

Lee and Lennart,

To clarify, I am using both machines on the lan as WiFi. Have Trend Micro's PC-Cillin suite and am utilizing the firewalls on both my laptop & desktop. I have set firewalls to "allow" sb3 thru the ports. I have disabled uPnP following Mark Brummett's July '06 tutorial. Had no issues installing either the FSUIPC & WideFS or sb3 as instructed. but sb3 does not see the running FS9. This is where I am in need of [Mod - Happy Thoughts]istance. Thanks, Pat Snyder

[Lennart Vedin]

OK. if WideFS running at the laptop and indicate connected to FS, and then SB3 at the laptop can not connect to FS, it is not a firewall issue.

Only the WideFS<>WideFS rely on TCP/IP connection.

 

SB3 must be installed at laptop with the option, something like: "running SB3 at on other PC".

 

SB3 connect to WideFS (same as when connect to FSUIPC) using "Memmory mapping", not using TCP/IP connection.

 

I do not have the solution, but SB3 do not connect to FSUIPC/WideFS by any TCP/IP ports.

 

 

You must manual start WideFS at the laptop and see that it indicate "Connected". If not WideFS "Connected", OK then it may be a firewall issue.

[Patrick Snyder 998078]

Lennart, The dialogue box that appears after opening the Wideclient and then SB3 says it "cannot establish a connection with a running copy of MSFS. MSFS must be running and the FSUIPC module must be installed in order for SB3 to operate", (both have been successfully accomplished) it is [Mod - Happy Thoughts]uming that either FS9 is not running or FSUIPC has a problem with the installation. I have not setup static IP addresses yet and that could be an issue. However I did read a thread that I will find again that suggested that Peter Dowson's latest version of FSUIPC that was registered had created problems for connecting. Gonna check his forum as well. Thanks for explaining the TCP/IP and /or UDP issue. Pat Snyder