WideFS tips: XPSP3, TrendMicro, wireless N, windows firewall

[BillfromLosAngeles]

This is an outrageously good program and it works perfectly. But, here's what I learned over a couple of hours. I am not sure if all of this is MANDATORY, but this is what seems to work. (Less stringent measures may work, but for now....)

1. I (think I) needed to specify a name for the FSX computer and tcp Protocol.

2. I needed to abandon my wireless N-protocol ROUTER, as there were mini "drops" here and there and that made trouble shooting too hard ("No network service" followed by "Network connected" a couple of seconds later. I had to use ethernet hard wire . (One wire from the router in kitchen with a switch in the computer room.)

3. I had to completely TURN OFF TrendMicro virus/firewall (I am not sure if they sell this in Europe, but if they don't they should...). Pete alludes to this when he says that turning the front end doesn't necessarily work. (THIS MAY HAVE BEEN THE MOST IMPORTANT......)

4. Then I had to manually ALSO TURN OFF the windows firewall from the Control Panel (THIS SEEMS TO COME ON WHEN U TURN OFF THE TREND MICRO)

5. I shared ALL OF C: TO START, but now that it is running, I will see if I can get away with just sharing FSX folder. (In fact, if WideClient just polls the FSX, then I suppose I might not have to share anything? I am a little iffy about sharing my C with the firewalls off.... Pete, do I have to share anything?

THANX PETE FOR A PHENOMENAL JOB!

[Pete Dowson]

1. I (think I) needed to specify a name for the FSX computer and tcp Protocol.

You do if the broadcasting isn't getting through. That needs both PCs running WinXP or later, and both to be in the same named workgroup.

2. I needed to abandon my wireless N-protocol ROUTER, as there were mini "drops" here and there and that made trouble shooting too hard ("No network service" followed by "Network connected" a couple of seconds later. I had to use ethernet hard wire . (One wire from the router in kitchen with a switch in the computer room.)

Wireless routers are general pretty good these days, but if they are used in a room with lots of metal and electrical equipment (like a kitchen!) they can prove problematic. I need two access points in my house because of thick walls made with some sort of old fashioned brick which seems as hard as metal!

3. I had to completely TURN OFF TrendMicro virus/firewall (I am not sure if they sell this in Europe, but if they don't they should...). Pete alludes to this when he says that turning the front end doesn't necessarily work. (THIS MAY HAVE BEEN THE MOST IMPORTANT......)

Well i don't use firewalls BETWEEN my PCs -- I have a good setup on my ADSL modem/router. But you certainly should simply be able to give permissions -- FS and WideClient, ports 8002 and 9002.

5. I shared ALL OF C: TO START, but now that it is running, I will see if I can get away with just sharing FSX folder. (In fact, if WideClient just polls the FSX, then I suppose I might not have to share anything? I am a little iffy about sharing my C with the firewalls off.... Pete, do I have to share anything?

Nothing at all as far as WideFs is concerned. It isn't a disk access program, it sends data only by Ethernet. However, some programs you run on the clients may want to read or even write data on the Server. That's something you have to find out from the application documents. Typical things are scenery file access for planners building databases, flight and Plan files folder access for planners and other programs which need to read plans, etc.

Regards

Pete