Access control, Antivirus, Antivirus software, Application security, Auditing, Authentication, Biometrics, Current threats, cybersecurity, Digital certificates, Encryption, Endpoint security, Firewall, Firewalls, Forensics, Hacking, Identity & Access Management, Incident response, Information risk management, Information security, Intrusion management, ISA Server, malware, McAfee, Password, Patch management, patching, PEN testing, Platform Security, Risk management, Secure Coding, Security in 2010, Security management, Security products, Security Program Management, Security tokens, SFTP, Single sign-on, Spyware, SSL, SSL/TLS, Symantec, Trojans, User Permissions, Veritas, Viruses, vulnerability management, Web security, Windows Security, worms VIEW ALL TAGS
I am setting up a Web SSL VPN for remote access across my WAN. Can someone explain why SSL VPNs use Port 443? Can I use any other port?
The problem is that HTTPS 443 port isn't accessible from interned, but it is open in local network. Our iSeries is connected to inet via L2TP withot IPSec. If no packet filters are active, nmap shows that ports 25, 80, 110 and even 10322 (WAS admin console) have state 'open' on internet ip...
This is a weird one and I don't know what to make of it or what next steps to take to troubleshoot it: Basically, my WiFi NIC has all of a sudden started blocking port 443 (SSL). I have a Dell Inspiron 300m laptop (running Windows XP Pro SP2) with a TrueMobile 1300 WLAN card; earlier today it...