🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: alt.games.quake3
Article #286221

Re: Locating Quake3 servers with Superscan port scanner?

#286221
From: Mark
Date: Tue, 17 Jan 2006 20:47
6 lines
1515 bytes
"NuQ" <anon@anon.com> wrote:
>
> I think most people use the in-game server browser, or GameSpy, or 
> All-Seeing Eye and sort by lowest ping.  No need to use Superscan.

(responded in new thread "Locating Quake3 Servers?")
Technical Details
Message-ID: <Z7ydnehgqtQjylDenZ2dnUVZ_sCdnZ2d@w-link.net>
Path: mbox-mo1.pugleaf.net!number1.nntp.dca.giganews.com!local01.nntp.dca.giganews.com!nntp.w-link.net!news.w-link.net.POSTED!not-for-mail
References: <RKKdnbMWWsiWG1TeRVn-oQ@w-link.net> <43cbe9ad$0$6393$892e7fe2@authen.yellow.readfreenews.net>

Show Full Headers
Complete Article Headers
Path: mbox-mo1.pugleaf.net!number1.nntp.dca.giganews.com!local01.nntp.dca.giganews.com!nntp.w-link.net!news.w-link.net.POSTED!not-for-mail
NNTP-Posting-Date: Tue, 17 Jan 2006 14:46:54 -0600
From: "Mark" <nospam@thanksanyway.org>
Newsgroups: alt.games.quake3
References: <RKKdnbMWWsiWG1TeRVn-oQ@w-link.net> <43cbe9ad$0$6393$892e7fe2@authen.yellow.readfreenews.net>
Subject: Re: Locating Quake3 servers with Superscan port scanner?
Date: Tue, 17 Jan 2006 12:47:05 -0800
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2670
X-RFC2646: Format=Flowed; Response
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
Message-ID: <Z7ydnehgqtQjylDenZ2dnUVZ_sCdnZ2d@w-link.net>
Lines: 8
NNTP-Posting-Host: 207.244.150.30
X-Trace: sv3-gJKNErsoxvk8/Ju+X/9bOgqf622ryqzXlsJ8BO9yjiFrnsaREsUvHxhRL74VeBNeho7B2Lgm+M5jtE+!K1c9Nbh2GmHhxLTMrnvu4JItHVLKkmLgyr3cUMaapddYbotshiYwPwlkAihwXrYD7FEozTAcnwY6!jC/ZBfbfU5k=
X-Complaints-To: abuse@w-link.net
X-DMCA-Complaints-To: abuse@w-link.net
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.32
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit