Unable to connect

Kilo.Dollar · 10-13-2006, 08:03 AM

Background.
I attempetd to install Spam Fighter. During the installation it asked to be allowed open ports for access to Bayesian database, or something to that effect. Before, I was able to connect onto P2P networks using Limewire and Soulseek etc.
After this attempt, Spam Fighter froze, forcing me to restart my machine. Then, I could not connect to my P2P friends.
After struggling for a week, I ended up reinstalling XP anew, and now I'm not sure how I can "renew" my love affair with P2P connections.
I've had my IP settings set back to what they were before but still cannot connect. Firewall (XP) is disabled, current max concurrent half-open connections set @ 10,000,000.
Anyone with assistance would be appreciated.

Will.Spencer · 10-15-2006, 09:11 AM

This is very odd. Installing a fresh copy of Windows XP should have cleared away any bad stuff that was plaguing your system.

What error messages are you receiving from Limewire and Soulseek?

Have you tried eMule? It's the one I am most familiar with, so troubleshooting it will be easier.

Kilo.Dollar · 10-17-2006, 04:28 AM

This is the error message I am getting from Emule

"Starting TCP connection test...
TCP test failed! UDP test will not be performed.

Connection test finished. "

This is despite the fact that I have manually opened the requested ports as per the online help page.

I followed your help in the "mirc ports blocked blog". Here are some snapshots from my PC.

Z:\>tracert 194.68.45.50

Tracing route to 194.68.45.50 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 172.20.11.1
2 20 ms 8 ms 23 ms gw123.93.idm.co.zw [217.15.123.93]
3 12 ms 12 ms 12 ms net117-120.wvale-glendale.ecoweb.co.zw [217.15.1
20.117]
4 18 ms 15 ms 44 ms gw.hre-wvale.ecoweb.co.zw [217.15.120.105]
5 29 ms 40 ms 18 ms 217.15.112.61
6 581 ms 595 ms 575 ms 217.15.112.57
7 583 ms 587 ms 580 ms unknown.net.reach.com [134.159.95.37]
8 574 ms 588 ms 583 ms i-4-0.ldn-core1.net.reach.com [202.40.148.17]
9 589 ms 588 ms 575 ms i-1-2.lnx01.net.reach.com [202.84.140.58]
10 655 ms 653 ms 662 ms i-11-0.nwk-core01.net.reach.com [202.84.140.45]

11 658 ms 672 ms 658 ms i-9-0-0.nwk01.net.reach.com [202.40.148.118]
12 * * * Request timed out.
13 669 ms 651 ms 680 ms 0.ge-3-0-0.gbr1.nwr.nac.net [209.123.11.174]
14 694 ms 663 ms 651 ms 0.so-7-3-0.gbr2.oct.nac.net [209.123.11.58]
15 706 ms 791 ms 720 ms 0.ge-0-0-0.gbr1.oct.nac.net [209.123.11.49]
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Z:\>netstat -nr

Route Table
================================================== =========================
Interface List
0x1 ........................... MS TCP Loopback interface
0x20002 ...00 0b db 6c ee e1 ...... Intel(R) PRO/1000 MT Network Connection - Pa
cket Scheduler Miniport
================================================== =========================
================================================== =========================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 172.20.11.1 172.20.11.168 10
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
172.20.11.0 255.255.255.0 172.20.11.168 172.20.11.168 10
172.20.11.168 255.255.255.255 127.0.0.1 127.0.0.1 10
172.20.255.255 255.255.255.255 172.20.11.168 172.20.11.168 10
224.0.0.0 240.0.0.0 172.20.11.168 172.20.11.168 10
255.255.255.255 255.255.255.255 172.20.11.168 172.20.11.168 1
Default Gateway: 172.20.11.1
================================================== =========================
Persistent Routes:
None

Z:\>tracert www.rapidshare.de

