我的WSUS 3.0服务器近期不能接收client端的连接。Application log中发现如下信息。
Event Type: Error
Event Source: Windows Server Update Services
Event Category: Clients
Event ID: 13042
User: N/A
Computer: WSUS01
Description: Self-update is not working.
经过研究，下面的方法可以解决问题。
Setting mailbox limits over 2GB in Exchange 2003
Exchange Server 2000/2003 allows the Exchange Administrator to set limits on the mailboxes of users in the Exchange Organization (read Setting Mailbox Limits, Working with Store Policies and Overwriting Mailbox Store Policy Limits for more info). Setting limits on the mailboxes help control the database size and plan for efficient backup, restore and maintenance tasks.
However, in most scenarios, there will always be users that think that they deserve more storage space than they were given in the first place. Some of these are VIPs, others just need it for their work, and the rest are simply trying to make their life easier.
So, whatever may be the reason, you might find yourself in need to configure higher mailbox limits for some users.
Well, up to this point all I did was to explain what you already know. However, there is one tricky bit:
When trying to configure mailbox limits higher than 2097151 KB the Exchange System Manager (ESM) or Active Directory Users and Computers (ADUC) snap-ins will not allow you to enter these higher limits.
You will receive an error saying: “The value for ‘Issue warning at (KB)’ is not valid. Specify a value from 0 through 2097151″.
The mailbox limits are actually Active Directory attributes. If you set a sample user’s mailbox limits and look at the user object with a tool such as LDP or Adsiedit.msc you will notice that they are:
Issue Warning = MDBStorageQuota
Prohibit Send = MDBOverQuotaLimit
Prohibit Send and Receive = MDBOverHardQuotaLimit
These limits are part of the UI, and NOT a hard coded limit on the attribute itself.
Solution
If the Ubuntu Server installer has set your server to use DHCP, you will want to change it to a static IP address so that people can actually use it.
Changing this setting without a GUI will require some text editing, but that’s classic linux, right?
Let’s open up the /etc/network/interfaces file. I’m going to use vi, but you can choose a different editor
sudo vi /etc/network/interfaces
For the primary interface, which is usually eth0, you will see these lines:
auto eth0
iface eth0 inet dhcp
As you can see, it’s using DHCP right now. We are going to change dhcp to static, and then there are a number of options that should be added below it. Obviously you’d customize this to your network.
auto eth0
iface eth0 inet static
address 192.168.1.200
netmask 255.255.255.0
network 192.168.1.0
broadcast 192.168.1.255
gateway 192.168.1.1
Now we’ll need to add in the DNS settings by editing the resolv.conf file:
sudo vi /etc/resolv.conf
On the line ‘name server xxx.xxx.xxx.xxx’ replace the x with the IP of your name server. (You can do ifconfig /all to find out what they are)
Now we’ll just need to restart the networking components:
sudo /etc/init.d/networking restart
Ping www.google.com. If you get a response, name resolution is working(unless of course if google is in your hosts file).
Really pretty simple.
