Problems Connecting to an address using WAG310G.

Forums › LAN (ethernet/Wifi/routers/Bluetooth) › Problems Connecting to an address using WAG310G.

gotteem

9 posts

Wannabe Geek

#111968 21-Nov-2012 10:12

I am getting the following error message when I try to connect to an address: X-STUDY cannot connect to FDMS: FDMS 250 at 12.41.48.47:10250. I have a cisco WAG310G and IP is x-net. Have had TT who own X-Study (which is an app inside of X-Trader) log onto my comp and they reckon its a port issue. Xnet reckon they dont know. I blindly have tried port forwarding but dont really know what to do. I have included the error message and my cisco port forwarding screen

ubergeeknz

3344 posts

Uber Geek

Trusted

Vocus

#720635 21-Nov-2012 10:47

You shouldn't need port forwarding to connect out to an external application.

Obvious Question: Is that application meant to be accessible from the public Internet?

If so:

Can you ping that address?

Post up the results of a traceroute to it? (use a command prompt > type "tracert 12.41.48.47")

Can you telnet to that address/port? ("telnet 12.41.48.47 10250" from command line) What happens?

Tried disabling Windows Firewall (or allowing your application)?

gotteem

9 posts

Wannabe Geek

#720865 21-Nov-2012 16:41

Thanks for your help.

"Is that application meant to be accessible from the public Internet?" I guess yes. We have to pay a subscription, and the other guys can access it no worries. I have even logged on at their place using my logon. They havent had to modify any settings apart from firewall.

"Disable windows firewall". Basically yes. I had to change these settings on the firewall: User Account Control (UAC) must be disabled
The Base Filtering Engine (BFE) Windows Service must be disabled.

"Can you ping that address?" :

"Post up the results of a traceroute to it? (use a command prompt > type "tracert 12.41.48.47")":

"Can you telnet to that address/port?":

gotteem

9 posts

Wannabe Geek

#720868 21-Nov-2012 16:44

Sorry.

Telnet image meant to be:

ubergeeknz

3344 posts

Uber Geek

Trusted

Vocus

#720877 21-Nov-2012 16:55

Destination Net Unreachable coming back from one of the hops on your route is Not A Good Sign (TM)

Is the IP address definitely correct? If it's even configurable.

If you're sure, then send the results of your tracert to your ISP to have a look.

gotteem

9 posts

Wannabe Geek

#720887 21-Nov-2012 17:15

Well only have that address because its being sent back to me on that error message. You have me wondering if maybe I shouldnt believe it.

ubergeeknz

3344 posts

Uber Geek

Trusted

Vocus

#721206 22-Nov-2012 10:58

True; maybe install wireshark, get a network capture, and we can see for sure what the application is trying to connect to.

gotteem

9 posts

Wannabe Geek

#721436 22-Nov-2012 16:32

Ok, but before I do, I have confirmed that this is the correct address. Also, we did a tracert on my friends computer that can get x-study, and he got the same reply as I did ie destination net unreachable. So even though the application works on his comp, the tracert didnt connect. Apparently the address is in chicago.

ubergeeknz

3344 posts

Uber Geek

Trusted

Vocus

#721439 22-Nov-2012 16:43

Well I can't see why you're unable to connect then, if the tracert error is indeed a red herring.

Is the last hop the same on your friend's tracert?

You may need to go back to your ISP, if the guys running x-study can't see what's wrong... it's certainly a bit weird.

gotteem

9 posts

Wannabe Geek

#721447 22-Nov-2012 17:09

Installed wireshark but cant get it to run

gotteem

9 posts

Wannabe Geek

#721703 23-Nov-2012 09:49

Interestly, the route taken for our connection is completely different.

Heres my friends tracert:

I dont know if this means anything to you?

ubergeeknz

3344 posts

Uber Geek

Trusted

Vocus

#721708 23-Nov-2012 09:56

gotteem: Interestly, the route taken for our connection is completely different.

Heres my friends tracert:

I dont know if this means anything to you?

Not really, he's with a different ISP so a different route is to be expected. As you can see TCL are using TelstraGlobal to do their international routing to the US. We use our own Odyssey network so it would be different again.

Do you have another computer and/or router you can try?

gotteem

9 posts

Wannabe Geek

#721796 23-Nov-2012 11:53

I have just tried a different router...same problem.

My friend has suggested coming over with his computer one day so we shall see. I talked to xnet and emailed them the tracert, and they are looking into it.