SETI Q setup question

[Spacehead]

I want to get the client running on the same computer as SETI Q to start using the Q. I'm currently running the CLI, Driver & Spy.
My current Driver cache is set at 20, with 11 to return.
Do i just enter 127.0.0.1 as the host name & use port 5517 on Driver?
Do i even need to use Driver along with Q?

I'd like to get this sorted out, then point my other computer at SETI Q.

 

[Confused]

Yeah, that should all work.

I find it best if in Q you do not set it up with an IP address or subnet mask, leave them all at 0, i have only had problems with setting up these values!

You do not need to use Driver with Q, however it could be useful if Q decides to shut down for any reason, or anything else goes wrong with it


Confused

 

[Polo]

What confused said
I for myself use "-proxy 127.0.0.1:5517" at the end of the command line with no seti driver.

 

[deerslayer]

Mine is set at 192.168.0.1:5517

Should it be set up differently? I haven't had any troubles with it yet.

 

[JWMiddleton]

Spacehead, It is recommended that one uses the name of the system instead of the IP addy. For example I put "jwmiddleton" as the host and 5517 as the port (in my case.) When I had an IP addy in the host field I had trouble with the modem dialing whenever a WU was submitted by the system on which SetiQueue runs. 127.0.0.1 (loopback) might work, but I never tried it. I prefer to use SetiDriver with a days worth of WUs just in case SetiQueue gets closed or has a problem.

Good luck!

 

[Spacehead]

JWMiddleton,
If i go to Control Panel-System-Computer Name tab i can change the name to whatever i want? Then use that?
I should mention this is a Windows XP Home system.

 

[paf077]

Mine is set at 192.168.0.1:5517

That's fine if you have a router and the Q is on the main Pc, or your pc is set up has the router!

Mine has been that way for 10 months now and no problem.


Paf

 

[JWMiddleton]

Originally posted by: Spacehead
JWMiddleton,
If i go to Control Panel-System-Computer Name tab i can change the name to whatever i want? Then use that?
I should mention this is a Windows XP Home system.

Sorry that I didn't get back to you sooner. Dave and I have been celebrating our birthdays!

Yes, that would be the way to do it with WinXP. I set this up for my Mother on Wednesday and used XP Home.

 

[Spacehead]

Thanks!
I'll make sure this works, then try pointing my other computer at the Q.
I'm sure i'll be asking more questions

 

[Spacehead]

OK, SETI Q seems to be working good, for this computer. But i'm still having problems getting my network to work.

What i've been doing is transfering via CD-RW my entire SETI folder from my 2nd PC to my main PC to up/download WU's.
Can i setup a queue for this 2nd computer & have to up/download WU's into that when i transfer on CD?

 

[Rattledagger]

If you're running SetiQueue on a machine with no network-card but a modem, do NOT use the computer name, but use 127.0.0.1
I found this out the hard way last year.

It's no problem setting up a second setiqueue on the 2nd machine, and using CD-RW to move the queue back and forth. Just make sure the files don't get write-protected.

 

[Assimilator1]

Alternatively for the netless rig you could use SETIHide which has an import/export function for WU's & results

 

[Spacehead]

Originally posted by: Rattledagger
If you're running SetiQueue on a machine with no network-card but a modem, do NOT use the computer name, but use 127.0.0.1
I found this out the hard way last year.

It's no problem setting up a second setiqueue on the 2nd machine, and using CD-RW to move the queue back and forth. Just make sure the files don't get write-protected.

I don't think i really want to start moving the Q around. I'll just keep doing what i've been doing till i get this figured out.
And the Q is on a computer with a network card & a modem.

 

[dmcowen674]

Originally posted by: Spacehead
OK, SETI Q seems to be working good, for this computer. But i'm still having problems getting my network to work.

What i've been doing is transfering via CD-RW my entire SETI folder from my 2nd PC to my main PC to up/download WU's.
Can i setup a queue for this 2nd computer & have to up/download WU's into that when i transfer on CD?

What exactly is happening (or not happening) giving you trouble with a network?

 

[Spacehead]

Originally posted by: dmcowen674

What exactly is happening (or not happening) giving you trouble with a network?

Nothings happening. The 2 computers don't "see" each other.
Both have a Netgear FA311 ethernet card & i have a Netgear FS605 5 port switch.
Windows XP home & 98SE.

People that i've talked to say all i have to do is connect the 2 together & XP will find the other one.

I probably have some setting wrong somewhere.

 

[RaySun2Be]

Not strong on Win98, but do you have Client for Microsoft Networks loaded onto the Win98 PC?

I had a Win95 PC that could ping my SETIQ, but SETIDRIVER just wouldn't talk to it. Installed Client for Microsoft Networks and it started connecting to the SETIQ.

 

