TeAm Smokeball has FOUND its Q

[Smoke]

I got a report from LEGEND (a member of TS) that he can now see the team's Q. This is while still using the router which I have been on for the last hour.

I contacted PUFF (another member of TS) and had him try to open the team's Q with his browser and he was unable to do so.

So it is still a mixed bag. I have one new person who previously could not see the Q who now can, but I have another client who is still unable to see the Q.

So at this time I think I will take the router out of the setup and just hook the Q Server directly to the Modem. I'll post again when the changeover has taken place.

 

[Smoke]

OK, I am now on the Q Server running straight through the MODEM. There is no router in the setup.

If some of you can now try to "see" the "TS Q" I would appreciate it.

TeAm Smokeball SetiQueue

 

[Confused]

Yup can see it

Couldn't before!

Confused

 

[NOX]

Well, I can see it. The only thing is I tried to do a Tracert like OK and got this...

Microsoft(R) Windows DOS
(C)Copyright Microsoft Corp 1990-1999.

C:\>tracert smokeball.dns2go.com

Tracing route to smokeball.dns2go.com [66.21.162.62]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 172 ms 203 ms 187 ms adsl-21-162-62.bix.bellsouth.net [66.21.162.62]


Trace complete.

C:\>

Ping is fine though.

 

[Confused]

This is from the UK


Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\>tracert smokeball.dns2go.com

Tracing route to smokeball.dns2go.com [66.21.162.62]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms server.mshome.net [192.168.0.1]
2 11 ms 30 ms 21 ms 172.26.43.254
3 11 ms 11 ms 22 ms col-cam1-a-fa00.inet.ntl.com [213.107.240.1]
4 14 ms 10 ms 12 ms col-t2core-a-pos42.inet.ntl.com [213.107.225.9]

5 13 ms 14 ms 12 ms pop-bb-a-so-603-0.inet.ntl.com [62.253.184.153]

6 27 ms 29 ms 19 ms pop-bb-b-ge-730-0.inet.ntl.com [213.105.172.81]

7 19 ms 19 ms 51 ms so-4-2-0.cr1.lhr3.uk.mfnx.net [208.185.188.41]
8 93 ms 90 ms 92 ms so-7-0-0.cr1.dca2.us.mfnx.net [64.125.31.186]
9 121 ms 120 ms 119 ms so-6-0-0.cr1.dfw2.us.mfnx.net [216.200.127.205]

10 122 ms 180 ms 121 ms pos0-0.mpr1.dfw2.us.mfnx.net [216.200.127.214]
11 120 ms 120 ms 119 ms uunet-abovenet-OC12.dfw2.above.net [208.184.231.
250]
12 125 ms 133 ms 119 ms 0.so-1-3-0.XL1.DFW9.ALTER.NET [152.63.99.210]
13 130 ms 136 ms 129 ms 0.so-7-0-0.XL1.HOU7.ALTER.NET [152.63.103.93]
14 131 ms 159 ms 129 ms POS6-0.GW6.HOU7.ALTER.NET [152.63.101.173]
15 141 ms 144 ms 136 ms bellsouth-hou-gw.customer.alter.net [65.208.9.15
4]
16 136 ms 135 ms 145 ms 205.152.132.141
17 153 ms 142 ms 141 ms 205.152.27.46
18 203 ms 141 ms 169 ms 205.152.27.198
19 148 ms 145 ms 158 ms 66.21.224.94
20 215 ms 194 ms 229 ms adsl-21-162-62.bix.bellsouth.net [66.21.162.62]


Trace complete.

C:\>

 

[Assimilator1]

I can see your Q no probs

 

[Smoke]

It seems I have isolated the problem. Some of you from as far away as England have reported seeing the Q.

Now PUFF even reports seeing the Q.

I just got off the phone and walked PUFF through the setup of his SetiDriver and he was recognized immediately by the Q. He is now back in the fold.

So now I have to decide if I should just scrap the Linksys Router Model BEFW11S4 or not.

It would be a shame if the only problem is a "setting". I think I'll go up to my local Office Depot and buy a new one. I'll set it up and then see if PUFF and other TS members can see the Q and successfully get setup again as active clients. Then I'll check the settings (assuming it will work) and see if anything is different in that router than my current one. If the settings are the same it will then be determined that the "router" is indeed defective. And that "would" really be a shame because it has been working perfectly except for this SetiQueue problem.

I'll update this thread when something new has been determined.

I want to thank all of you that have been giving me a helping hand with this. I have to say I was starting to get really depressed. :Q

But there is light at the end of the tunnel.

 

[Crazee]

Glad to hear things are better

Keep us informed and let us know if there is anything else we can do

 

[Orange Kid]

I seeeeeeeeee youuuuuuuuuu

 

[Smoke]

I just purchased a NEW BEFW11S4 from Office Depot. I'm going to look at and write down the settings for the OLD BEFW11S4 before I completely take it offline. As I write this I am still hooked up straight through the MODEM.

I'll install the NEW router and then I would like to request if you all would look to see if the Q is still visible. If it is, I will double check to see if there are any settings with the NEW router that differ from the OLD one.

I could go on with the plan but for now that will be as far as I need to elaborate.

So I'll post when I'm up and running on the NEW router and we will see "if" it works. :Q

Greg

 

[Confused]

Greg, if i'm still awake by the time you get the new router in, then i'll see if i can still see you baby, shaking a little ass, from across the pond

Garry

 

[Smoke]

OK, I'm now operating with the NEW router.

Please see if you all can see the TS Q. /fingers crossed/

 

[Confused]

Yup, i can see the black screen of Seti Queue

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\>tracert smokeball.dns2go.com

