Page 2 - Ftp Econnrefused

Yeah, that was my call and yeah, that was the result. Got a "
Unable to make a connection. Please try again." error message.



I just need to figure out how to capture the result so I can give it to you . . .

HeadElf

Right Click -> Select All
Press Enter
Paste into new post.

Active Connections

Proto Local Address Foreign Address State
TCP elfhobbit:epmap elfhobbit:0 LISTENING
TCP elfhobbit:microsoft-ds elfhobbit:0 LISTENING
TCP elfhobbit:2869 elfhobbit:0 LISTENING
TCP elfhobbit:1026 elfhobbit:0 LISTENING
TCP elfhobbit:2394 localhost:2395 ESTABLISHED
TCP elfhobbit:2395 localhost:2394 ESTABLISHED
TCP elfhobbit:2397 localhost:2398 ESTABLISHED
TCP elfhobbit:2398 localhost:2397 ESTABLISHED
TCP elfhobbit:2421 localhost:10080 ESTABLISHED
TCP elfhobbit:2493 localhost:10080 ESTABLISHED
TCP elfhobbit:2494 localhost:10080 ESTABLISHED
TCP elfhobbit:2495 localhost:10080 ESTABLISHED
TCP elfhobbit:2497 localhost:10080 ESTABLISHED
TCP elfhobbit:2699 localhost:10080 TIME_WAIT
TCP elfhobbit:2711 localhost:10080 TIME_WAIT
TCP elfhobbit:2725 localhost:10080 TIME_WAIT
TCP elfhobbit:5152 elfhobbit:0 LISTENING
TCP elfhobbit:5152 localhost:2396 CLOSE_WAIT
TCP elfhobbit:9999 elfhobbit:0 LISTENING
TCP elfhobbit:10080 elfhobbit:0 LISTENING
TCP elfhobbit:10080 localhost:2421 ESTABLISHED
TCP elfhobbit:10080 localhost:2493 ESTABLISHED
TCP elfhobbit:10080 localhost:2494 ESTABLISHED
TCP elfhobbit:10080 localhost:2495 ESTABLISHED
TCP elfhobbit:10080 localhost:2497 ESTABLISHED
TCP elfhobbit:10080 localhost:2608 TIME_WAIT
TCP elfhobbit:10080 localhost:2697 TIME_WAIT
TCP elfhobbit:10080 localhost:2699 TIME_WAIT
TCP elfhobbit:10080 localhost:2701 TIME_WAIT
TCP elfhobbit:10080 localhost:2703 TIME_WAIT
TCP elfhobbit:10080 localhost:2705 TIME_WAIT
TCP elfhobbit:10080 localhost:2707 TIME_WAIT
TCP elfhobbit:10080 localhost:2709 TIME_WAIT
TCP elfhobbit:10080 localhost:2713 TIME_WAIT
TCP elfhobbit:10080 localhost:2715 TIME_WAIT
TCP elfhobbit:10080 localhost:2717 TIME_WAIT
TCP elfhobbit:10080 localhost:2719 TIME_WAIT
TCP elfhobbit:10080 localhost:2721 TIME_WAIT
TCP elfhobbit:10080 localhost:2723 TIME_WAIT
TCP elfhobbit:10080 localhost:2727 TIME_WAIT
TCP elfhobbit:10110 elfhobbit:0 LISTENING
TCP elfhobbit:13128 elfhobbit:0 LISTENING
TCP elfhobbit:18080 elfhobbit:0 LISTENING
TCP elfhobbit:netbios-ssn elfhobbit:0 LISTENING
TCP elfhobbit:2422 pv-in-f100.google.com:http ESTABLISHED
TCP elfhobbit:2496 a210-9-88-58.deploy.akamaitechnologies.com:http ESTABLISHED
TCP elfhobbit:2498 a210-9-88-58.deploy.akamaitechnologies.com:http ESTABLISHED
TCP elfhobbit:2499 a210-9-88-58.deploy.akamaitechnologies.com:http ESTABLISHED
TCP elfhobbit:2500 a210-9-88-58.deploy.akamaitechnologies.com:http ESTABLISHED
TCP elfhobbit:2712 216.36.248.30:http TIME_WAIT
TCP elfhobbit:2726 beacon.or3.scorecardresearch.com:http TIME_WAIT
UDP elfhobbit:microsoft-ds *:*
UDP elfhobbit:isakmp *:*
UDP elfhobbit:1027 *:*
UDP elfhobbit:4500 *:*
UDP elfhobbit:ntp *:*
UDP elfhobbit:1028 *:*
UDP elfhobbit:1900 *:*
UDP elfhobbit:ntp *:*
UDP elfhobbit:netbios-ns *:*
UDP elfhobbit:netbios-dgm *:*
UDP elfhobbit:1900 *:*
UDP elfhobbit:domain *:*
UDP elfhobbit:bootps *:*
UDP elfhobbit:bootpc *:*

Hope this helps.

HeadElf

Well, it helps in that I know another thing that isn't causing the problem.

Are you able to hook the usb modem up to your laptop and get an internet connection on it? If so, try using FTP from your laptop.