[Assimilator1]

Spacehead
I don't know much about XP but I've played around with 98SE & networks a few times.
Just pluggin them together won't do it for 98 ,I take it you TCP/IP installed? NIC drivers are ok? (only instance of them?),are they on the same workgroup?
You've shared both PC's?

 

[Smoke]

I think the problem here is he has a "switch" and not a "router".

Picture of a Local Area Network using the FS605 Switch and a RP614 Router

 

[RaySun2Be]

Spacehead,
Give us the specifics of each PC networking. What is installed, (Client for MS Networks, netbui, TCP/IP, etc.) the IP address information (ip address, subnet mask, gateway, etc.)

I'm assuming they are connected via the switch. For just getting the 2 PCs to talk to each other, a router isn't necessary as long as they are on the same IP address scheme, just a hub or switch is needed.

can you ping the other PC from each PC using the IP address, can you ping each PC from the other using the machine name?

 

[JWMiddleton]

Originally posted by: Spacehead

Nothings happening. The 2 computers don't "see" each other.
Both have a Netgear FA311 ethernet card & i have a Netgear FS605 5 port switch.
Windows XP home & 98SE.

People that i've talked to say all i have to do is connect the 2 together & XP will find the other one.

I probably have some setting wrong somewhere.

XP installs TCP/IP by default. But, there are a lot of places where you could have problems. On each of the XP boxes run "ipconfig /all" from a command prompt. (To get the command prompt: Click <Start><Run...>, then type "command" in the Open: box and click <OK>.) Tell us what the IP Address and Subnet Mask is for each machine. If you have an IP Address then run "ping xxx.xxx.xxx.xxx" from each machine using the IP Address of the other box. Did it work? Were there any lost packets?

/edit Dennis was faster than me! And he uses a cain! :Q

 

[Smoke]

I'll go back to my corner now.

 

[Spacehead]

Here's some of the answers to your questions.

XP Home
Ethernet adapter
Autoconfigured IP- 169.254.18.48
Subnet mask- 255.255.0.0
Default gateway is blank

Control Panel - Network Connections - Local Area connection - Properties
"This connection uses the following items"
- Client for MS Networks
- File & printer sharing for MS Networks
- QoS Packet Scheduler
- TCP/IP
All are checked & i assume these are a list of things installed.





Windows 98SE
0 Ethernet adapter
IP- 0.0.0.0
Subnet mask- 0.0.0.0
Default gateway is blank

1 Ethernet adapter
IP- 192.168.0.98
Subnet mask- 255.0.0.0
Default gateway- 192.168.0.1

On the 'Configuration" tab in Control Panel, under Network, the following are installed:
- Client for MS Networks
- Dial-Up Adapter
- Netgear FA311/312 PCI Adapter
- TCP/IP Dial-Up Adapter
- TCP/IP Netgear FA311/312 PCI Adapter
- File & printer sharing for MS Networks

Ping fails from both computers using IP address listed above & using the computer names.
I shut down ZA, NAV, & all SETI related programs while trying to ping, just in case.

To Assimilator1 questions:
Workgroup name on both comps is MSHOME
1 instance of NIC on both comps
I have the SETI Q folder shared on the XP comp & the SETI folder shared on the 98SE comp.


The weird thing is, when i had these comps built, the guy had them connected to his network. But i don't know how it was set up.
I'm going to call him later today, as he hasn't been replying to my emails.

 

[Smoke]

The weird thing is, when i had these comps built, the guy had them connected to his network. But i don't know how it was set up.

I bet he had a "router". :Q

/me runs back into the corner/

 

[Rattledagger]

Well, a sub-net of 255.0.0.0 means the 1st part of an ip-address must be the same...
A sub-net of 255.255.0.0 means both the 1st and 2nd part must be the same.

Therefore machine 1 can only access ip-169.254.0.0 to 169.254.255.254
Machine 2 can access the whole ip-192.-serie.

You should get both machines to use part of the same serie, either 169.254.x or 192.168.x with sub-net 255.255.0.0
It's probably easiest to manually configure this...

 

[Confused]

169.254.x.x is what Windows gives to a network adapter it cannot get any other info for.


Try setting the IP address manually on ALL computers to something in the 192.168.0.x range, with the subnet mask of 255.255.255.0


If you are using ICS to share the internet, then the "sharing" machine will be automatically set for 192.168.0.1, so pick 2, 3 etc for the rest of the PCs. Also, if using ICS, then on the other machines, enter the Default Gateway as 192.168.0.1, and also set the Primary DNS server to be 192.168.0.1 as well. This will tell the computers to look to 192.168.0.1 (the "sharing" PC) if they are trying to access something they cannot find on an internal network



Confused