Unable to Connect With WideFS - DNS Issues ?

[garydpoole]

Hello 

For a very long time, I have had no issues connecting WideFS to FSUIPC running on my FSXSE server. However, for the last week or so, WideFS has been unable to connect.

Here is an exert from the WideClient log file:

********* WideClient Log [version 6.999y] Class=FS98MAIN *********
Date (dmy): 06/05/17, Time 14:57:03.378: Client name is BEDROOM4-1
      234 LUA: "C:\Program Files (x86)\FSX Addons\WideClient\Initial.LUA": not found
      265 Attempting to connect now
      281 Trying to locate server: Need details from Server Broadcast
      281 Failed to connect: waiting to try again
     2325 Attempting to connect now
    45162 Trying to locate server: Need details from Server Broadcast
   191835 Server = BEDROOM4-3
   191944 Trying TCP/IP host "BEDROOM4-3" port 8002 ...
   191944 ... Okay, IP Address = 92.242.132.16
   212957 Error on client pre-Connection Select() [Error=10060] Connection timed out
   212957 Ready to try connection again
   214985 Attempting to connect now
   214985 Giving up server, looking for another!
   214985 Server = BEDROOM4-3
   215016 Trying TCP/IP host "BEDROOM4-3" port 8002 ...
   215016 ... Okay, IP Address = 92.242.132.16
   238026 Server = BEDROOM4-3

I can see that the problem is obviously the "rogue" IP address of 92.242.132.16 being returned by FSUIPC. 

Firstly, let me stress that I know that this problem has nothing at all to do with WideFS or FSUIPC. I believe that the issue is related to my router and ISP - TalkTalk as I believe that this has something more to do with DNS Hacking ? For some reason, when asked by FSUIPC for my server's IP address, the router is returning 92.242.132.16, not the correct one.

Further investigations have shown this IP address to belong to an organisation named Barefruit Error Handling who have some affiliation with TalkTalk.

However, I'm now at a loss how, or if, I can overcome this problem ? I have read that sometimes, a new router is the only way ?

Any help or advise would be much appreciated !

Kind regards

Gary

 

[Luke Kolin]

DNS resolution is failing, and your router isn't implementing DNS properly. It's being "helpful" by returning an address that redirects to TalkTalk's error page:

http://error.talktalk.co.uk/main?ParticipantID=nmum6rqpq5q6gkm3933n3nf9s76onu6r&FailedURI=http%3A%2F%2F92.242.132.16%2F&FailureMode=1&Implementation=&AddInType=4&Version=pywr1.0&ClientLocation=uk

You probably need an entry in your hosts file, or use IP addresses to connect instead of host names. I run my own DNS for my 192.168.0.x addresses, but that's probably overkill for 99% of the population.

Cheers!

Luke

[garydpoole]

7 minutes ago, Luke Kolin said:

You probably need an entry in your hosts file, or use IP addresses to connect instead of host names. I run my own DNS for my 192.168.0.x addresses, but that's probably overkill for 99% of the population.

Cheers!

Luke

Hey Luke

Thanks for your fast response and explanation !

However, although I'm pretty PC-Savvi, I'm no network expert !

Please could you expand upon the above - what do you mean when you say, "entry in your hosts file" ?

Many thanks

Gary

[garydpoole]

OK, not wanting to speak too soon, but I think that I've solved the problem by changing the DNS server configurations within my router to use the openDNS servers instead of TalkTalk's.

So far, so good...

Kind regards

Gary