If that, my next plan would be to use a linux live cd and attempt to use the built in ftp client. I'm not totally sure if I can walk you through that over a forum.

I'm curious about your zonealarm settings. Did you open specific ports, or just allow the application? Are you able to totally disable zone alarm and attempt an ftp connection? (do so at your own risk)

<wince> I SO don't want to go there . . . and I now have ftp access. Don't frown at me. I cannot tell you what I did that worked. I am still clueless. I did lots of things, I rebooted lots of times . . . I'm feeling REALLY blonde about this.

Now if I can get the file sharing and wireless broadband connection working I'll be impressed with myself . . . still clueless but impressed none-the-less.

HeadElf

Well, let's go back to my original question. I asked about pinging two different IPs, one from the laptop and one from the desktop.

If the pings work, it's simply a matter of bridging network connections.

why don't we try the simplest of FTP type connections:

Open a command prompt and type in "ftp 12.123.124.57" or whatever the IP address is (too lazy to go back up and look) and see what happens there. remove the client, just do a straight command-line FTP hookup

If I were to run ipconfig /all, which IP address would I use to ping from the desktop. Ditto on the laptop.

?

HeadElf

Okay, I think I've figured that out. From the desktop I ping 192.168.10.102. That's the IP addy for the laptop and it works. It hits the laptop and I get productive results.

When I ping from the laptop to the desktop (ping 192.168.10.101) I get a series of timed outs. I'm not getting the desktop from the laptop. Am I doing something wrong or <BIG wince> is it settings?

I guess you'd better tell me what the heck "bridging" is.

HeadElf

Can you please post the output of "ipconfig /all" from both the laptop and the desktop?

No point...problem already solved
This could have been done instead of trying ftp in firefox, but I figured once we had tried two clients that the problem was most likely not an ftp client issue.

I know I wasn't very clear in my "I can ftp" post. I installed the newest version of FZ, couldn't connect, did some more research, made a non-change to my registry, played with some more stuff, messed with the router and then I could connect.

Now I can ping my laptop from my desktop but not my desktop from my laptop. Any idea where to turn here? My laptop sees the wireless router and says it's connected with excellent strength, but I can't ping the desktop.

HeadElf

See post #25.

Desktop:

Windows IP Configuration
Host Name . . . . . . . . . . . . : elfhobbit
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8168B/8111B Family PCI-E GBE NIC
Physical Address. . . . . . . . . : 00-1D-7D-D4-CD-52
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.10.101
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.10.1
DHCP Server . . . . . . . . . . . : 192.168.10.1
DNS Servers . . . . . . . . . . . : 192.168.10.1
Lease Obtained. . . . . . . . . . : Saturday, June 20, 2009 9:15:38 AM
Lease Expires . . . . . . . . . . : Saturday, June 27, 2009 9:15:38 AM

PPP adapter Sprint Mobile Broadband - Novatel Wireless:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 173.127.16.177
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 173.127.16.177
DNS Servers . . . . . . . . . . . : 68.28.50.91
68.28.58.92

Laptop:

Windows IP Configuration

Host Name . . . . . . . . . . . . : LAPTOP
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:
Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
Physical Address. . . . . . . . . : 00-16-36-0B-A1-E6

Ethernet adapter Wireless Network Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/Wireless 2915ABG Network Connection
Physical Address. . . . . . . . . : 00-13-CE-B5-A6-E5
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.10.104
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.10.1
DHCP Server . . . . . . . . . . . : 192.168.10.1
DNS Servers . . . . . . . . . . . : 192.168.10.1
Lease Obtained. . . . . . . . . . : Saturday, June 20, 2009 11:29:46 AM
Lease Expires . . . . . . . . . . : Saturday, June 27, 2009 11:29:46 AM

Ethernet adapter Local Area Connection 2:
Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Bluetooth LAN Access Server Driver
Physical Address. . . . . . . . . : 00-14-A4-DE-C7-E8

HeadElf

Zonealarm by default will not allow your desktop to respond to ping.

From here : *Replace 131.111.12.0 with 192.168.10.0*

To allow a response to ping from the Trusted Subnet 131.111.12.0/24:
Version 3 of ZoneAlarm

* Double-click the ZoneAlarm icon in the System Tray
* Click on Firewall in the left-hand toolbar area
Click on the Zones tab in the top right of the dialogue box. You should see your own computer's IP Address listed as in the Trusted Zone. You need the following as well...
* Click on Add>> button and select Subnet
* In the Local Zone Properties dialogue box, click Add >>, Subnet...
* In the Trusted Zone specify:
*
o IP Address 131.111.12.0
o Subnet Mask 255.255.255.0
o Description CS Trusted
* Click OK

It is suggested that you then also add the Computing Service internal network. 131.111.10.0/23. If you choose to do so:

* Click Add >>, Subnet
* In the Trusted Zone specify
*
o IP Address 131.111.10.0
o Subnet Mask 255.255.254.0
o Description CS Internal
* Click OK

Then finish off:

* Click Apply to reconfigure ZoneAlarm
* Exit ZoneAlarm but leave it running.


Then re-attempt pinging.