more seti Q help needed

[danzigrules]

ok here goes, I have a funky home network over here and i can't seem to to a client pc to upload WU thru my Q to orangeKids Q. Heres the rundown of the ips that I use on the network:

the gateway pc has 2 nics in it, 1 for the cable modem, the other for the internal network. Of course the cable modem is the ip that @home game me, and the internal starts with 10.0.0.1, but I have to use nat32 so the other pcs on the network can have net access, so the nat32 proggy uses the ip of 10.0.0.100. all the internal pcs get their ip from the nat pc. ex. 10.0.0.101.

I have tried setting the ip in setidriver on the client pcs to; 10.0.0.1, 10.0.0.100, and the ip of the cable modem. None of which work.

any ideas?

thx

 

[danzigrules]

no one knows eh 🙁

 

[Orange Kid]

with a lan it should work using the ip of the internal nic and the port that setiq is set to listen on.
as a second option you might try using

<< localhost >>

and the port # or even 127.0.0.1:whichever port#
i haven't used nat but one of these settings might work.

 

[Sukhoi]

Use the IP# of the LAN NIC, which I guess is 10.0.0.1:5517

 

[aiex]

Ok sorry to crash your thread but i need some seti q help as well.
1 of my cows went down and i lost their wu's that seti q sent them. Is there any way in order to tell seti q this so it doesn't keep them flashing up on the skymap and deletes them from its memory?

 

[Poof]

First - aiex... If you bring up Setiqueue's web interface on one of your machines &amp; login, you should be able to go to the &quot;Admin&quot; section, select &quot;Tools&quot;, and then select the item &quot;Delete/Recycle and overdue work unit&quot;. You should then see a list of WUs that are outstanding, and you can select each and decide what to do with it.

Next - danzigrules... I'm sortof confused at how your nat32 thing works. If you manually assigned your internal NIC as &quot;10.0.0.1&quot; but then also assigned it &quot;10.0.0.100&quot;, that can kinda be confusing. Granted, you can supposedly assign multiple IPs to a single NIC, but you might want to keep it to 1 unless that nat32 requires 2.

If you're trying to point Setidriver to your Setiqueue on your gateway machine, make sure you fill in the port info correctly on your Setidriver config screen for proxying, ie., it will need &quot;5517&quot;. Also, make sure that your Setiqueue is pointing to OK's at port 5001.