检讨ISA2004 VPN部署失败原因

[ 2005/07/14 13:02 | by gOxiA ]

部署前看了些资料,发现并不难,于是开始测试。

搭建好虚拟平台,使用2003SP1系统,ISA2004标准版

安装后没发现什么异常,然后部署VPN,启用后死活就是无法连接上,到底是哪里错了?哪里的配置都没有错啊!只是日志中总有什么防火墙无法写入到注册表,我以为是内存太少造成的也就没有理会,继续分析。就这样折腾了好几天,最后跟一个朋友在QQ谈起来问及补丁的事情才发现,NND问题原来出在没有安装补丁的原因,因为2003SP1的安全级别更高所以会限制ISA的一些运行机制,必须安装ISA2004SP1补丁后才可以,最后急忙打上补丁果然一切OK了,我考!就是一个这个小小的疏忽,让我折腾了几天都没搞明白为什么我错误配置都是对的他NND就是连接不上。

所以我告诫自己,以后一定要查看运行说明,2003SP1看来真的是和自家的产品也过意不去。

ISA2004 SP1的下载地址是:

http://www.microsoft.com/downloads/details.aspx?displaylang=zh-cn&FamilyID=69c5d85c-5c80-473c-9cb4-60dda75d568d

# Example MySQL config file for small systems.
#
# This is for a system with little memory (<= 64M) where MySQL is only used
# from time to time and it's important that the mysqld daemon
# doesn't use much resources.
#
# You can copy this file to
# /etc/my.cnf to set global options,
# mysql-data-dir/my.cnf to set server-specific options (in this
# installation this directory is /usr/local/var) or
# ~/.my.cnf to set user-specific options.
#
# In this file, you can use all long options that a program supports.
# If you want to know which options a program supports, run the program
# with the "--help" option.

# The following options will be passed to all MySQL clients
[client]
#password = your_password
port  = 3306
socket  = /tmp/mysql.sock

# Here follows entries for some specific programs

# The MySQL server
[mysqld]
old_password
basedir=C:/mysql
datadir=C:/mysql/data

port  = 3306
socket  = /tmp/mysql.sock
skip-locking
key_buffer = 16K
max_allowed_packet = 1M
table_cache = 4
sort_buffer_size = 64K
read_buffer_size = 256K
read_rnd_buffer_size = 256K
net_buffer_length = 2K
thread_stack = 64K

# Don't listen on a TCP/IP port at all. This can be a security enhancement,
# if all processes that need to connect to mysqld run on the same host.
# All interaction with mysqld must be made via Unix sockets or named pipes.
# Note that using this option without enabling named pipes on Windows
# (using the "enable-named-pipe" option) will render mysqld useless!
#
#skip-networking
server-id = 1

# Uncomment the following if you want to log updates
#log-bin

# Uncomment the following if you are NOT using BDB tables
#skip-bdb

# Uncomment the following if you are using InnoDB tables
#innodb_data_home_dir = /usr/local/var/
#innodb_data_file_path = ibdata1:10M:autoextend
#innodb_log_group_home_dir = /usr/local/var/
#innodb_log_arch_dir = /usr/local/var/
# You can set .._buffer_pool_size up to 50 - 80 %
# of RAM but beware of setting memory usage too high
#innodb_buffer_pool_size = 16M
#innodb_additional_mem_pool_size = 2M
# Set .._log_file_size to 25 % of buffer pool size
#innodb_log_file_size = 5M
#innodb_log_buffer_size = 8M
#innodb_flush_log_at_trx_commit = 1
#innodb_lock_wait_timeout = 50

[mysqldump]
quick
max_allowed_packet = 16M

[mysql]
no-auto-rehash
# Remove the next comment character if you are not familiar with SQL
#safe-updates

[isamchk]
key_buffer = 8M
sort_buffer_size = 8M

[myisamchk]
key_buffer = 8M
sort_buffer_size = 8M

[mysqlhotcopy]
interactive-timeout

实际上最主要的就是添加红色部分的设置。

备份和清除大型事件日志

[ 2005/07/09 10:02 | by gOxiA ]

描述

如果事件日志文件的大小大于 20 MB,就将其备份和清除。


脚本代码
strComputer = "."
Set objWMIService = GetObject("winmgmts:" _
   & "{ impersonationLevel=impersonate, (Backup, Security) }!\\" _
       & strComputer & "\root\cimv2")
Set colLogFiles = objWMIService.ExecQuery _
   ("Select * from Win32_NTEventLogFile")
For each objLogfile in colLogFiles
   If objLogFile.FileSize > 100000 Then
      strBackupLog = objLogFile.BackupEventLog _
          ("c:\scripts\" & objLogFile.LogFileName & ".evt")
      objLogFile.ClearEventLog()
   End If
Next

分页: 438/474 第一页 上页 433 434 435 436 437 438 439 440 441 442 下页 最后页 [ 显示模式: 摘要 | 列表 ]