Grr ,cant get SETI client to connect to Q anymore,HELP!

[Assimilator1]

This is for little brother THE TERMINATOR

Using SETIDriver on my fathers PC ,proxy settings are ,host name - James on port - 5517 (no fixed IP's)
In the SETI CLi I get this error

recv fd=48 n=0, errno=2
Unexpected end of data from server

SETIQ's log gives me this error 19:27: Server Invalid IP address 192.168.0.x for setiqueue request

WTH does that mean??
The IP shown is the IP currently assigned to it.
Can anyone help me quickly with this one? ,not going to be here for too long

Thanks guys

 

[Freewolf]

The only time I had that error was when my router changed the ip address of all my machines after the power went out for a while and the router reset when it came back on
You might want to check the q setting for the seti@home server and see if they have been changed by someone.I think you could get that error if your setting are wrong.

 

[Assimilator1]

Now its funny you mention that because I forgot to say earlier that this error only occured after a router was installed when my father got broadband here.

Btw the Q is run on James's machine & his client connects with no problems!

I'm not sure what settings you are referring to but I think you mean in 'settings' ,'Queue server'

The IP is 127.0.0.1 (local host)
Subnet mask matches the machines

 

[Freewolf]

In your q setting what is the setting for the seti@home server? Does your brother's computer have any problem connecting to the internet?

 

[Assimilator1]

I didn't get what you meant by 'q setting' in your 1st post ,I still don't!
He can access the net fine

 

[Assimilator1]

Well ,I don't get it ,I went to 'settings' ,'Queue server' in the SETIQ window itself & altered the subnetmask from 255.255.255.0 to 0.0.0.0 & now my fathers client connects fine.

But why shouldn't it of done with a subnet mask of 255.255.255.0 ?
Both machines have the same subnet mask

 

[Freewolf]

You want the setting to be 0.0.0.0. Those are the setting the q uses to connect to the seti@home server
Those was the setting I was asking about.

 

[Assimilator1]

I think we're getting our wires crossed

Those are not the numbers the Q uses to connect to SETI (or other Q's) ,those numbers (subnetmask) dictate what SETI clients can connect to it.
His SETIQ was able to connect to another Q no probs
Where the Q goes to depends upon the 'connection type' in 'Queue server(server settings)'
Setting to 0.0.0.0 allows any & all clients to be able connect to it ,not something I really wanted to do ,anyway thanks for your help

But what I still don't get is why the client could no longer connect to my bros Q when SETIQ's IP was changed from 192.168.0.xx to 127.0.0.1 ,is it because the subnetmask only allows IP's from 127.0.0.1 to 127.0.0.254 once the IP is changed to the 127 range?

 

[Freewolf]

Sounds like you know more about it than I do.
Maybe Steve or Greg can tell you more .

 

[Confused]

Sorry i didn't get in here earlier, been out at a mate's house...

Anyway, for some reason, i've never been able to find out why, when you put something other than 0.0.0.0 in the IP and subnet for SetiQueue, clients can't connect, this has bugged me for a while, but don't know why.

In theory, setting up the IP address (ie 192.168.0.1) and the subnet mask (255.255.255.0) should allow everything in the 192.168.0.x range to connect, and refuse connection from other machines. However this doesn't seem to work in SQ.

Thinking about it, i am going to send an email over to Ken Reneris (the maker of SQ) and ask him why this is doing this

Will report back when i get an answer on this


Edit: I've just had a thought.....did you set an IP address on James' machine, and enter this in SetiQueue config? If so, then there is no reason why this might be doing it (refer to above), but if both machines are on DHCP then the IP address isn't static, so if in SQ you have the IP at 0.0.0.0 and the subnet mask as 255.255.255.0 it will only allow computers in the 0.0.0.x range to connect... One thing to try might be set up James' machine to use static IP, and set this IP in SQ settings...but then i've tried that before and it still gives same message....back to email i think!


Confused

 

[Rattledagger]

I'm a little confused...

Let's see if I've understood the problem...
Q1 is set to 127.0.0.1, sub-net 255.255.255.0
Q2 on another machine can't access Q1.

Since 127 is localhost, other machines must use something different to connect, so a sub-net of 255.0.0.0 to 255.255.255.255 will never work.
On the other hand, if you get Q1 & Q2 to 192.x.x.x, you can use sub-net 255.0.0.0
If Q1 & Q2 is on 192.168.x.x, you can use sub-net 255.255.0.0 and so on.

And to Confused...
Funny, I'm running SetiQueue with sub-net 255.0.0.0, and a fixed ip-address, and I've had no problems. (Ok, I've sometimes had problems getting wu from Berkeley...)

Edit...
I just tested seti-client-connect-part, and this worked as it should, allowing/refusing based on sub-net & ip-address. The same for the web-part (statistics ++)

 

[Assimilator1]

OMG this is getting in here!

In theory, setting up the IP address (ie 192.168.0.1) and the subnet mask (255.255.255.0) should allow everything in the 192.168.0.x range to connect, and refuse connection from other machines.

This has always worked for me ,in fact this is the setup that James had before the router was installed & DHCP was set.

but if both machines are on DHCP then the IP address isn't static, so if in SQ you have the IP at 0.0.0.0 and the subnet mask as 255.255.255.0 it will only allow computers in the 0.0.0.x range to connect

So I guess the other client wouldn't connect because it was on 192.168.0.x whilst SETIQ was 127.0.0.1?,the original subnetmask number was blocking attempts outside of 127.0.0.xxx? , & setting the subnetmask to 0.0.0.0 got around that limitation.Btw both James & my fathers PC have auto assigned IP's (by the router) of 192.168.0.x ,they seem to stay at the same number on each bootup but despite that if I lock James IP number than he loses the net!

Rattledagger
You know why that is?^^ hehe j/k

Let's see if I've understood the problem...
Q1 is set to 127.0.0.1, sub-net 255.255.255.0
Yes!

Q2 on another machine can't access Q1.
Close ,it isn't a 2nd Q but another SETI client(using SETIDriver),& yes it couldn't access James's Q(Q1)

Since 127 is localhost, other machines must use something different to connect, so a sub-net of 255.0.0.0 to 255.255.255.255 will never work.
I didn't know that ,that's where I went wrong ,I didn't realise the relationship between the IP & subnetmask

On the other hand, if you get Q1 & Q2 to 192.x.x.x, you can use sub-net 255.0.0.0
If Q1 & Q2 is on 192.168.x.x, you can use sub-net 255.255.0.0 and so on.
Yes that's exactly how it was ,but after the router was installed I could no longer relie on fixed IP's (wouldn't allow net access) ,and that's why I put in 127.0.0.1.

Anyway I fixed it by putting 0.0.0.0 in the subnetmask ,this allows any IP to connect .............. I don't suppose this will open the flood gates to uninvited Q users?

Thanks for the input guys

(Btw I hate auto assigned IP numbers!)