OS and Software > Broadband Tweaks > Tweak Test

Tweak Test

Anyone? Please?

reply to mrsbones
• In the router you have to allow ICMP (Pings) or the router will block them.

• In ZA, set it NOT TO START AT BOOT. You cannot "disable" ZA as the True Vector service is still running, That is ZA.
--
"You can observe a lot by watching". Yogi Berra

Thanks. Will try that when I can get back to the computer.

reply to Irish Shark

When say "hangs" do you mean that after clicking on the Start Button that it launches, but it does give you the results?

Or, the test finishes and clicking on the Results Button it "hangs" there and does not give you any results?
--
"You can observe a lot by watching". Yogi Berra

I am working on it. Testing. Should have something today.
--
"You can observe a lot by watching". Yogi Berra

Ok, thanks.

I can run the Tweak Tester just fine. This what I have:

• I am on Win 7 x64 with IE9 (Beta)

• Both Ports 8085 and 8086 are not open. You can test your ports using this tool.
»www.yougetsignal.com/tools/open-ports/

• In the Windows Firewall, there are no rules (Inbound and Outbound) to allow or block anything on Ports 8085 and 8086.

• Microsoft Security Essentials is on for security. There is no setting to allow ports to bypass it.

• I have a router WRT54G running Tomato. Somewhere in there is a setting to allow Ports 8085 and 8086 access. I have looked for hours trying to find where the setting is; I can not find it. No Ports are being forwarded except for Skype. There in nothing in the DMZ. The only place that I found where it might be is in the routing table.

• What I would suggest is to take this in bite size pieces. If you have a router, pull the router out of the mix and see if that works. If it does, we now know that it is a routing setting that is blocking these ports.

• If it does not work, then there still something blocking the ports in the PC. Shutdown one potential blocker at a time and test. (ZA, Firewall, Popup blocker, etc.)
--
"You can observe a lot by watching". Yogi Berra

Thank you so much! I'll get on this tonight and see what happens. Thanks again!

After reading your ISP review and looking at the MODEM that posted in your first post, I might be pulling you through a knothole.

Can you please describe your hardware setup?

Thanks
--
"You can observe a lot by watching". Yogi Berra

Modem is an Option iCon 452 "Globetrotter" HSUPA (don't know what that means) with a SIM card, set to connect to 3G. It's connected to the router's USB modem port.

Router is a Cradlepoint MBR900 (home version) with firmware version 1.7.5 installed (latest version). It's a wired/wireless router made for mobile internet as well as wired, with 4 ethernet ports. My computer is connected to the router via ethernet cable.

AFAIK, it's a basic modem -> router -> computer configuration, just with a USB mobile modem instead of a wired box. It was all plug-n-play.

If you need more specific info, please let me know and I'll dig it up.

So you can pull the router and still connect to the Internet?

I pulled my router and connected directly to the MODEM and ran the Tweak Test. It worked just fine.

There is something in my Firewall that is allowing the two port to open. Checked the Firewall rules and I could not find any rules allowing the two port to open. So how can the test run?

I ran the Tweak Test and then had a Command Prompt running netstat -n. The two ports are now open, but where? I just let the Tweak Test alone not hitting the results button. Now I ran a netstat -b. IE9 was allowing the ports to open.

Back to the Firewall Rules looking for IE and the rules associated with it. One of the rules for IE said to accept any any program and open the port(s) it needed. If not explicitly denied, IE lets them in. That is why the Port Tester showed them as closed because nothing was running to open the ports. Security breach? Maybe; but with 65535 ports, you cannot have a rule for everything.
--
"You can observe a lot by watching". Yogi Berra

I can plug the modem directly to the computer and connect to the internet using the software that's preloaded in the modem (Option's UCanConnect).

I'll try the test running netstat when I'm in later today. It should give useful information, correct?

Yes, it should tell us something. If the ports are open up or not.

Open a Command prompt and set up netstat -n, but do not start it.

Run the Tweak Test and then quickly hit enter on the netstat. The two ports should show up if they are getting to your PC.

When the Tweak Test is finished, just leave it alone. Then run the netstat -b and see what program is associated with the two ports.

Good luck.
--
"You can observe a lot by watching". Yogi Berra

• The netstat -n will show all local ports that are in use and what outside IP address and the port that is wants opened. The netstat -b will show the ports in the netstat -n and what process is running that opens the ports.

• In the netstat results you are looking for is in the center column is the two ports that the Tweak Tester uses (8085 and 8086).

• As you can see only one (8086) is there. That says that the port is opened; but 8085 is not there. So it is possible that the router is blocking the port or a firewall/something else is blocking the port.

• The other things that I see is that port 8086 is listed twice. Also the the loopback address 127.0.0.1 is listed. 127.0.0.1 means that PC is only listening on the loopback interface. External devices can't connect to it. Software may connect to it locally on that same PC.

• the 192.168.0.197:xxxx is the router.

• In the netstat -b, port 8086 is opened by Firefox. So only one port that the Tweak Tester uses is established. That is why it is not working.

• This is what I get:

netstat -n

TCP 192.168.1.137:49870 209.123.192.189:8086 TIME_WAIT
TCP 192.168.1.137:49871 209.123.192.189:8085 ESTABLISHED

Netstat -b

[iexplore.exe]
TCP 192.168.1.137:49804 209.123.192.189:8086 TIME_WAIT
TCP 192.168.1.137:49805 209.123.192.189:8085 TIME_WAIT

• TIME_WAIT means both sides have agreed to close and TCP must now wait a prescribed time before taking the connection down.

• CLOSE_WAIT means the remote system has finished sending and your system has yet to say it's finished

• What I would suggest is put the quick start Java back in play. Look at Firefox and see if there is anything blocking ports. Make sure Avast is not running (look in Task Manager to see what programs and services are running).

• If all that looks OK, pull the router and test again, and use the netstat command.
--
"You can observe a lot by watching". Yogi Berra

Thanks for the info. I did notice that only 8086 was open.

I'll test again today per your advice.

reply to Irish Shark
AAARRRGGGHHH! I'm really getting frustrated with this.

OK, so I took the router out of the equation, disabled Avast, disabled ZA, and enabled Java Quick Start. Ran the tweak test and netstat -n. Still showing only port 8086 opening. Ran netstat -b, and no firewall/antivirus entries, just Firefox and Java. 127.0.0.1 still shows up at the top of the list.

I couldn't find anywhere in Firefox or IE 8 (upgraded the other day) where I could allow ports.

I then went into my TCP/IP properties and enabled IP filtering, adding ports 8085 and 8086 and selected "Permit Only". Rebooted the PC. Tried to connect to the internet but couldn't. Went back into TCP/IP properties and selected "Permit All" under IP Filtering. Rebooted the PC. The modem software showed "connected", but I couldn't connect to any websites. Went back into TCP/IP properties and disabled IP Filtering. Rebooted PC. Reconnected to the internet and can now get to websites.

The modem is connected to the router again. I don't think the router is blocking anything, since I got the same results from plugging directly into the PC.

Any thoughts? I am very grateful for your help, but if you're tapped out, I understand.