| Subject: Re: The IP address for ssl @ Berkeley? |
| From: John |
| Date: 02/04/2004, 21:25 |
In article <m6ebc.1675$6v4.335@newssvr32.news.prodigy.com>, Mike Bader
<mdbader@flash.net> writes
kosh.ssl.berkeley.edu 128.32.18.151
shserver2.ssl.berkeley.edu 66.28.250.122
setiathome.ssl.berkeley.edu 128.32.18.151
sagan.ssl.berkeley.edu 128.32.18.166
alien.ssl.berkeley.edu 128.32.18.176
iosef.ssl.berkeley.edu 128.32.18.175
milkyway.ssl.berkeley.edu 128.32.18.165
serendip.ssl.berkeley.edu 128.32.18.162
setidata.ssl.berkeley.edu 128.32.18.155
--
Thanks Mike. I may now find out why SETI Queue works via my company
internet connection and not Demon. Despite the fact that Demon Internet
allows me to do everything else.
John
--
John Clark
In the "reply to", replace either "fredclark" or "Workgroup" with
"jonclark" for direct e-mail.