Tracing route to www.rapidshare.de [130.117.156.24]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 172.20.11.1
2 9 ms 9 ms 9 ms gw123.93.idm.co.zw [217.15.123.93]
3 13 ms 11 ms 13 ms net117-120.wvale-glendale.ecoweb.co.zw [217.15.1
20.117]
4 12 ms 25 ms 18 ms gw.hre-wvale.ecoweb.co.zw [217.15.120.105]
5 21 ms 30 ms 27 ms 217.15.112.61
6 595 ms 594 ms 580 ms 217.15.112.57
7 780 ms 710 ms 924 ms s2-2.EWN-RO1-LAG.worldstream.com [217.15.112.6]

8 577 ms 599 ms 577 ms fa8-0-0.ECO-RO1-LON.worldstream.com [217.15.112.
105]
9 581 ms 587 ms 590 ms y-s-2.lon1.arbinet.net [213.232.64.76]
10 607 ms 590 ms 592 ms ae-19-53.ebr1.London1.Level3.net [4.68.116.94]
11 581 ms 591 ms 606 ms ae-1-100.ebr2.London1.Level3.net [4.69.132.118]

12 672 ms 654 ms 661 ms ae-4.ebr1.NewYork1.Level3.net [4.69.132.109]
13 645 ms 663 ms 647 ms ae-11-53.car1.NewYork1.Level3.net [4.68.97.84]
14 645 ms 647 ms 640 ms cogent-level3-ge.NewYork1.Level3.net [4.68.111.4
2]
15 686 ms 653 ms 673 ms p15-0.core02.jfk02.atlas.cogentco.com [66.28.4.1
4]
16 753 ms 719 ms 726 ms p2-0.core01.lon01.atlas.cogentco.com [66.28.4.19
0]
17 743 ms 735 ms 749 ms p15-0.core01.ams03.atlas.cogentco.com [130.117.1
.226]
18 746 ms 744 ms 733 ms p4-0.core01.fra03.atlas.cogentco.com [130.117.0.
146]
19 734 ms 777 ms 744 ms t3-2.mpd01.fra03.atlas.cogentco.com [130.117.1.3
0]
20 739 ms 749 ms 753 ms v55.mpd01.fra05.atlas.cogentco.com [130.117.1.2]

21 744 ms 763 ms 743 ms rapidshare.de [130.117.156.24]

Trace complete.

Hope it can give someone an hint. I think the problem is more on my machine (XP) than the ISP because I've never had problems with my ISP before.

Will.Spencer · 10-19-2006, 06:27 AM

And all of your other applications are working? Everything but p2p?

If layers one, two, three, and parts of four are working, the obvious culprit is a firewall rule or router ACL.

I see that your Microsoft Windows XP Firewall is disabled. That adds to the confusion.

What device is your PC plugged into? Is there anything between it and the broadband modem?

What do you mean when you say "I have manually opened the requested ports as per the online help page." What did you open them up in? Whatever that device or software is -- it is the first suspect as the item which it causing you this trouble.

Note that the eMule TCP tests often fail. That's usually do to a NAT device somewhere in your network. This tests checks whether the eMule network can connect to you, not the other way around. eMule works even if these tests fail -- but not as well.

I suppose that it is theoretically possible that this was the exact time that Ecoweb decided to block p2p traffic. Have you asked them? I tried to check on their web site, but it is broken at the moment.

Kilo.Dollar · 10-20-2006, 06:21 AM

Well, I haven't contacted my ISP. I've never had problems with them. So I am tempted to assume it's not them.
I am on a LAN though. However, as noted before, I used to connect well. I checked my ports on another site, and all I got was most of them are "stealth" ports. Not really blocked. Not sure waht that means or how to get around it.
What I meant by "manually opening a port" is setting an exception for the program's required port in XP firewall.
Picture this. Before I could use MSN messenger, play Internet checkers, now I can't. Does ISP block these too???

Will.Spencer · 10-20-2006, 06:52 AM

What ports do work for you?

What device is your PC plugged into? Is there anything between it and the broadband modem? For example, a router or Wireless Access Point?

Kilo.Dollar · 10-23-2006, 02:18 AM

I have a radio link to my ISP's base station( Wireless access). Hope this is the info you require.
Before the following ports used to work 6346.

Will.Spencer · 10-23-2006, 03:52 AM

