|
| |||||||||
| Tags: dns, port, port formward, sbs, server, windows server |
![]() |
| | Thread Tools | Search this Thread |
|
#1
| |||
| |||
| An error on DNS Port 53 by Best Practices Analizer
I use SBS 2008, --> Best Practices Analzer: It reports an error: The DNS Server service should listen on DNS port 53, but that port is owned by the process. ------------------- I can't find any infommation on this error message. This is reporting back to the SBS console as an exception, and I see the red flag every time I sign on. How do I correct this ? thx |
|
#2
| ||||
| ||||
| re: An error on DNS Port 53 by Best Practices Analizer
According to recent tests, released this week on a security list, allow Windows to resolve the DNS server address, it opens up a huge gap in most personal firewalls known as Tiny Personal Firewall 2.0 or AtGuard (and possibly others) . As the firewall allows any communication through the port 53 (UDP), to facilitate name resolution, a Trojan can use this to connect through that port and then send and receive commands, firewall without warning. The consequences of this are easy to grasp. |
![]() |
|
| Thread Tools | Search this Thread |
| |
Similar Threads for: "An error on DNS Port 53 by Best Practices Analizer" | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Port Forwarded but Still get Port Checker Error | Vayya | Networking & Security | 5 | 26-06-2010 06:16 PM |
| DC Demotion Best Practices | ADVIS | Active Directory | 2 | 19-10-2009 06:57 PM |
| AD Sites and Services Best Practices | Luiz | Active Directory | 13 | 11-09-2009 08:47 PM |
| Best practices for DNS AD on domain controllers | Andrea | Windows Server Help | 6 | 25-11-2008 06:01 AM |
| Missing port types : local port and Standard TCP/IP port | programmer_not_admin | Windows XP Support | 5 | 28-12-2006 07:38 PM |