Search Again: QDNS and Sonic Wall From: Gary Richter Date: Friday, January 28, 2005 Time: 1:37:50 pm Probably off topic and a stretch that somebody might know what is going on...but unless I ask we will never know will we...<snicker> Latest and greatest QDNS Pro with 9.3.0 Bind with the -4 mod on an xserve with 10.3.7 QDNS and EIMS on 216.210.202.66 Sonic Wall TZ170 on 216.210.202.125 My fire wall is reporting lines like this ever couple of minutes: 01/28/2005 10:24:52.560 - UDP packet from LAN dropped - Source:216.210.202.66, 53, LAN - Destination:216.210.202.125, 1638, LAN - Port: 1638 - Notice port 53 (name service) from .66, but the port it is trying to get to is 1630 and that number changes by 1 every time this error shows up. follow a little less frequently but ever 5 minutes by Source:216.210.202.66, 25, LAN - Destination:216.210.202.125, 2203, LAN - Port: 2203 - Notice port 25 (email) from .66 but the port it is trying to get to is 2203, and again it changes by 1 port number on the next error. -------- Anybody have a clue why either QDNS using port 53 would be trying to talk to the sonicwall? or and totally off topic why EIMS would be doing the same? The thing that is odd is I have the sonicwall config'd to go outbound from .66 to .126 with no restrictions. .126 is the slave QDNS install to the master on .66 FYI the sonicwall has in place for a long time and have no issues other then these showing up. =============================================== Gary Richter, President PanaVise Products, Inc. 7540 Colbert Dr. Reno, Nevada 89511 Ph: 775.850.2900 Fx: 775.850.2929 Email: grichter@panavise.com http://www.panavise.com ===============================================

Messages In This Thread: QDNS and Sonic Wall by Gary Richter on Jan 28, 2005 at 1:37:50 pm Re: QDNS and Sonic Wall by Men & Mice Support on Jan 28, 2005 at 11:24:04 pm