What ports work for you now?

Your PC connects directly to an 802.11 Wireless Access Point (WAP) provided by your ISP?

Kilo.Dollar · 10-24-2006, 03:38 AM

Quote:

Originally Posted by Will.Spencer

What ports work for you now?

Your PC connects directly to an 802.11 Wireless Access Point (WAP) provided by your ISP?

1. None except the 80.
2. No. Please note: Another PC on my LAN is able to connect so it cannot be a disconnection from my ISP.
3. Does changing IP addresss and network ID have any effect, because I did that?

Will.Spencer · 10-24-2006, 07:07 AM

Quote:

Originally Posted by Kilo.Dollar

1. None except the 80.

That points to a web proxy issue.

Quote:

Originally Posted by Kilo.Dollar

2. No. Please note: Another PC on my LAN is able to connect so it cannot be a disconnection from my ISP.

That points away from a web proxy issue. :???:

But, before we completely abandon that path, let's look at our proxy configuration on both machines.

In Internet Explorer:

Open the <Tools> menu
Click the <Internet Options> menu item
Click the <Connections> tab
Click the <LAN Settings> button
Do you have anything entered into any of these fields? (On either machine?)

If you are using a different web browser, the procedure to see your web proxy configuration will be different. What web browser are you using?

Quote:

Originally Posted by Kilo.Dollar

3. Does changing IP addresss and network ID have any effect, because I did that?

If those were broken, I can't think of how web browsing on port 80 would work.

Kilo.Dollar · 10-25-2006, 03:07 AM

Sure. On both machines>
Address: IDMSRV01
Port :8080
I'm using IE. Going to IE7 now.

Will.Spencer · 10-25-2006, 05:16 AM

Quote:

Originally Posted by Kilo.Dollar

Sure. On both machines>
Address: IDMSRV01
Port :8080
I'm using IE. Going to IE7 now.

So... your web traffic is going through a proxy.

Can you try unconfiguring that proxy, just as a test?

I have the awful feeling that I am missing something really obvious here, but I can't think of what it could be.

Kilo.Dollar · 10-26-2006, 04:48 AM

Sorry, how do I unconfigure the proxy?

Will.Spencer · 10-26-2006, 05:43 AM

How to Unconfigure a Proxy in Internet Explorer

In Internet Explorer:

Open the <Tools> menu
Click the <Internet Options> menu item
Click the <Connections> tab
Click the <LAN Settings> button
Uncheck Automatically detect settings
Uncheck Use automatic configuration script
Uncheck Use a proxy server for your LAN
Click the <OK> button

Kilo.Dollar · 10-26-2006, 07:57 AM

I C.
If I do that then I won't be able to browse. Unfortunately these settings had been there before with no problem.

Will.Spencer · 10-26-2006, 09:33 AM

That's why I said "just as a test."

Kilo.Dollar · 10-26-2006, 09:43 AM

I appreciate. Let me try to keep a cool head.
So what do you suggest we tackle next???

Will.Spencer · 10-29-2006, 10:00 PM

Quote:

Originally Posted by Kilo.Dollar

So what do you suggest we tackle next???

This is turning out to be quite an intractable problem.

As you have one PC that works and another PC that doesn't, I would try to set up everything on the failing PC exactly like the working PC is configured.

I would even unplug the working PC (as a test) and give the failing PC the IP address of the working PC, just to see if something is blocking your by IP address.

I would draw a diagram of the network, as it is still unclear how everything fits together. For example, are the two PC's connected to the Internet in exactly the same manner?

Just to be comprehensive, I would contact the ISP and tell them that MSN Messenger is not working. I would not mention P2P. ISP's hate P2P. :p

Kilo.Dollar · 10-30-2006, 05:31 AM

After playing aroundwith some settings this is where I am. Messenger now works, only if I manually assign an IP address

. Internet Checkers and P2P crew still not connecting. In fact, Messenger only works if I do not assign the preferred gateway. If I do put the gateway it fails to connect.
The machies I have are as follows: Win XP (SP2) - not connectin, Win 2000 (SP4) - connecting, Win 2000 (SP4) - server.

