RE: Exchange 2003 and timeout errors on XP machines

To answer your questions, it happens to just about everyone, almost 40 users.
I have replaced and tested almost all the wires and everyone is on cat5e,
Everything via OWA works perfectly. There are no events that pertain to the
lose of connectivity on the server but only error 26 on the clients and then
a delay write error or faulting application in the applications that are
killed via the pop up from Outlook. I will reboot the server and see what
changes are made.

""Bill Peng [MSFT]"" wrote:

> Hi JK,
>
> Thank you for posting here and I'd like to provide the following info for
> your reference.
>
> First of all, will you please let me know your current Service Pack level?
> Have you installed SBS SP1 or MS 05-019?
>
> If yes, please refer to the following KB and make a call to our PSS support
> to obtain the Hotfix:
>
> Installing security update MS05-019 or Windows Server 2003 Service Pack 1
> may cause network connectivity between clients and servers to fail
> http://support.microsoft.com/kb/898060
>
> In addition, if the problem persists, please let me know:
>
> 1. Did the problem happen on all client computers?
> 2. After replacing 1 client computer's network cable, will the problem
> persists?
> 3. Are you able to open OWA to access the e-mails on the client or server?
> 4. Are there any error info in the Event Viewer?
>
> For the store.exe and w3wp.exe memory problem, I'd like to provide the
> following info for your reference:
>
> Store.exe will take as much memory as possible to provide better service
> for Exchange. However, when other processes need memory, it will
> automatically release memory for these processes. w3wp.exe will also take
> high memory usage and this should be a normal behavior. For now, please
> check whether the server has any performance issues (such as application
> hang or service no response). If yes, we can consider it as a performance
> issue and continue troubleshooting the problem.
>
> I hope the above info helps.
>
> If you have any update, please don't hesitate to let me know.
>
> Regards,
>
> Bill Peng
> MCSE 2000, MCDBA, CCNP, CCDA
> Microsoft CSS Online Newsgroup Support
>
> Get Secure! - www.microsoft.com/security
> =====================================================
> When opening a new thread via the web interface, we recommend you check the
> "Notify me of replies" box to receive notification. 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.
>
> The SBS public newsgroup only focuses on SBS related technical issues, for
> other Microsoft products, we recommend you to post to appropriate newsgroup
> to get most qualified responses.
> http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
>
> For urgent issues, you may want to contact Microsoft PSS 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: Exchange 2003 and timeout errors on XP machines
> >thread-index: AcWHy8CmAmU3O4fPQrCxD5NbvaquKg==
> >X-WBNR-Posting-Host: 64.161.46.243
> >From: "=?Utf-8?B?ams=?=" <jk@xxxxxxxxxxxxxxxxxxxxxxxxx>
> >Subject: Exchange 2003 and timeout errors on XP machines
> >Date: Wed, 13 Jul 2005 09:56:03 -0700
> >Lines: 19
> >Message-ID: <08B664DE-DC9F-4AB4-8525-56EFBAE4FE39@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.0
> >Newsgroups: microsoft.public.windows.server.sbs
> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> >Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
> >Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:135416
> >X-Tomcat-NG: microsoft.public.windows.server.sbs
> >
> >I have SBS 2003 fully patched with all the updates. I have posted this one
> >before. Eschange 2k3 sp1 with all the patches etc. I am not running ISA on
> >the server. Off and on throughout the day, clients on XP pro with Outllok
> >2003 get a pop up saying that they have lost connection to the server and
> >then 5 seconds later restored. In that 5 seconds they loose connectivity
> to
> >the SQL server and are booted out from a number off applications. I have
> >replaced all the switches in the network and now am looking at replacing
> >cables. SBS 2k3 seams to be running just fine. There are no error logs
> that
> >would pertain to the issue at hand. I have updated all the harware with
> >current drivers. My question would be where do I go now? I have advised
> that
> >individuals use the remote web for the time being until I can figure it
> out.
> >
> >The issue did not start until I install an extra 2k3 file server about a
> >month ago and install sp1 for server 2k3. I had issue installing sp1 for
> >exchange because I was missing a regestry key which a gentleman pointed
> out
> >to me earlier. Any help at this point is welcomed. I am running a dual
> >processor xeon server with 3 gb of memory. Everything in the task manager
> is
> >in order and store.exe and sql are at the top of the food chain with
> w3wp.exe
> >following. ANy suggestions?
> >
>
>
.

Relevant Pages

  • RE: CONFIG_DEBUG_SLAB_LEAK omits size-4096 and larger?
    ... of memory, ... Remind me what the most recent *bad* kernel was of those you tested? ... run a check under full load (800 + clients). ... So with that many clients all making requests to the server at once, ...
    (Linux-Kernel)
  • [Full-Disclosure] Broadcast crash in Xpand Rally 1.0.0.0
    ... versus server and clients ... The problem is caused by an unchecked memory allocation controlled by ... If the memory to allocate is too big the mallocfunction will fail ...
    (Full-Disclosure)
  • Broadcast crash in Xpand Rally 1.0.0.0
    ... versus server and clients ... The problem is caused by an unchecked memory allocation controlled by ... If the memory to allocate is too big the mallocfunction will fail ...
    (Bugtraq)
  • Broadcast crash in Xpand Rally 1.0.0.0
    ... versus server and clients ... The problem is caused by an unchecked memory allocation controlled by ... If the memory to allocate is too big the mallocfunction will fail ...
    (Full-Disclosure)
  • RE: Setup Cannot Copy the file: shell32.dll
    ... HD running W2K3 Server Ent Ed since Beta 1 for two years. ... I hope is is just a matter of replacing the memory. ...
    (microsoft.public.windowsxp.setup_deployment)