| Event ID | 225 |
| Source | Symantec Web Security server |
| Description | No DNS servers found |
| Event Information | According to Symantec Resolution: If the server has been infected by a variant of W32.Nimda, then you must reinstall all TCP/IP related hardware drivers and protocols. If the server has not been infected by a variant of W32.Nimda, then follow the steps that apply to your servers operating system to fix the problem: Windows NT: 1.Right-click the Network Neighborhood icon on the Desktop, and then click Properties. 2.Click the Protocols tab, and then click TCP/IP Protocol. 3.Click Properties. 4.Click the DNS tab, and verify that both the Host Name and Domain boxes have the appropriate entries and that at least one valid DNS server is listed in the DNS Service Search Order list. 5.Consult your network administrator or Internet service provider (ISP) if you are unsure of the settings that should be used here. Make the necessary changes. 6.Click OK. 7.Restart the server. 8.Restart Symantec Web Security. Windows 2000: 1.Right-click My Network Places, and then click Properties. 2.Right-click Primary Network Connection, and then click Properties. 3.Click Internet Protocol (TCP/IP), and then click Properties. 4.Verify that the appropriate IP address for a valid DNS server is selected. Consult your network administrator or Internet service provider (ISP) if you are unsure of the settings that should be used here. Make the necessary changes. 5.Click Advanced. 6.On the DNS tab, check Append these DNS Suffixes. Ensure that the correct suffix is set at the bottom of this screen. 7.Click OK. 8.Restart the server. 9.Restart Symantec Web Security. |
| Reference Links | Event ID 225 of Source Symantec Web Security server |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.