Carlyle Sutphen said: > Let me echo Jack with a bit of emphasis. Look, some of you > are publishing the IP addresses of your routers, the make and version > of your routers, WHICH PORTS YOU ARE OPENING
You can get that from a simple port scan. >and the ip > addresses and operating systems of the machines behind your > routers. Hmmm. Mostly MS Windows (expected) and generally the default IP range for the NAT devices. Not exactly rocket science. Having actual numbers instead of aaa.aaa.aaa.aaa and bbb.bbb.bbb.bbb help most of the time because the person needing help assumes it doesn't matter and the person offering help must assume that they know what they are doing. If I told you that I was trying to connect to my machine behind a NAT device using aaa.aaa.aaa.aaa:1 you have no way of knowing if I'm posting the external address of the NAT device or the internal address of the machine. [snip] > > Please look into VPN and SSH. Use VNC exclusively through one of > these. That I don't disagree with. > Also, educate yourselves on intrusion detection. Turn up the logging > verbosity on your routers and check them regularly. You may well be > surprised to see what is going on "down there" At the point the NAT device is logging it, it is stopping it. I personally don't see much use about getting worked up about all the MS Windows machines spewing broadcast packets out on NetBIOS ports. Or for that matter all the worms trying to talk to my non-existent MSSQL server. Much better advice would be to check the logs of whatever Internet facing services you are running. -- William Hooper _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