Tracing route to smokeball.dns2go.com [66.21.164.10]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms server.mshome.net [192.168.0.1]
2 11 ms 36 ms 16 ms 172.26.43.254
3 13 ms 11 ms 11 ms col-cam1-a-fa00.inet.ntl.com [213.107.240.1]
4 11 ms 59 ms 11 ms col-t2core-a-pos42.inet.ntl.com [213.107.225.9]

5 14 ms 14 ms 15 ms pop-bb-a-so-603-0.inet.ntl.com [62.253.184.153]

6 19 ms 20 ms 20 ms pop-bb-b-ge-720-0.inet.ntl.com [213.105.172.77]

7 20 ms 19 ms 27 ms so-4-2-0.cr1.lhr3.uk.mfnx.net [208.185.188.41]
8 96 ms 90 ms 90 ms so-7-0-0.cr1.dca2.us.mfnx.net [64.125.31.186]
9 118 ms 120 ms 119 ms so-6-0-0.cr1.dfw2.us.mfnx.net [216.200.127.205]

10 119 ms 121 ms 119 ms pos0-0.mpr1.dfw2.us.mfnx.net [216.200.127.214]
11 119 ms 119 ms 121 ms uunet-abovenet-OC12.dfw2.above.net [208.184.231.
250]
12 120 ms 120 ms 119 ms 0.so-1-3-0.XL1.DFW9.ALTER.NET [152.63.99.210]
13 153 ms 131 ms 141 ms 0.so-7-0-0.XL1.HOU7.ALTER.NET [152.63.103.93]
14 130 ms 130 ms 158 ms POS6-0.GW6.HOU7.ALTER.NET [152.63.101.173]
15 174 ms 145 ms 136 ms bellsouth-hou-gw.customer.alter.net [65.208.9.15
8]
16 167 ms 136 ms 154 ms 205.152.132.205
17 148 ms 143 ms 157 ms 205.152.27.38
18 142 ms 143 ms 183 ms 205.152.27.134
19 143 ms 146 ms 147 ms 66.21.224.94
20 208 ms 225 ms 196 ms adsl-21-164-10.bix.bellsouth.net [66.21.164.10]


Trace complete.

C:\>ping smokeball.dns2go.com

Pinging smokeball.dns2go.com [66.21.164.10] with 32 bytes of data:

Reply from 66.21.164.10: bytes=32 time=197ms TTL=130
Reply from 66.21.164.10: bytes=32 time=194ms TTL=130
Reply from 66.21.164.10: bytes=32 time=198ms TTL=130
Reply from 66.21.164.10: bytes=32 time=197ms TTL=130

Ping statistics for 66.21.164.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 194ms, Maximum = 198ms, Average = 196ms

C:\>





So what you gonna do about your old router *cough*give to me*cough**splutter*

Garry

 

[NOX]

Everthing seems ok here from Hawaii...

Microsoft(R) Windows DOS
(C)Copyright Microsoft Corp 1990-1999.

C:\>ping smokeball.dns2go.com

Pinging smokeball.dns2go.com [66.21.164.10] with 32 bytes of data:

Reply from 66.21.164.10: bytes=32 time=188ms TTL=132
Reply from 66.21.164.10: bytes=32 time=188ms TTL=132
Reply from 66.21.164.10: bytes=32 time=172ms TTL=132
Reply from 66.21.164.10: bytes=32 time=172ms TTL=132

Ping statistics for 66.21.164.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 172ms, Maximum = 188ms, Average = 180ms

C:\>

 

[Assimilator1]

yeah I can see it no probs

 

[serialb]

So, did you buy the same router? Do they have different versions? Usually, firmware upgrades on routers will give more functionality. Try to do a firmware upgrade on your old one and see if that helps. If so, that could save you a few bucks.

 

[Smoke]

migroo,

I bought another Linksys BEFW11S4. This one has the designation of Version 2. :Q

During the turmoil, one of the first things I did was to update the firmware. Actually if was after I did the firmware update that things got progressively worse.

The OLD router is still good and I'm going to let my son have it. It will enable him to create a LAN with my granddaughter's computer and free him from manually dialing in on her 56K to upload/download SETI WUs. Plus she will have DSL speed to surf the web.

/got to remind him to put one of those Parental Filters on her computer.

 

[Migroo]

LOL, wrong Snowman

That Snowman is serialb



I like disguises...

 

[Smoke]

Ha Ha, excuse my old eyes. LOL

I will not edit that post. What's the point of being stupid if you can't demonstrate it once in a while.

 

[Confused]

Migroo, Ray did that yesterday, he confused me with Conjur!

These old people, tsk!

 

[RaySun2Be]

<< Migroo, Ray did that yesterday, he confused me with Conjur!

These old people, tsk! >>



Hey!


I resemble that remark!


Again, sorry about that Confused. Or was it Conjur? Or maybe Conjused? Or Confur? Eh, all I know it was some young punk, anyway....

 

[Migroo]

Ray, dont you mean 'resent'??



LOL, again

 

[serialb]

LOL, wrong Snowman

That Snowman is Migroo



I like disguises...



I realize there are different versions of Linksys routers, but I have no idea what differentiate them. Same firmware same everything.

 

[Smoke]

serialb,

/got that right this time/ Ha

The new version 2 has some changes in the configuration area and I noticed the firmware is 1.40.2, Nov 28 2001.

It also comes with Virus [PC-Cillin] and Firewall [ZoneAlarm Pro] software with options within the SETUP to activate them. So far I have not chosen to do that.

One thing didn't change is the PASSWORD. Ha Ha