RE: POP 3 Errors/Warnings

Server MTU is 1472, Router MTU was 1468. After adjusting the issue seems to
be resolved. Thanks for the help.

"Terence Liu [MSFT]" wrote:

Hello Customer,

Thanks for your kindly update.

In my last reply, I mean you have to test out the MTU value of your SBS
server and Route. Then you have to set these two in the same value. This
problem has no relationship with ISP Route MTU value.

You can find the method how to set the MTU value for SBS server in my last
reply.

If the issue persists after the two values are same, follow these steps:

Please try to setup the DNS on the SBS server to check if it is a
DNS issue and let me know the result.

1. Click "Start", point to "Administrative Tools", and then click "DNS".

2. Right-click the server object in DNS, and then click "New Zone".

3. Click "Next" on the first page of the New Zone Wizard.

4. On the "Zone Type" page, click "Primary zone", and then click "Next"

5. On the "Active Directory Zone Replication Scope" page, click "To all
domain controllers in the Active Directory domain", and then click "Next".

6. On the "Forward or Reverse Lookup Zone" page, click "Forward lookup
zone", and then click Next.

7. On the "Zone Name" page, type the ISP Pop3 mail server FQDN, and then
click "Next". For example, type "pop3.isp.com" (without the quotation
marks), and then click "Next".

8. On the "Dynamic Update" page, click "Do not allow dynamic updates", and
then click "Next",

9. Click "Finish" to complete the wizard.

10. Double-click "Forward Lookup Zones", and then click the new zone.

11. Right-click the new zone, and then click "New Host (A)".

12. In the "New Host" dialog box, leave the "Name" box empty, type the
server's internal IP address in the "IP address" box, and then click "Add
Host".

13. Please open a command prompt window, and then run the ipconfig
/flushdns command to renew the DNS record.

NOTE: If the IP address of the POP3 server changes (if the POP3 server does
not have static IP), the POP3 connector will still fail.

If the issue still persists, collect some more information for further
investigation:

1. Please enable the service logging at Server Management - > Pop3
connector Manager -> Troubleshooting Tab -> Modify the Logging level to
Max.
2. Click Start -> Run, type EVENTVWR.MSC and click OK.
2. Select the Application Event log, right click it and select "Save Log
File As"
3. Save it as .evt file.
4. Export System Event Log too.
5. Send log file to my working mailbox: v-terliu@xxxxxxxxxxxxx

I appreciate your time and look forward to hearing from you.

Best regards,

