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

SETI down?

THis is the only news I see there (for April):

? April 3, 2003 ?
We're currently preforming some maintenance on our team pages. Please bear with us.
 
Originally posted by: Wiz
I can get to the Berkley S@H web pages but can't submit any work.
Click to expand...

I can't even get to the berkley page. I wish I could use queues!!!!

Can anyone send me some unprocessed WUs? 😉
 
looks like I can send units in but not get any new ones. 😕

3:25pm: Sending result 08fe03aa.2507.20208.528412.172
3:09pm: Download WU: Failed Connect to shserver2.ssl.berkeley.edu:80 (network i/o timedout)
3:08pm: Sending result 07fe03ab.21591.33154.679838.160
3:00pm: Sending result 09fe03aa.430.22562.922168.186
1:37pm: Waiting 10s before trying again
1:37pm: Download WU: Failed Connect to shserver2.ssl.berkeley.edu:80 (network i/o timedout)
1:36pm: Sending result 17fe03ab.12838.5328.215900.247
1:36pm: Waiting 10s before trying again
1:36pm: Sending Result: Failed Connect to shserver2.ssl.berkeley.edu:80 (network i/o timedout)
1:36pm: Sending result 17fe03ab.12838.5328.215900.247
1:27pm: Sending result 08fe03aa.2507.13568.565904.154
1:17pm: Waiting 10m00s before trying again
1:17pm: Download WU: Failed Connect to shserver2.ssl.berkeley.edu:80 (network i/o timedout)
1:07pm: Waiting 10m00s before trying again
1:07pm: Sending Result: Failed Connect to shserver2.ssl.berkeley.edu:80 (network i/o timedout)
1:07pm: Sending result 08fe03aa.2507.13568.565904.154
12:57pm: Waiting 10m00s before trying again
12:57pm: Download WU: Failed Connect to shserver2.ssl.berkeley.edu:80 (network i/o timedout)
12:46pm: Waiting 10m00s before trying again
12:46pm: Sending Result: Failed Connect to shserver2.ssl.berkeley.edu:80 (network i/o timedout)
12:46pm: Sending result 08fe03aa.2507.13568.565904.154
12:36pm: Waiting 10m00s before trying again
12:36pm: Download WU: Failed Connect to shserver2.ssl.berkeley.edu:80 (network i/o timedout)
12:26pm: Waiting 10m00s before trying again
12:26pm: Sending Result: Failed Connect to shserver2.ssl.berkeley.edu:80 (network i/o timedout)
12:25pm: Sending result 08fe03aa.2507.13568.565904.154
12:15pm: Waiting 10m00s before trying again
12:15pm: Download WU: Failed Connect to shserver2.ssl.berkeley.edu:80 (network i/o timedout)
12:09pm: Waiting 5m51s before trying again
12:09pm: Sending Result: Failed Connect to shserver2.ssl.berkeley.edu:80 (network i/o timedout)
12:09pm: Sending result 08fe03aa.2507.13568.565904.154
12:06pm: Waiting 2m55s before trying again
12:06pm: Download WU: Failed Connect to shserver2.ssl.berkeley.edu:80 (network i/o timedout)
12:04pm: Waiting 1m27s before trying again
12:04pm: Sending Result: Failed Connect to shserver2.ssl.berkeley.edu:80 (network i/o timedout)
12:04pm: Sending result 08fe03aa.2507.13568.565904.154
12:03pm: Waiting 43s before trying again
12:03pm: Download WU: Failed Connect to shserver2.ssl.berkeley.edu:80 (network i/o timedout)
12:02pm: Waiting 21s before trying again
12:02pm: Sending Result: Failed Connect to shserver2.ssl.berkeley.edu:80 (network i/o timedout)
12:02pm: Sending result 08fe03aa.2507.13568.565904.154
12:02pm: Waiting 10s before trying again
12:02pm: Sending Result: Failed Connect to shserver2.ssl.berkeley.edu:80 (network i/o timedout)
12:01pm: Sending result 08fe03aa.2507.13568.565904.154
 
