Messages

1

General discussion forum / Novice user - where do I go to get started (K3 twin)

« on: 2021-03-06, 16:39:06 »

I'd like to do the K3 twin thing (K3 and K3/0), with a KPA500/KAT500.  And N1MM.  CW and SSB - hopefully with my WinKeyer box (or emulation of same).

'Seems like a prototypical use case, and in my Googling I find lots of posts about particular issues that folks see arise in their setups, but I haven't yet found a step-by-step setup guide to follow.

Many thanks,

/Bill, K2PO

2

Configuration of Routers, Firewalls, etc / Novice problems getting inbound traffic thru router, etc

« on: 2014-05-03, 19:48:16 »

This should be easier than it is.

I got the latest RemoteRig pair a few weeks ago, with a K3/0-Mini.

On the LAN network, everything plays together great.  The RR boxes are 192.168.2.227 and .228.

I have a Belkin router, and opened ports 13000, 13001 and 13002.

I have a static IP address.

Yet no joy.

I've tried scanning the system from elsewhere on the internet, using a port scanner (http://www.t1shopper.com/tools/port-scan/ ).  In particular, I have it scan the static IP address, at ports 13000-13005. All yield the same result (not responding...)

I then tried putting 192.168.2.228 in the DMZ.  Same result.

I then tried shutting off the Belkin router firewall altogether.  Same result.

I then realized there's Windows firewall to worry about (I'm running Win7).  I disabled it (both Domain Profile, Public Profile, and Private Profile).  Same result.

I then realized I have Microsoft Security Essentials running (anti-virus software), so disabled it.  Same result.

So I'm stumped.  It seems like it shouldn't be this hard - there's probably something simple I'm missing.

One final clue - the router keeps a log of incoming possible attacks.  When I attempt the scans of ports 13000-13005 from outside the network, the security log identifies only the probes of ports 13003, 13004 and 13005 as threatening.  So it it treating 13000-13002 differently than others.  Below is the Belkin log report.
    Sat May 3 09:55:01 2014
    =>Found attack from 208.64.252.230.
    Source port is 55309 and destination port is 13003 which use the TCP protocol.
    Sat May 3 09:55:01 2014
    =>Found attack from 208.64.252.230.
    Source port is 60100 and destination port is 13004 which use the TCP protocol.
    Sat May 3 09:55:01 2014
    =>Found attack from 208.64.252.230.
    Source port is 43218 and destination port is 13005 which use the TCP protocol.

The only thing I can think of is something on the ISP side.  (Yet the attack log indicates the probes of 13000-13002 are getting some respect, somewhere...)

'Suggestions?

tnx,

/Bill, K2PO
Portland, OR