Will.Spencer · 11-05-2006, 01:07 AM

Quote:

Originally Posted by Kilo.Dollar

After playing aroundwith some settings this is where I am. Messenger now works, only if I manually assign an IP address

. Internet Checkers and P2P crew still not connecting. In fact, Messenger only works if I do not assign the preferred gateway. If I do put the gateway it fails to connect.

That confuses me even more, because layer three (the network layer) should affect all layer four (the transport layer) protocols in the same way -- and that is not what you are seeing here.

What did your ISP say when you contacted them?

How do the IP addresses of the two systems differ?

How does the IP address that you assigned manually differ from the IP address that you are receiving via DHCP?

Did you try swapping the IP addresses, as I suggested?

Have you compared the routing tables on both PC's? (`netstat -nr`)

Have you compared the output of `ipconfig /all` on both PC's?

What site/program/protocol are you using for Internet Checkers?

Kilo.Dollar · 11-06-2006, 03:20 AM

What did your ISP say when you contacted them?
- The said nothing has been changed. They feel the problem is on my side, or maybe software issues. And so it seems. Was assured they haven't (or aren't planning) killing the P2P yet. You think I could ask them to do more?

How do the IP addresses of the two systems differ?
- The two are on the same range. Mine I assign xxx.xx.xx.37 and the other machine has xxx.xx.xx.48

How does the IP address that you assigned manually differ from the IP address that you are receiving via DHCP
- DHCP gives me xxx.xx.xx.168 irrespective of whether I've left and rejoined the domain or not. The 37 was the previous address before this problem. Maybe this could be the cause.

Did you try swapping the IP addresses, as I suggested?
- Still there is no improvement. Have a feeling it may not have anything to do with IP addresses. Just a feeling...

Have you compared the routing tables on both PC's? (`netstat -nr`)
- Route tables of both machines the same.

Have you compared the output of `ipconfig /all` on both PC's?
- Same as above. Except one has "Hybrid" node type, and this one "Unknown"

What site/program/protocol are you using for Internet Checkers?
- Using the XP inbuilt Checkers. Start>All Programs>Games:Internet Checkers.

Will.Spencer · 11-07-2006, 10:50 PM

Quote:

Originally Posted by Kilo.Dollar

Did you try swapping the IP addresses, as I suggested?
- Still there is no improvement. Have a feeling it may not have anything to do with IP addresses. Just a feeling...

Not just a feeling now, a tested hypothesis.

Quote:

Originally Posted by Kilo.Dollar

Have you compared the output of `ipconfig /all` on both PC's?
- Same as above. Except one has "Hybrid" node type, and this one "Unknown"

I can't see NetBIOS as being the issue.

Quote:

Originally Posted by Kilo.Dollar

What site/program/protocol are you using for Internet Checkers?
- Using the XP inbuilt Checkers. Start>All Programs>Games:Internet Checkers.

That uses TCP port 28805. What does this tell us? Does this tell us that web stuff works because it goes through the web proxy, but all non-web traffic has issues? Hmmm... MSN Messenger doesn't quite fit that theory -- or any theory.

I could not be more confused if the sun rose in the West.

Kilo.Dollar · 11-08-2006, 03:36 AM

There is a site called Shields Up http://grc.com/x/ne.dll?bh0bkyd2, that reports all these ports as stealth
Is there a way around this?

Will.Spencer · 11-08-2006, 06:28 PM

Quote:

Originally Posted by Kilo.Dollar

There is a site called Shields Up http://grc.com/x/ne.dll?bh0bkyd2, that reports all these ports as stealth
Is there a way around this?

Stealth is a good thing. With standard TCP, a closed port will respond by saying "I'm closed!"

This gives an attacker information plus it helps an attackers network scan run quickly.

A stealth port, on the other hand, doesn't respond at all. The attacker gets no information and he has to wait for a response which he never receives. This makes all of his scanning run more slowly.

Kilo.Dollar · 11-10-2006, 02:48 AM

So isn't my problem related to them being stelath? Are stealth prots open or closed?