• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

help! setiqueue problems

S

strikermike

Member
Please help,
All of a sudden one of my computers can no longer connect to my queue. When I try to transmit I get this message
FD=64 N=0, ERRNO2. In the server log I find this message Invalid IP 192.168.0.210 setiqueue request. The computer running the queue can see the problem computer and visa versa. Any thoughts ? Thanks 😕
rolleye.gif
😕
 
I'd check to see if any firewall or security measures have been activated on the client computer or the Q server for that matter.

And make sure BLOCK WAN REQUEST has not been enabled in your router.
 
Idon't think it would have to do with WAN settings. I'm assuming these computers are in the same building using the same IP range and subnet mask based on the 192.168.0.xxx IP address.

Oh I just found that in the http server settings you can set up a dedicated IP & subnet mask range to accept client access from. If you have chnged those settings you should set them back to the default and set "allow any IP address" back to "enabled".
 
Originally posted by: strikermike
Please help,
All of a sudden one of my computers can no longer connect to my queue. When I try to transmit I get this message
FD=64 N=0, ERRNO2. In the server log I find this message Invalid IP 192.168.0.210 setiqueue request. The computer running the queue can see the problem computer and visa versa. Any thoughts ? Thanks 😕
rolleye.gif
😕
Click to expand...

I had the exact same problem!:Q ,this is with my fathers PC connecting to my brothers Q ,suddenely it refused to connect (after working fine for months).I got the exact same server log report too!😕.As a temporary fix (last week) I got the machine to connect to an external Q & it worked no problem!😕.On Monday I redirected it back to my bros Q after I altered some settings in ZA (allowed IP ranges ,to enable them to see each other),I don't know if thats anything to do with the SETI problem though ,& I don't yet know if the problems fixed
 
Thanks Baldy, Assimilator, and Smokeball things I have already tried with no luck
1) in Http server allow any IP
2) In Queue Clients Tried a dedicated port also no Joy
3) deleted and reinstalled setidriver on problem machine no luck
4) Made sure the Machine name and Display name match but no Luck.
It seems that the queue is receiving the request but for some reason is not honoring the request for a new WU. I was hoping
someone might know what the error message means. Ths machine will still connect directly to Berkley.
 
On my fathers PC the IP address had been changed (to auto assign from fixed) though the problem occured a week or more after that..........I think.
Could it be that SETIQ has assigned an IP to a client which now has a different IP?
 
Oh yes check in the Userxxxxxxx (x's = numbers) folder and then in the Qxxxx folder for your client_xxx.ini file for that client. Client name is in the top line when the file is open. Open it in wordpad and check the value of these two lines for these settings:

Client/FixedIp=FALSE
Client/FixedPort=0

If they are different set them to this, save the file, exit and reenter setiqueue and then try to connect to it again.
 
Thanks Baldy18 ,handy to know 🙂 ,I'll check my brothers Q latter.

Btw isn't the same information available through the browser in 'Clients' ,clients name?.

Fixed IP lookup -
Dedicate client port -
 
You know you're right it is in there also. I learned how to edit settings first in the ini files so I'm still learning where everything is in the browser interface.
 
Thanks for all the help but still no luck. I checked the proper client ini file and edited the ip address to match the known address of the problem computer but still no luck. I was thinking if I should just delete the client from the queue and then try to establish a new connection. Any suggestions on that?
 
I finally fixed my problem. Even though allow anny Ip address was checked in HTTP server settings.Ypo still need to check in queue server settings by setting both the IP and subnet to all 0's everything seems to work so far. Thanks for all your help.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top