1433 is the default Microsoft SQL Server port. Someone is trying to probe your machine for the presence of this software package. If your machine were listening on port 1433 then the remote computer would most likely begin a sequence of well known probes to attempt to hijack your database engine.
You can verify that port 1433 is not active on your machine by loading a command line and typing:
On a windows machine
C:\>netstat -an
Look for port 1433. On a linux / UNIX machine:
#netstat -an | grep 1433
Bottom line... I wouldn't worry about it. Get a firewall if you don't already have one. Take care.
I'm safe, thanks to ZoneAlarm, the world's greatest freeware program.
Here's what my ports look like under netstat -an
C:\WINDOWS\Desktop>netstat -an Active Connections Proto Local Address Foreign Address State TCP 0.0.0.0:1030 0.0.0.0:0 LISTENING TCP 0.0.0.0:135 0.0.0.0:0 LISTENING TCP 0.0.0.0:5000 0.0.0.0:0 LISTENING TCP 63.155.104.7:9322 0.0.0.0:0 LISTENING TCP 63.155.104.7:139 0.0.0.0:0 LISTENING TCP 127.0.0.1:1026 0.0.0.0:0 LISTENING TCP 127.0.0.1:1029 0.0.0.0:0 LISTENING UDP 63.155.104.7:15483 *:* UDP 63.155.104.7:137 *:* UDP 63.155.104.7:138 *:* UDP 127.0.0.1:1616 *:* UDP 127.0.0.1:2132 *:* UDP 127.0.0.1:1900 *:*
Just now I got another probe. Does FR send to its clients? Jim Robinson?
The firewall has blocked Internet access to your computer (TCP Port 1433) from 203.248.195.112 (TCP Port 4132). Time: 10/19/2002 8:24:00