Terence Liu(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.

--------------------
| Thread-Topic: POP 3 Errors/Warnings
| thread-index: Acb5BpyoOFjf1s1AQOuIC/cI6vzzXQ==
| X-WBNR-Posting-Host: 216.153.227.51
| From: =?Utf-8?B?TEREMTU=?= <LDD15@xxxxxxxxxxxxxxxxxxxxxxxxx>
| References: <5F5EE622-BF9C-4310-8EB1-A1AF60567DF7@xxxxxxxxxxxxx>
<U#E$vqO#GHA.4992@xxxxxxxxxxxxxxxxxxxxx>
| Subject: RE: POP 3 Errors/Warnings
| Date: Thu, 26 Oct 2006 06:57:02 -0700
| Lines: 248
| Message-ID: <C70CB910-A6BB-4B70-B683-6A0A00BEFE4F@xxxxxxxxxxxxx>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
| Newsgroups: microsoft.public.windows.server.sbs
| Path: TK2MSFTNGXA01.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:308183
| NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| Thank you for your time. I have some interesting observations for you.
|
| Ping <SBSServer> -f -l <packet_Size> from client clips out at 1472 as you
| indicated.
|
| Ping <POPServer> -f -l <packet_Size> from SBS server is a little more
| complicated and as follows:
|
| packet_size > 1440 - Result: Packet needs to be fragmented but DF set
| 1440 >= packet_size >= 1025 - Result: Request Timed Out
| packet_size < 1024 - Result: Reply from ~ TTL=128
|
| Point is there seems to be some sort of hole between 1024 and 1440 where
I
| cannot get a response from the server.
|
| Moving on we have a netGear FVS318 router with adjustable MTU. Originally
it
| was set to default of 1468. I changed it to 1500. Essentially I have the
same
| result except to upper limit on this hole changed to 1472.
|
| So I didn't get into the registry settings yet becuase the results I
recieve
| are different then what you had originally discribed. It would appear to
me
| that the ISP has an MTU of 1024 (this is a guess based upon my
observations).
| Should I confirm this with them and set the router and SBS server
accorningly?
|
| Thanks.
|
| "Terence Liu [MSFT]" wrote:
|
| > Hello Customer,
| >
| > Thank you for posting here.
| >
| > From your post, I understand that you got Event Log Errors of 1019,
1023,
| > 1035 & 1052, 1053 about POP3 connector in SBS 2003 Server environment.
If I
| > am off base, please feel free to let me know.
| >
| > After analyzing, these Errors log not point to one problem: the main
cause
| > of the 1019, 1023, 1025 issue is most possibly the router
incompatibility
| > with the Windows Server, and issue of 1052 and 1053 is most possibly
caused
| > by some emails are sent to your Global POP3 mail box via BCC.
| >
| > Please understand that our partner newsgroup is an issue based service,
| > meaning we usually respond to one question/issue per post. This will
lessen
| > the confusion for both of us, as well as ensure that our results are
| > accurate and not a result of a test for a different question.
Therefore, I
| > will work with you on the first question in this post. Regarding the
| > additional question(s), please open a new post so that the dedicated MS
| > engineer can help you on it in a more efficient manner.
| >
| > According to my knowledge, the 1019, 1023, 1035 events are mostly
caused by
| > incompatibility between the router and the Windows Server, that is, the
| > Maximum Transmission Unit (MTU)'s difference on the Windows Server and
| > hardware router. This issue may appear on Linksys router
BEFVP41/BEFSR41
| > and other similar ones.
| >
| >
| > Hence, I suggest performing the following steps to determine the MTU
| > setting:
| >
| > On the SBS server:
| > 1). To get the MTU Size maximum, you may need to have the following
command
| > on one of internal client connected to SBS server directly.
| > ping <SBS_IP_address> -f -l <packet_size>
| > and on SBS server, please ping the POP3 mail server with following
command
| > ping <POP3MailServer_IP_address> -f -l <packet_size>
| > Being:
| > <SBS_IP_address or POP3MailServer_IP_address > - the IP address from
the
| > internal network.
| > <packet_size> - the packet size to test the maximum MTU packet size.
| > You can use some <packet_size> parameters to get the packet ideal size.
| > This can be identified by the ping results, for example, ping
192.168.18.8
| > -f -l 5000
| > If the ping result is like below:
| >
| > Pinging [192.168.18.8] with 5000 bytes of data:
| > Packet needs to be fragmented but DF set.
| > Packet needs to be fragmented but DF set.
| > Packet needs to be fragmented but DF set.
| > Packet needs to be fragmented but DF set.
| > Ping statistics for 192.168.18.8:
| > Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
| >
| > You may need to decrease the <packet_size> until encounter a non
fragmented
| > packet size the link can answer like below:
| >
| > Pinging [192.168.18.8] with 1472 bytes of data:
| > Reply from 192.168.18.8: bytes=1472 time<1ms TTL=128
| > Reply from 192.168.18.8: bytes=1472 time<1ms TTL=128
| > Reply from 192.168.18.8: bytes=1472 time<1ms TTL=128
| > Reply from 192.168.18.8: bytes=1472 time<1ms TTL=128
| > Ping statistics for 192.168.18.8:
| > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
| > Approximate round trip times in milli-seconds:
| > Minimum = 0ms, Maximum = 0ms, Average = 0ms
| >
| > Or else, in this case, the maximum MTU Size is 1472. It is the by
default
| > number for SBS 2k3 server.
| >
| > If the router Maximum MTU size is smaller than the one on the SBS
server,
| > you may need following steps:
| > Modifying the MTU Size:
| > 1)Go to the key:
| >
KEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfa
| > ces
| > 2)Go the key corresponding to the NIC GUID
| > 3) Create a Dword parameter 'MTU' with the value small than router size
| > 4) Restart the client machine
| >
| > References:
| > Diagnoses and Treatment of Black Hole Routers
| > http://support.microsoft.com/?id=159211
| > TCP/IP and NBT Configuration Parameters for Windows XP
| > http://support.microsoft.com/?id=314053
| >
| > If the issue persists, collect some more information for further
| > investigation:
| > 1. Confirm whether the issue appears on the particular mailbox only.
| > 2. Dump attributes of the problematic user and a good one.
| > Both CSVDE and LDIFDE can dump user attributes, for your convenience, I
| > would like to list the following related information for your refer:
| >
| > XADM: How to Perform a Dump of a Container or Object in Exchange 2000
| > http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q255253
| > Note: This article is also applied for Exchange 2003.
| >
| > How to use Csvde to import contacts and user objects into Active
| > http://support.microsoft.com/?id=327620
| >
| > 3. Check the application log with diagnostic logging enabled for pop3
| > connector.
| >
| > To enable the logging:
| > a. Click Start, and then click Server Management.
| > b. Expand Advanced Management, and then click POP3 Connector Manager.
| > c. In the right pane, click Open POP3 Connector Manager.
| > d. Click the Troubleshooting tab, and then click Maximum in the Logging
| > level list.
| > e. In the Exchange mailbox list, click a mailbox where you want
| > undeliverable e-mail messages sent to, and then click OK.
| > f. Click Yes on the following message that appears:
| > Changes to the logging level do not take effect until the Microsoft
| > Connector for POP3 Mailboxes service is restarted. Restarting the
service
| > temporarily interrupts the download of mail until the service starts
again.
| > To restart the service now, click Yes. Otherwise, click No.
| > g. Click Open POP3 Connector Manager, and then click the Scheduling
tab.
.

Relevant Pages

  • RE: SBS2003 Standard Server Cannot Access Webpages.
    ... It appears that the router is the root cause, but it's weird that only the ... web traffic initiated from the SBS Server is blocked by the router. ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • Re: VPN Question
    ... I have VPN access into another domain ... However, to administer that server, you don't have to use ... >>> internal router and DHCP is handled by the SBS server. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 R2 Setup for T1 and Web Site Hosting
    ... means by definition that they will supply a router that handles the ... As far as the website, I will recommend they go to an outside host, ... the SBS server is also their main company server. ...
    (microsoft.public.windows.server.sbs)
  • Re: Email....what to do part2 :)
    ... If you've run the Configure Email and Internet Connection wizard ... SBS server so be sure to have the appropriate number of SBS CALs. ... router is handling the DHCP ...
    (microsoft.public.windows.server.sbs)
  • RE: VPNs in SBS2003 using ISA.
    ... To determine whether the failure is caused by your local router, ... Please temporarily place a client directly connected to the external NIC ... >> Server to a simple hub and connect the client to the same hub. ... >> the same subnet as the external network adapter of the SBS Server. ...
    (microsoft.public.windows.server.sbs)