Finally!!!: ALL FIXED NOW - setiQ help please - hooking up Linksys router, 2 hubs, 5 computers,

Wiz

Diamond Member
Feb 5, 2000
6,459
16
81
Ok, I dug out the Linksys router I got for free and hooked it up.
Got my machine working (online) quickly, hooked up it's first E'net port to the router.
Got second machine (wifes) online, no problem.
Trouble: SetiQ is set on 192.168.0.1 & my first internet connection is on dhcp - my machine finished a WU & it went through setiQ just fine, but I can't ping 192.168.0.1 from the wifes machine.
Mine is set at 192.168.1.100 & the wifes is 192.168.1.103 and they are both online.
My other E'net port is the one setiQ is attached to and it's address is fixed at 192.168.0.1

So - should I set my setiQ E'net port to DHCP & then all will be OK?



CHANGED TOPIC FROM:

I use Win XP ICS here on my home LAN & share out my cable modem to the wife & kids machines, all seti crunchers.
Last night my machine froze, I tried a restart & it got to the blue "Welcome" screen & just sat there.
After a few reboots I tried lowering my speed & latency & etc and still had the problem.

Then for one reason or another I let it sit at the "Welcome" screen a long time and oticed that the mouse pointer would move once every 30 seconds - 2 minutes. I waited a long time and eventually the desktop loaded. Very slowly.

OK - by very slowly I mean to say this entire process from start until I figured out what was causing it lasted from about 9:45pm - 2:20am.

Eventually by rebooting into safe mode and doing msconfig & starting without services & start up items and then enabling them one at a time until the SLOW reboot happened again I found it was the Internet Connection Sharing / Internet Firewall service causing the problem.

No matter what I do, when I try enabling it again the machine slows to a crawl of epic proportions.

SO - anybody hear of this happening and if so, a way to fix?

Thanks!
 

Unforgiven

Golden Member
May 11, 2001
1,827
0
0
have you check the dependencies of that service and made sure that all of the dependencies are working properly and are started before starting the Internet Connection Sharing / Internet Firewall service? it may be trying to start other dependent services and slowing way down because they are not started.
 

Wiz

Diamond Member
Feb 5, 2000
6,459
16
81
Yes, I can actually get the service started - the problem starts when I try to enable it in the Network control panel. As soon as I click OK after hitting "Share this connection" it freaks.

Now I'm hooking up a router, this is fun & games time with my 'elegant' ustairs / downstairs network. I already had two hubs - right now I know one is getting internet but not sure about downstairs yet.

I also have a problem with my setiQ now, as it is set for 192.168.0.1 & my router is handing out addresses starting at 192.168.1.100
I plugged into the router with that network interface but now I have to remember how to log onto the thing and change settings. What fun.
 

Wiz

Diamond Member
Feb 5, 2000
6,459
16
81
For now, I just turned of the Q & set SetiDriver to go direct to BerZerkley.
Easier than trying to figure out more networking crud.
 

Freewolf

Diamond Member
Feb 15, 2001
9,673
1
81
192.168.1.1 is your default router ip
I use the machine name and port # for the setidriver q setting myself as my router is set to give out the ip addresses to the machines and if it gets reset then the ip address can change from machine to machine.
 

Wiz

Diamond Member
Feb 5, 2000
6,459
16
81
Yes, I figured that out & got in there & mucked about a bit.

I don't know if having a static IP set downstairs is going to bite me in the butt sooner or later, I guess I can wait & see.
 

Narack

Junior Member
Jan 22, 2005
1
0
0
May be alot simpler for you if all components were kept on the same network, IE. 192.168.1.???. You shouldn't really be able to cross talk to networks without a bridge and if you were able to do it with 1 of 4 or 5 comps it is just a fluke.
 

Wiz

Diamond Member
Feb 5, 2000
6,459
16
81
Guess I mislead you a bit inadvertantly:
You shouldn't really be able to cross talk to networks without a bridge and if you were able to do it with 1 of 4 or 5 comps it is just a fluke.

Actually the one E'net port at 192.168.0.1 was plugged into the router and sent out from SetiQ a WU. So it was getting internet but the rest of the network couldn't see it (as expected).
 

Smoke

Distributed Computing Elite Member
Jan 3, 2001
12,650
207
106
Make sure your SetiQueue has the following setting:

Connect Type: WinINetDefault
 

ICXRa

Diamond Member
Jan 8, 2001
5,924
0
71
Why not disable DHCP on the router and then go in and hard code the IP's on each machine using the 192.168.XXX.XXX private class c? Are your routers and hubs connected via a straight through cable on uplink ports or are you using crossover cables to tie them together?
 

networkman

Lifer
Apr 23, 2000
10,436
1
0
Originally posted by: ICXRa
Why not disable DHCP on the router and then go in and hard code the IP's on each machine using the 192.168.XXX.XXX private class c? Are your routers and hubs connected via a straight through cable on uplink ports or are you using crossover cables to tie them together?

