• 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.

Can't connect to my SetiQ!

Ken g6

Ken g6

Programming Moderator, Elite Member
Moderator
I just had to reinstall my network card drivers, because I fouled them up trying to install Microsoft WebTV. Anyway, I went through the Windows security steps at Shields Up!, for Windows 98, which I thought I had done before installing SetiQ. But now, whenever I try to connect over the network (to 127.0.0.1:5512) I get:

gethostbyname: No such file or directory
Can't connect to server; will retry in an hour.

So does anyone have any idea what network things I need to re-enable to get SetiQ working again? Not anything NetBIOS, I hope.

P.S. Another weird thing started happening at the same time: all normal-size bold text in this forum has stray pixels in weird places. Could this somehow be connected?

Thanks in advance!
 
You only need TCP/IP well configured on your nic. Netbios is not needed.
127.0.0.1 is your local IP. It's OK if you're running both SETIQ and SETI@Home on this machine.
 
What do you mean by "well configured"? Would SetiQ normally work with the configuration given in the link above? Have you tried it?

It is possible I installed the wrong driver for my machine, but web browsing seems to work.
 
Yep, pinging myself works just fine, from myself or from my mail server. I just can't connect to my own SetiQ.

BTW, I did get it working for my own system by patching the client. But I was just about to set up a miniteam on my SetiQ, with stats, so this puts a kink in my plans.
 
Well, I tried about everything else, so I finally tried binding Client for Microsoft Networks to the TCP/IP protocol. It worked; SetiQ is now accessible. 🙂 But that also means having SetiQ accessible requires a major security hole, enabling Client for Microsoft Networks and by implication NetBIOS. 🙁

So now I may have to install a personal firewall. 🙁

Update: Apparently this change makes my computer more visible, but still prevents anyone from doing anything to me (with current technology.) So I may not need that firewall yet. 🙂
 
You may already know this but NetBios isn't needed to run setiQ. All that's required is TCP/IP, that's the only protocol I'm running on my little network.

You might want to try zone alarm for your firewall it's very easy to use. Everything is configured using a gui, and it's free.🙂
 
Ken_g6: Are you using static or dynamic IP's? I don't think it will make a difference with your problem but it should be easier if your using dynamic IP's. I'm currently using the SetiQ PC's NetBIOS name on my clients to connect to SetiQ. I've got a Linksys router and when I reboot all of the systems it changes the IP sometimes. I got tired of changing all the clients to point to the new IP. I use SetiLog in combo with the 3.0 CL client.
Here's my line: "C:\Program Files\SETI@home\SETILog.exe" -proxy system2:5512 /s /h

Oh, before I did this I was just pointing the clients to my SetiQ PC's IP. Even on the PC running the client and SetiQ I used the machine's IP (not 127.0.0.1:5512). I don't see how that would make a difference but it's worth a shot if you haven't already tried.

Good luck!

Rob
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top