Latest news

? April 4, 2003 ?
We had a UPS in our server room blow out. We may have another outage or 2 today while we shift things around.

There will also be intermittent service drops for one hour starting tomorrow at 0800 UT while maintenance is performed on our Internet link.
 
Originally posted by: Intelligence3
Originally posted by: Wiz
I can get to the Berkley S@H web pages but can't submit any work.
Click to expand...

I can't even get to the berkley page. I wish I could use queues!!!!

Can anyone send me some unprocessed WUs? 😉
Click to expand...

Why cant you use queues?
 
I can't use queues because the firewall here at work seems to interfere with them. Very annoying. I have tried several different queues now, but I never successfully connect.
 
I don't see any port 80 queues in the list thread. Do you know anyone who has one?
 
I was running my Queue on port 80, a long time ago, but it started intefering with the web server i wanted to set up (and the web server, at the time (IIS) didn't like to play on a non-standard port) so i changed to another port.

Still have web server, and also have people now using the Queue, so i can't put mine on port 80, unfortunately


Confused
 
Try the one on port 443, HTTPS ..

Its CADkindaGuy queue...

It might be available since most firewalls open for this port also..
 
I tried Port 80 when I first setup my Queue. I was stumbling through the install and followed a suggestion to use DMZ (?) and Port 80.

What followed was unbelieveable. I became overun with thousands of Trojan, Greek 😉 , and "you name it" viruses. After turning off SetiQueue and the the DMZ (?) Port 80, I worked for many hours with Norton eliminating viruses that seemed to grow in number faster than I could quarantine and delete them.

I finally got all of them removed (I thought) but within the next week my computer started acting very strangely. Finally upon a reboot one day, I completely lost the BIOS and in effect the motherboard itself.

Now maybe if I had not enabled DMZ (? I think that's what it's called), all of this would not have happened but right now I'm determined to never fool around with Port 80 again. :Q

Actually I just ran Shields UP! using both the "Test My Shields !" and the "Probe My Ports !" [OK, let's not have any smart remarks on this --- that is what "they" call it 😛] tests to see how my current defenses are holding up. I suggest you all do the same. 😉

What I found most interesting was the "Probe My Ports !" test which gave the following report. Notice the "STATUS" of Port 80. :Q


Port
Service
Status Security Implications

21
FTP
Closed Your computer has responded that this port exists but is currently closed to connections.

23
Telnet
Closed Your computer has responded that this port exists but is currently closed to connections.

25
SMTP
Closed Your computer has responded that this port exists but is currently closed to connections.

79
Finger
Closed Your computer has responded that this port exists but is currently closed to connections.

80
HTTP
Stealth! There is NO EVIDENCE WHATSOEVER that a port (or even any computer) exists at this IP address!

110
POP3
Closed Your computer has responded that this port exists but is currently closed to connections.

113
IDENT
Closed Your computer has responded that this port exists but is currently closed to connections.

135
RPC
Closed Your computer has responded that this port exists but is currently closed to connections.

139
Net
BIOS
Closed Your computer has responded that this port exists but is currently closed to connections.

143
IMAP
Closed Your computer has responded that this port exists but is currently closed to connections.

443
HTTPS
Closed Your computer has responded that this port exists but is currently closed to connections.

445
MSFT
DS
Closed Your computer has responded that this port exists but is currently closed to connections.

5000
UPnP
Closed Your computer has responded that this port exists but is currently closed to connections.


The following was the report I received when I ran "Test My Shields !":

Attempting connection to your computer. . .

Shields UP! is now attempting to contact the Hidden Internet Server within your PC. It is likely that no one has told you that your own personal computer may now be functioning as an Internet Server with neither your knowledge nor your permission. And that it may be serving up all or many of your personal files for reading, writing, modification and even deletion by anyone, anywhere, on the Internet!

Preliminary Internet connection refused!
This is extremely favorable for your system's overall Windows File and Printer Sharing security. Most Windows systems, with the Network Neighborhood installed, hold the NetBIOS port 139 wide open to solicit connections from all passing traffic. Either this system has closed this usually-open port, or some equipment or software such as a "firewall" is preventing external connection and has firmly closed the dangerous port 139 to all passersby. (Congratulations!)

Unable to connect with NetBIOS to your computer.
All attempts to get any information from your computer have FAILED. (This is very uncommon for a Windows networking-based PC.) Relative to vulnerabilities from Windows networking, this computer appears to be VERY SECURE since it is NOT exposing ANY of its internal NetBIOS networking protocol over the Internet.
 
Smokie posted a busted link 😛 Here's the correct one 😛

Port Probe
Port
Service
Status Security Implications

21
FTP
Stealth! There is NO EVIDENCE WHATSOEVER that a port (or even any computer) exists at this IP address!

23
Telnet
Stealth! There is NO EVIDENCE WHATSOEVER that a port (or even any computer) exists at this IP address!

25
SMTP
Stealth! There is NO EVIDENCE WHATSOEVER that a port (or even any computer) exists at this IP address!

79
Finger
Stealth! There is NO EVIDENCE WHATSOEVER that a port (or even any computer) exists at this IP address!

80
HTTP
OPEN! The web is so insecure these days that new security "exploits" are being discovered almost daily. There are many known problems with Microsoft's Personal Web Server (PWS) and its Frontpage Extensions that many people run on their personal machines. So having port 80 "open" as it is here causes intruders to wonder how much information you might be willing to give away.

110
POP3
Stealth! There is NO EVIDENCE WHATSOEVER that a port (or even any computer) exists at this IP address!

113
IDENT
Stealth! There is NO EVIDENCE WHATSOEVER that a port (or even any computer) exists at this IP address!

135
RPC
Stealth! There is NO EVIDENCE WHATSOEVER that a port (or even any computer) exists at this IP address!

139
Net
BIOS
Stealth! There is NO EVIDENCE WHATSOEVER that a port (or even any computer) exists at this IP address!

143
IMAP
Stealth! There is NO EVIDENCE WHATSOEVER that a port (or even any computer) exists at this IP address!

443
HTTPS
Stealth! There is NO EVIDENCE WHATSOEVER that a port (or even any computer) exists at this IP address!

445
MSFT
DS
Stealth! There is NO EVIDENCE WHATSOEVER that a port (or even any computer) exists at this IP address!

5000
UPnP
Stealth! There is NO EVIDENCE WHATSOEVER that a port (or even any computer) exists at this IP address!
Click to expand...

Of course I know that there is a server running on port 80, but it's Apache, so doesn't get attacked by most of the IIS things! 😉

Test My Shields!
Attempting connection to your computer. . .
Shields UP! is now attempting to contact the Hidden Internet Server within your PC. It is likely that no one has told you that your own personal computer may now be functioning as an Internet Server with neither your knowledge nor your permission. And that it may be serving up all or many of your personal files for reading, writing, modification and even deletion by anyone, anywhere, on the Internet!

Your Internet port 139 does not appear to exist!
One or more ports on this system are operating in FULL STEALTH MODE! Standard Internet behavior requires port connection attempts to be answered with a success or refusal response. Therefore, only an attempt to connect to a nonexistent computer results in no response of either kind. But YOUR computer has DELIBERATELY CHOSEN NOT TO RESPOND (that's very cool!) which represents advanced computer and port stealthing capabilities. A machine configured in this fashion is well hardened to Internet NetBIOS attack and intrusion.

Unable to connect with NetBIOS to your computer.
All attempts to get any information from your computer have FAILED. (This is very uncommon for a Windows networking-based PC.) Relative to vulnerabilities from Windows networking, this computer appears to be VERY SECURE since it is NOT exposing ANY of its internal NetBIOS networking protocol over the Internet.
Click to expand...
 
Confused, I need to start running all my posts by you for spelling, grammar, and link corrections. 😛

😉 😀 LOL
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top