Need help getting SetiQ to work with LINKSYS 4 Port Router?

[Russ2kSE]

Any ideas? I can not get it to work. I am trying to assign a IP static for the machine that will have it, but when I do it will not see the internet period. Can anyone help me here?

 

[Russ]

Why not just let the router assign the IP address with DHCP? Much simpler.

But, if for some reason you need a static address assigned to the machine, make sure that the other network settings match the router. IE:

Unless you've changed it, it's set to 192.168.1.1, so set the NIC to 192.168.1.XXX. The subnet mask is 255.255.255.0, and the gateway would be 192.168.1.1 (same as the router). Then enter your primary and seconday DNS addresses provided by your ISP, and reboot the machine. The DNS servers should also be entered in the router itself.

Russ, NCNE

 

[office boy]

Just use computer name, as in "-proxy computername:5512". That will work fine.

 

[Russ2kSE]

Okay, you guys just confused me. So I can use DHCP for SetiQ? If so, how do I configured SetiQ to work then with the machines since it requires IP info?

 

[Russ]

After the machine has booted and grabbed an IP address, run winipcfg to find what that address is.

Russ, NCNE

 

[networkman]

I have the exact same router here and am using its DHCP functions. I also have SetiQ set up as well, but I run SetiQ on each PC(the logic being that if a single PC were to fail, my luck would determine it the be the single queue server). I haven't had any problems with the setup at all.. each machine boots up, gets assigned an IP and goes!

 

[Fardringle]

If you want to continue to use DHCP, and don't want to change the proxy IP number on the clients every time your SetiQ server's IP address changes, just use Office Boy's solution of putting the SetiQ computer's name instead of the IP address. That way, no matter what the IP address is, the clients will always be able to see and use the SetiQ, as long as all of the clients have installed Client for Microsoft Networks so that they can properly resolve the SetiQ computer name to an IP address..

 

[blade47]

These guys know a whole lot more than I do about networking so I'll just tell you what I'd do based on their fine advice.

As Russ said
<<Why not just let the router assign the IP address with DHCP? Much simpler.>>
Do what Russ said.

SetiQ itself doesn't require any ip info for the other machines trying to connect to it on the network. To get the other computers on the network to connect to the setiQ server all you have to do is set the proxy settings for each of the clients to point to the setiQ server.

Office boy stated
<<Just use computer name, as in &quot;-proxy computername:5512&quot;. That will work fine.>>
As he said you don't even have to know the ip of the machine running setiQ just the name of the computer.

Networkman stated
<<I run SetiQ on each PC(the logic being that if a single PC were to fail, my luck would determine it the be the single queue server).>>
That was my luck. It was always my setiQ server. This is a fine solution. Personally instead of running multiple copies of setiQ I run one setiQ server with a weeks worth of wu's and a copy of SetiDriver on each of my machines pointing to the setiQ server. That way I can keep a days worth of wu's on each pc in case of a setiQ server crash.

 

[Russ2kSE]

Where do I use that at? The proxy //computername:55 whatever you said?

 

[Fardringle]

If you are using the GUI client, just change the proxy settings to the name/IP address of the host, and the port to 5512.

If you are using the command line client, create a shortcut to the client, and on the end of the &quot;Target:&quot; line in the shortcut properties, add -proxy servername/address:5512 and you should be good to go.