Actually, you don't even need to disable the DHCP. In my own setup here at home(with Linksys), I set the router to give out addresses from .2 up to .75 and then set each of my important boxes to fixed ip addresses of .60 and higher, since they'll likely never get issued as dynamic addresses anyway. :)

I also agree -- keep it all on the same network (192.168.1.xxx) to keep it simple.



 

Wiz

Diamond Member
Feb 5, 2000
6,459
16
81
Rich - do you have a SetiQ running there? That's all I'm trying to figure out now as everything else is working great.

Smoke - I'll try that - thanks ;)

ICXRa -

for all but one box:
Router <-> Hub <-> PC
all straight through - no crossover

for my machine, having two E'net ports each has a straight through cable connected directly to the router and each is currently set for DHCK getting IP's 192.168.1.100 & 192.168.1.102 - each seems to work fine - can ping them from other machines on the LAN

SetiQ says it's in IP 192.168.0.1

I don't see in the Linksys setup where to change to 192.168.0.xxx which is what would be needed (seemingly) to make the Q work - however maybe Smokes suggestion is what I need to try. ;)
 

ICXRa

Diamond Member
Jan 8, 2001
5,924
0
71
Well from the look of it the only issue is the queue residing in a different network. I can't think of anything that could be causing that except for a similar issue I had here at home. My surfboard always assigns my asante router with the .11 address automatically and dhcp cannot be disabled on the surfboard....acorrding to motorola anyway. I dislike dhcp hence the reason I disable it whenever possible because on my particular setup it took me awhile to discover that my cable modem was assiged .11 which in turn became my gateway for my boxes. Which model Linksys is it? Would be nice to figure out a way to change the address config and simplify the fix on this.
Stuff like this makes me dislike home switches with wan ports on them because it seems like in a effort to make it easier it often makes it more of a pain to do certian things.
 

Wiz

Diamond Member
Feb 5, 2000
6,459
16
81
Greg's suggestion worked - Thanks Smoke!

Thannks everyone, you are a helpful bunch to be sure! ;)
 

ICXRa

Diamond Member
Jan 8, 2001
5,924
0
71
Good news Wiz!

Should have guessed Smoke had the answer....you can't get one past the old man! ;)
 

Smoke

Distributed Computing Elite Member
Jan 3, 2001
12,650
207
106
Originally posted by: ICXRa
Good news Wiz!

Should have guessed Smoke had the answer....you can't get one past the old man! ;)
lol, Wiz maybe you should tell them how we met. ha ha lol
 

Wiz

Diamond Member
Feb 5, 2000
6,459
16
81
lol, Wiz maybe you should tell them how we met. ha ha lol

I would but...

I just discovered my Q isn't working yet.

I can ping both of the IP's on my machine - maybe I need to set it up to send to the first instead of the second. On my machine, if I set setidriver it to go to 127.0.0.1:5517 then of course it works and the Q can send / receive to / from Berzerkely.
However other machines on my LAN can't connect to my Q yet.
I'm working on that some more now.
 

Wiz

Diamond Member
Feb 5, 2000
6,459
16
81
Made another change, will see if any machines go out through the Q & report back.

Now putting http://192.168.1.112:5517 into the web browser brings up the setiQ so I am thinking it will work. Crossing fingers & toes this time... ;)






geez, when did I pass over 5000 Posts anyway??? Man I'm starting to feel old...
 

Smoke

Distributed Computing Elite Member
Jan 3, 2001
12,650
207
106
Run "ipconfig" and verify what the "ip address" is on the SetiQueue machine.

If, for example, the Q resides on a machine with an "ip address" of 192.168.1.100
(Do not confuse the "ip address" with the "Default Gateway")

Then the non-Q machines need to use the following

Proxy Server: 192.168.1.100
Port: (whatever your Q is using ... the default is 5517)*

*Look in the General SetiQueue settings for the Port Number

 

Wiz

Diamond Member
Feb 5, 2000
6,459
16
81
I think there is still a problem with Q settings as I think it's still got something about the old IP address in there:

"IP & Subnet Mask 192.168.0.1, 255.255.255.0"
 

Coolkid

Platinum Member
Mar 4, 2003
2,189
0
0
Originally posted by: Wiz
I think there is still a problem with Q settings as I think it's still got something about the old IP address in there:

"IP & Subnet Mask 192.168.0.1, 255.255.255.0"

If you change those both to 0.0.0.0, you shouldnt have any problems :)
 

Wiz

Diamond Member
Feb 5, 2000
6,459
16
81
If I knew where to do to change the IP for SetiQ I wouldn't be having these problems.
 

Unforgiven

Golden Member
May 11, 2001
1,827
0
0
open the seti queue icon, go to settings, server settings, set the settings:

IP Address to 0.0.0.0
Subnet Mask to 0.0.0.0

there you go.