TeAm Smokeball has FOUND its Q

[Smoke]

[EDIT]

It seems the purchase of a NEW router has fixed the situation.

_______________________

Well, I have been fighting with problems for over a week and have finally given up. I have thrown in the towel.

I have reformatted the server and notified the members to go to Berkeley for the time being. I'm going to install SetiQueue and start over completely new. This is going to take a lot of time and effort.

So don't be surprised if TS's numbers slide for a while.

Too late for advice, but sympathy appreciated.

 

[Fingers]

OH NO! :Q

 

[Orange Kid]

Been there, had to do that.................a restart every few days seems to cure a lot of SETIQueue's ill's............I don't think it can handle some of the massive logs it generates when Berkeley is having bandwidth woe's.

point them towards a public Q for the time being

 

[Crazee]

Sorry to hear that Smokeball

Good luck getting everything set up quickly.

 

[Swanny]

Hmmm, never had problems with mine. But I never do more than 30WUs a day either


Good luck getting it back up, gramps!

 

[ElFenix]

thats sorry to hear, how many units were lost?

 

[Smoke]

There were some scattered reports in the order of "I sent in six" my reply, "The Q says you only sent in 3". So I have no idea if or how many WUs were lost.

I have installed the latest version 3.03.2.2a but I seem to be stuck.

I'm trying all sorts of IP addresses without any luck. The Q server is one of my LAN computers.

I'm reading a "Install Help" File right now trying all sorts of entries.

 

[networkman]

--> tries to send over some sympathy via ESP.

 

[Evadman]

Awww poopie.

 

[Smoke]

Any suggestions on how to get outside computers to see my NEW Q?

The server is recognized on the LAN and recognizes all of the other LAN computers.

The server can contact Berkeley.

I have gotten one CLIENT recognized and Passed Through. It is the SetiDriver that is on the Server itself. I had to use the internal LAN address for it to get to the Q.

If I can get one of the other LAN computers using an outside IP Address to reach the Q I will be back in business. But I have not been able to accomplish this.

The SetiDriver Settings that worked before and should work again are as follows:

Host: smokeball.dns2go.com
Port: 5517

I would sure appreciate some help.

 

[IsOs]

Sorry to hear about your problem. I'm still using the older version of SETI Q 3.03.1.7 so I'm not familiar with the new version.

I'm guessing that the IP & subnet mask might be causing the problem. Are they set to 0? Is it possible for you to either post your current SETI Q setting or email copy of SETIQ.ini, client.ini and user.ini?

 

[lane42]

Hope you get it up and running Smokie.

 

[Crazee]

I can see your queue Smokeball. It should work for outside computers now

 

[Smoke]

Thanks Crazee,

About an hour ago I stumbled onto the problem. I thought my dns2go program was on a different computer. It turned out the dns2go program was on the Q server that got reformatted. Once I reinstalled the dns2go program I finally made contact with computers outside of the LAN.

I'm configuring my own computers first before I start the arduous task of contacting each client/member. :Q

 

[ICXRa]

Good luck getting everything back to normal Smokeball

 

[IsOs]

Glad to hear you got it fixed.

 

[toft-dk]

Sorry to hear that Smokeball

 

[Robor]

Sorry to hear that Greg. Hope you get it figured out and Team Smokeball is back at 100%.

 

[Assimilator1]

Sorry to hear about the trouble Smokeball

Hope you get everything sorted soon

I'll send ya some Beers for inspiration!

 

[Wiz]

Ouch Greg, that is a bummer

Running server software on Windows can be fun. (at least interesting)
There are some tricks like a scheduled reboot with the server software running as a service can definitely help some systems retain long distance stability. I can help you set that kind of thing up.
There is a utility that some of you might also find helpful called ServersAlive. I have used it for years, it watches services that you want to stay up and can run tests like 'does it respond within xx seconds?' If not: a) restart service or b) reboot machine

Here is a blurb from their site:

"The program can monitor up to 10 hosts/services in the unregistered version and up to 1000 in the registered version. If your organization only needs monitoring for 10 or less services then use Servers Alive for FREE as long as you want! "

Oh yeah, and be sure to see the FAQ, #7 is mine... (I wrote that several years ago)

 

[Orange Kid]

anyone else besides crazee able to reach Smokeball's Q

i can't

 

[sean2002]

NO luck connecting to the team Queue for me.

 

[Smoke]

Would you all try this link to the TS Q and report back if you can see it? Thanks.

TeAm Smokeball's SetiQueue

 

[CADsortaGUY]

nope

No can see

 

[Crazee]

Smoke I can still see your queue. Who is your internet provider? What is the external ip address that dns2go is pointing to?