Prev: ISA 2004 cisco SSL vpn client
Next: Join a domain
From: chace zhang on 19 Jul 2006 05:29 Hi, Thanks for your update. According to the internet header "[192.168.2.1] RDNS failed" Do they have a reverse lookup zone for 192.168.2.x on local DNS? If the zone exists. make sure that you can do Nslookup Set type=PTR 192.168.2.1 Exit If not, then check in the zone to see if a) The record exists b) Check to see the zone is set to secure dynamic updates c) The server's internal IP address is on the 192.168.2.x subnet (assuming 255.255.255.0 mask) Hope this helps, please let me know if there is anything that I can do for you. I look forward to hearing from you soon. -------------------- | From: "spm" <nospam(a)coco.dot.co.dot.uk> | Subject: Re: Sender ID Filtering vs. SBS Fax Server | References: <xn0eolmkjbvgt4000(a)news.microsoft.com> <oBfCOYapGHA.4188(a)TK2MSFTNGXA01.phx.gbl> <xn0eon1fa78ccv000(a)news.microsoft.com> <nSiStIzpGHA.6120(a)TK2MSFTNGXA01.phx.gbl> <xn0eoprpzmddq000(a)news.microsoft.com> <2v6fb21uac5jbap5epkaq8qberlner6qcq(a)4ax.com> <socfb2d0orrgfibqi0ghqaq38k0fq1gnsf(a)4ax.com> <xn0eopzln39h1i000(a)news.microsoft.com> <Nh27HxYqGHA.4612(a)TK2MSFTNGXA01.phx.gbl> <xn0eou0dp9ro3q000(a)news.microsoft.com> <tVQDv1kqGHA.5464(a)TK2MSFTNGXA01.phx.gbl> | Organization: CoCo Systems Ltd. | User-Agent: XanaNews/1.18.1.3 | Message-ID: <xn0eovc202598f001(a)news.microsoft.com> | X-Ref: news.microsoft.com ~XNS:00000099 | MIME-Version: 1.0 | Content-Type: text/plain; charset=iso-8859-1 | Newsgroups: microsoft.public.windows.server.sbs | Date: Tue, 18 Jul 2006 03:54:18 -0700 | NNTP-Posting-Host: cocohome.co.uk 80.229.190.27 | Lines: 1 | Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP05.phx.gbl | Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:282230 | X-Tomcat-NG: microsoft.public.windows.server.sbs | | Hi Chace, | | As I reported to you by e-mail, the server has 2 NICs, and the IP | addresses of both are in the IP list. | | -- | Regards, | Steve. |
From: spm on 19 Jul 2006 11:20 Hi Chace, The server didn't have a PTR record set up in its DNS, so I have now added one and it resolves OK. I will see what happens next time we receive a fax, but I'm not terribly hopeful this is the solution, as I would have thought the "RDNS failed" entry in the message headers is for information only and is a result of setting the "Perform reverse DNS lookups on incoming messages" option for the SMTP Virtual Server. Is this option not independent of the Sender ID Filtering? I guess we'll soon find out... -- Regards, Steve.
From: chace zhang on 19 Jul 2006 22:15 Hi Steve, Regarding event 7519, Intelligent Message Filter writes this event when it cannot filter a message. Possible causes are corrupted or malformed header. So I think it worth to try. I will be here waiting for your reply. Thanks for your time. Have a nice day! Best Regards, Chace Zhang (MSFT) Microsoft CSS Online Newsgroup Support Get Secure! - www.microsoft.com/security ===================================================== This newsgroup only focuses on SBS technical issues. If you have issues regarding other Microsoft products, you'd better post in the corresponding newsgroups so that they can be resolved in an efficient and timely manner. You can locate the newsgroup here: http://www.microsoft.com/communities/newsgroups/en-us/default.aspx When opening a new thread via the web interface, we recommend you check the "Notify me of replies" box to receive e-mail notifications when there are any updates in your thread. When responding to posts via your newsreader, please "Reply to Group" so that others may learn and benefit from your issue. Microsoft engineers can only focus on one issue per thread. Although we provide other information for your reference, we recommend you post different incidents in different threads to keep the thread clean. In doing so, it will ensure your issues are resolved in a timely manner. For urgent issues, you may want to contact Microsoft CSS directly. Please check http://support.microsoft.com for regional support phone numbers. Any input or comments in this thread are highly appreciated. ===================================================== This posting is provided "AS IS" with no warranties, and confers no rights. -------------------- | From: "spm" <nospam(a)coco.dot.co.dot.uk> | Subject: Re: Sender ID Filtering vs. SBS Fax Server | References: <xn0eolmkjbvgt4000(a)news.microsoft.com> <oBfCOYapGHA.4188(a)TK2MSFTNGXA01.phx.gbl> <xn0eon1fa78ccv000(a)news.microsoft.com> <nSiStIzpGHA.6120(a)TK2MSFTNGXA01.phx.gbl> <xn0eoprpzmddq000(a)news.microsoft.com> <2v6fb21uac5jbap5epkaq8qberlner6qcq(a)4ax.com> <socfb2d0orrgfibqi0ghqaq38k0fq1gnsf(a)4ax.com> <xn0eopzln39h1i000(a)news.microsoft.com> <Nh27HxYqGHA.4612(a)TK2MSFTNGXA01.phx.gbl> <xn0eou0dp9ro3q000(a)news.microsoft.com> <tVQDv1kqGHA.5464(a)TK2MSFTNGXA01.phx.gbl> <xn0eovc202598f001(a)news.microsoft.com> <P6eZkXxqGHA.4612(a)TK2MSFTNGXA01.phx.gbl> | Organization: CoCo Systems Ltd. | User-Agent: XanaNews/1.18.1.3 | Message-ID: <xn0eowxoh46utr000(a)news.microsoft.com> | X-Ref: news.microsoft.com ~XNS:0000009A | MIME-Version: 1.0 | Content-Type: text/plain; charset=iso-8859-1 | Newsgroups: microsoft.public.windows.server.sbs | Date: Wed, 19 Jul 2006 08:20:02 -0700 | NNTP-Posting-Host: cocohome.co.uk 80.229.190.27 | Lines: 1 | Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP03.phx.gbl | Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:282613 | X-Tomcat-NG: microsoft.public.windows.server.sbs | | Hi Chace, | | The server didn't have a PTR record set up in its DNS, so I have now | added one and it resolves OK. I will see what happens next time we | receive a fax, but I'm not terribly hopeful this is the solution, as I | would have thought the "RDNS failed" entry in the message headers is | for information only and is a result of setting the "Perform reverse | DNS lookups on incoming messages" option for the SMTP Virtual Server. | Is this option not independent of the Sender ID Filtering? I guess | we'll soon find out... | | -- | Regards, | Steve. |
From: spm on 20 Jul 2006 11:12 Hi Chace, I can now repoort that the 7519 events persist, even when an rDNS record is set up for the server. Some observations to note, however: 1. Even though a PTR record exists in the reverse lookup zone for the server (and manual nslookup's on the server succeed), the message headers for fax-server initiated emails still show 'RDNS failed' aftre the IP address. 2. If I turn off the "Perform reverse DNS lookups on incoming messages" option for the SMTP virtual server, the "RDNS failed" info disappears (as I would expect), but the 7519 events still persist. This would suggest that, as I suspected, rDNS lookups and the Sender Filter are independent. 3. I now note that the server name included in the fax-server email notifications is missing the hyphen character that actually exists in the real server name. Could this be significant? 4. I today received an alert (a disk activity alert, in fact, about an unrelated event re a temporarily-attached USB external drive) by email from the server. This alert email's header showed the source as "[127.0.0.1] RDNS failed", and the servername also missed the embedded hyphen, but in this case there was no 7519 event. The 7519 event only happens with fax-server notification emails. -- Regards, Steve.
From: chace zhang on 21 Jul 2006 05:09
Hi Steve, Thank you for update. I would have a deeper talk with other senior engineers. Here I suggest you schedule a non-business time to perform a clean boot of your Small Business Server. To perform a clean boot, follow the steps below: A. Click Start, click Run, type "msconfig" (without the quotation marks) and click OK. B. Select "Selective Startup" and remove the check box for "Load Startup Items". C. On the "Services" tab, click Enable All. D. Check "Hide all Microsoft Services", click Disable All and clear "Hide all Microsoft Services". E. Click the OK button and then Click Yes to restart your computer. F. Try again. I look forward to your update. Have a nice day. Best Regards, Chace Zhang (MSFT) Microsoft CSS Online Newsgroup Support Get Secure! - www.microsoft.com/security ===================================================== This newsgroup only focuses on SBS technical issues. If you have issues regarding other Microsoft products, you'd better post in the corresponding newsgroups so that they can be resolved in an efficient and timely manner. You can locate the newsgroup here: http://www.microsoft.com/communities/newsgroups/en-us/default.aspx When opening a new thread via the web interface, we recommend you check the "Notify me of replies" box to receive e-mail notifications when there are any updates in your thread. When responding to posts via your newsreader, please "Reply to Group" so that others may learn and benefit from your issue. Microsoft engineers can only focus on one issue per thread. Although we provide other information for your reference, we recommend you post different incidents in different threads to keep the thread clean. In doing so, it will ensure your issues are resolved in a timely manner. For urgent issues, you may want to contact Microsoft CSS directly. Please check http://support.microsoft.com for regional support phone numbers. Any input or comments in this thread are highly appreciated. ===================================================== This posting is provided "AS IS" with no warranties, and confers no rights. -------------------- | From: "spm" <nospam(a)coco.dot.co.dot.uk> | Subject: Re: Sender ID Filtering vs. SBS Fax Server | References: <xn0eolmkjbvgt4000(a)news.microsoft.com> <oBfCOYapGHA.4188(a)TK2MSFTNGXA01.phx.gbl> <xn0eon1fa78ccv000(a)news.microsoft.com> <nSiStIzpGHA.6120(a)TK2MSFTNGXA01.phx.gbl> <xn0eoprpzmddq000(a)news.microsoft.com> <2v6fb21uac5jbap5epkaq8qberlner6qcq(a)4ax.com> <socfb2d0orrgfibqi0ghqaq38k0fq1gnsf(a)4ax.com> <xn0eopzln39h1i000(a)news.microsoft.com> <Nh27HxYqGHA.4612(a)TK2MSFTNGXA01.phx.gbl> <xn0eou0dp9ro3q000(a)news.microsoft.com> <tVQDv1kqGHA.5464(a)TK2MSFTNGXA01.phx.gbl> <xn0eovc202598f001(a)news.microsoft.com> <P6eZkXxqGHA.4612(a)TK2MSFTNGXA01.phx.gbl> <xn0eowxoh46utr000(a)news.microsoft.com> <YxYIeJ6qGHA.4272(a)TK2MSFTNGXA01.phx.gbl> | Organization: CoCo Systems Ltd. | User-Agent: XanaNews/1.18.1.3 | Message-ID: <xn0eoyc28gkkxc000(a)news.microsoft.com> | X-Ref: news.microsoft.com ~XNS:0000009C | MIME-Version: 1.0 | Content-Type: text/plain; charset=iso-8859-1 | Newsgroups: microsoft.public.windows.server.sbs | Date: Thu, 20 Jul 2006 08:12:36 -0700 | NNTP-Posting-Host: cocohome.co.uk 80.229.190.27 | Lines: 1 | Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP03.phx.gbl | Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:282890 | X-Tomcat-NG: microsoft.public.windows.server.sbs | | Hi Chace, | | I can now repoort that the 7519 events persist, even when an rDNS | record is set up for the server. Some observations to note, however: | | 1. Even though a PTR record exists in the reverse lookup zone for the | server (and manual nslookup's on the server succeed), the message | headers for fax-server initiated emails still show 'RDNS failed' aftre | the IP address. | | 2. If I turn off the "Perform reverse DNS lookups on incoming messages" | option for the SMTP virtual server, the "RDNS failed" info disappears | (as I would expect), but the 7519 events still persist. This would | suggest that, as I suspected, rDNS lookups and the Sender Filter are | independent. | | 3. I now note that the server name included in the fax-server email | notifications is missing the hyphen character that actually exists in | the real server name. Could this be significant? | | 4. I today received an alert (a disk activity alert, in fact, about an | unrelated event re a temporarily-attached USB external drive) by email | from the server. This alert email's header showed the source as | "[127.0.0.1] RDNS failed", and the servername also missed the embedded | hyphen, but in this case there was no 7519 event. The 7519 event only | happens with fax-server notification emails. | | -- | Regards, | Steve. | |