Posts

Posts uit juni, 2008 tonen

Software - Cisco VPN Client update v5.0.03.0530 available

Afbeelding
Hi there, Just discovered that Cisco released an updated version of their VPN Client. As I am running Windows Vista Business Edition on my notebook, and the previous client had a lot of (performance) issues, I was really pleased to read about the new version. Major "plus" about the new version: it is much faster in connecting to the remote VPN server (PIX / ASA / Concentrator). Where in the past making a connection took really about 20-30 seconds (and then sometimes would end in a "Failed to enable virtual adapter" error message), all of the connections work correct now and establishing a new VPN connection now only takes about 5 seconds or so. Regards, Rene

Tools - Uptime.exe

From Microsoft's Knowledge Base, article number 232243 : SUMMARY A new tool, Uptime.exe, is available for displaying system availability. Uptime.exe can be used to display the current uptime of the local or remote system. Optionally, it can also scan the Event log for key system events such as system restart or computers that are not responding (hanging). Where possible, it also calculates system availability. It is primarily intended for Windows NT Server 4.0 Service Pack 4 or later, though it operates in limited fashion on earlier versions. MORE INFORMATION Uptime.exe is a standalone program. To install the tool, simply copy the file into your Windows NT directory. You may then run the tool at a command prompt. Despite the fact that this tool was originally written for WinNT4 SP4, it is still very handy! You can download it at the article page, mentioned at the top. Regards, Rene

Lessons Learned - Cisco ASA 5510 and TCP request discarded

Hi there, Some weeks ago , I mentioned having had some trouble trying to figure out why a Cisco ASA would allow traffic TO the interface (ie, for using SSH) and not THROUGH the interface (to reach a server on the LAN, from the outside). I also mentioned the solution there: when permitting traffic through the outside-interface, always mention "interface" in the static-statement instead of the IP-address. Today, I ran into this problem again. But, slightly different this time (of course). The previous time, we were dealing with a single public IP address setup in a SOHO office. So, the customer had only one public IP address. My conclusion after troubleshooting that setup was, that you cannot use the exact public IP but have to use the "interface"-keyword instead. This time, this customer does really have a business internet setup, with a routed subnet on the outside. Because I have multiple static's in this config, I decided to use the real public IP addres