FTP refusing connection

Home Forums MultiConnect OCG FTP refusing connection

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #4722
    Billy Ashmall
    Participant

    I have a snapConnect e10 linux box that I can ftp into when it is connected to the network by wire. I am now trying to instead connect to it by ftp through the MT100UCC-G2 GSM modem. The connection just gets refused. Being that the ftp works wired my guess is that there might be some configuration setting I need to tell the modem. Can you please help or point me in the right direction?

    Thanx,
    ~~~BillyZ

    #4723
    Lonny Knudson
    Blocked

    Hi Billy,
    I’m assuming that you are able to successfully establish a ppp link using the MT100UCC-G2. If this is correct could you issue the following commands to the linux box while the ppp link is up and post the output:
    ifconfig
    route

    If the above is not correct (you are not able to establish a ppp link using the MT100UCC-G2), then we would want to look at your chat script, peer file and any command line options you are using when you start ppp.

    #4724
    Billy Ashmall
    Participant

    eth0 Link encap:Ethernet HWaddr 00:1C:2C:5C:A0:BD
    inet addr:192.168.1.82 Bcast:192.168.1.255 Mask:255.255.255.0
    UP BROADCAST MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:1 dropped:0 overruns:0 frame:0
    TX packets:1 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:0 (0.0 B) TX bytes:322 (322.0 B)
    Interrupt:21 Base address:0x4000

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    UP LOOPBACK RUNNING MTU:16436 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

    ppp0 Link encap:Point-to-Point Protocol
    inet addr:10.34.58.140 P-t-P:192.168.111.111 Mask:255.255.255.255
    UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
    RX packets:3 errors:0 dropped:0 overruns:0 frame:0
    TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:3
    RX bytes:54 (54.0 B) TX bytes:69 (69.0 B)

    and:
    #route
    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use Iface
    default * 0.0.0.0 U 0 0 0 ppp0
    192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
    192.168.111.111 * 255.255.255.255 UH 0 0 0 ppp0

    #4725
    Lonny Knudson
    Blocked

    Hi Billy,
    It looks like the cellular provider is assigning your mobile device a private IP address. Addresses in the 10.x.x.x range are not accessible from the internet. I would recommend consulting your cellular provider and telling them that you need to support a mobile terminated data application and see if they can assign your device a public IP address or provide you with a VPN connection that would allow access to the private IP.

Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.