WideFS Connection

[elsmoko]

Hi Pete,

I'm trying to connect a new Win Vista 32 laptop to my Win 7-64 PC with latest (registered) versions

of FSUIPC (with integrated WideServer) on the PC; and Wide Client on the laptop. Firewalls are

disabled all around and I've tried opening port 8002 via the DLink DLR-825 wireless router's web based

interface; however I don't know if I am doing this properly. I have attached a zipfile to this message

that includes the latest WideClient logfile, and also a screen capture of my attempt to open port 8002.

Any advice will certainly be appreciated.

Best regards,

Ken Boardman

WideFS_1.zip

[Pete Dowson]

I have attached a zipfile to this message that includes the latest WideClient logfile

The problem is the IP address being supplied for your Server:

795 Trying TCP/IP host "KENS-PC" port 8002 ...

795 ... Okay, IP Address = 208.67.216.145

This is NOT a local network address, but appears to be your ISP:

IP: 208.67.216.145

Decimal: 3494107281

ISP: OpenDNS, LLC

Organization: OpenDNS, LLC

Country: United States

State/Region: Washington

City: Seattle

I think this happens because of some weird setting on your router. But please see the FAQ subforum thread entitled

WideFS Server names translating into incorrect IP addresses

Regards

Pete

[elsmoko]

Thank you for pointing me in the right direction Pete. As you can

see below, Wide Client is now connecting. I read all the docs that

you recommended, then beat up my router (settings) and experimented

with varied combinations of Protocol=, ServerIPAdd=, and ServerName=

settings in the WideClient.ini file. As you can see, the Protocol and

ServerIPAdd settings did the trick, and as unlikely as it may seem,

the operation appears to recognize the difference between 192.168.0.1

and 192.168.0.10. Won't connect using 192.168.0.1. Seems very strange

to me; but then I'm a bit awkward at this mysterious networking stuff ~:)

Now, lets see if some of those FSX utility add-ons will connect from the

laptop. I use FS Flightkeeper, ASE, Radar Contact V4 and FS Commander.

May also try Servinfo and other VATSIM pograms, although I believe

Squawkbox must run on the FSX PC. Please correct me if I'm wrong.....

Thanks for all that you do for us.

Ken Boardman

********* WideClient Log [version 6.86] Class=FS98MAIN *********

Date (dmy): 30/01/12, Time 18:57:58.127: Client name is WIDEFS1

124 LUA: "C:\WideFS\Initial.LUA": not found

140 Attempting to connect now

140 Trying TCP/IP addr 192.168.0.10, port 8002 ...

140 Connection made okay!

12105 Lost contact with ASE WX requester

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>><<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

My WideClient.ini file contents :

; PLEASE SEE WideFS documentation for parameter details

; =====================================================

[Config]

Port=8002

Window=195,157,886,589

Visible=Yes

ButtonScanInterval=20

ClassInstance=0

NetworkTiming=5,1

MailslotTiming=2000,1000

PollInterval=2000

Port2=9002

ResponseTime=18

ApplicationDelay=0

TCPcoalesce=No

WaitForNewData=500

MaxSendQ=100

OnMaxSendQ=Log

NewSendScanTime=50

Priority=3,1,2

Protocol=TCP

ServerIPAddr=192.168.0.10

; -----------------------------------------------

[user]

Log=Errors+

; ===============================================

[sounds]

Path=C:\WideFS\Sound\

Device1=Primary Sound Driver

Device2=Speakers / Headphones (SigmaTel High Definition Audio CODEC)

Device3=HDMI (SigmaTel High Definition Audio CODEC)

[Pete Dowson]

... as unlikely as it may seem, the operation appears to recognize the difference between 192.168.0.1

and 192.168.0.10. Won't connect using 192.168.0.1. Seems very strange

to me

If your Server is 192.168.0.10, as appears to be the case, then of course it won't connect using 1 instead of 10 -- they are two different numbers (10 being 9 more than 1).

Regards

Pete

[elsmoko]

Thank you for putting that in proper perspective Pete. I was thinking .1 = .10 = .1000000 etc. But now I understand that we are just dealing

with whole #s separated by periods ~:)

Best regards,

Ken

[Ian P]

When thinking of IP Addresses, it's usually best to remember that they are actually all numbered from 0 to 255, so although you may see, say, "192.168.0.1" and "192.168.0.10", they are actually "192.168.000.001" and "192.168.000.010" - Windows removes the extra leading zeroes, which can sometimes be useful and other times (such as this) a pain.

Cheers,

Ian P.

[Pete Dowson]

Thank you for putting that in proper perspective Pete. I was thinking .1 = .10 = .1000000 etc. But now I understand that we are just dealing

with whole #s separated by periods ~ :)

Yes. In fact each number is one byte of 8 bits, so has a value of 0 to 255 as Ian has pointed out. The whole IP address is therefore 32 bits. The representation as 4 numbers is only a convention.

This is only for IPv4 -- the newer IPv6, introduced to allow a far greater expansion in the number of addresses, uses more -- 128 bits, or 16 bytes. They changed the way they are written to groups of hexadecimal digits instead of decimal ones, and use colons instead of points, for example:2001:0db8:85a3:0000:0000:8a2e:0370:7334.

Regards

Pete

[elsmoko]

Pete and Ian,

Thank you again for the IP Address enlightenment. Last time I ran ipconfig I noticed results that included IPv6 followed by hex digits

and then scratched my head for a moment. Seems that the FS programs I'm interested in connecting via network mostly still

using IPv4. Looks like I'll need to start writing stuff down. I have enough trouble just remembering the decimal addresses LOL!!

Best Regards,

Ken

As a side note, also got Simconnect client connected on the laptop last night >> so now I'm all dressed up with nowhere to go" (need to install

some FS programs on laptop ~:)

[Pete Dowson]

Thank you again for the IP Address enlightenment. Last time I ran ipconfig I noticed results that included IPv6 followed by hex digits

and then scratched my head for a moment. Seems that the FS programs I'm interested in connecting via network mostly still

using IPv4.

Yes. I've not yet met any direct use of IPv6. I think some of it is hidden behind aliasses in order to maintain compatibility with older programs and settings. I doubt if it really will ever see use for local IP addresses in a local network, as there are ample for local use in IPv4 -- they can be the same on every separate local network as those IP addresses aren't used over the 'net.

Regards

Pete