We are in the middle of moving users to a new 2003 exchange server. The old 2003 exchange really need to go base on hardware.. After moving clients over to the new exchange. I notice that when i open up emails more then 1mb in size it would take roughly 30-1minute to open. Also, it seems that when we first open outlook, it will take 20-30 second to open the connection to exchange. The dns seems to be fine through nslookup.. Everything seems to be contacting the new exchange server right... Does anyone have any pointers or what might be causing the problem...?? Thanks in Advance... AL
A.L. wrote: > We are in the middle of moving users to a new 2003 exchange server. > The old 2003 exchange really need to go base on hardware.. > > After moving clients over to the new exchange. I notice that when i > open up emails more then 1mb in size it would take roughly 30-1minute > to open. > > Also, it seems that when we first open outlook, it will take 20-30 > second to open the connection to exchange. > > The dns seems to be fine through nslookup.. Everything seems to be > contacting the new exchange server right... > > Does anyone have any pointers or what might be causing the > problem...?? > > Thanks in Advance... > AL What version & SP of Outlook, and are your users using cached mode? You might post an unedited ipconfig /all from a client & a DC.
Hi Lanwench, I am currently using exchange 2003 sp2 and outlook 2003 and 2000.. On both versions it seems to delay when opening.. I pulled some loggs from running... ethereal. Here are my finding.. I get alot of mapi unknown?! request I get alot of mapi unknown?! response from the server to me and vise visa. Thanks... Is there something that you are looking for in particular for the ipconfig /all.. It seems that dns is accurate.. "Lanwench [MVP - Exchange]" wrote: > A.L. wrote: > > We are in the middle of moving users to a new 2003 exchange server. > > The old 2003 exchange really need to go base on hardware.. > > > > After moving clients over to the new exchange. I notice that when i > > open up emails more then 1mb in size it would take roughly 30-1minute > > to open. > > > > Also, it seems that when we first open outlook, it will take 20-30 > > second to open the connection to exchange. > > > > The dns seems to be fine through nslookup.. Everything seems to be > > contacting the new exchange server right... > > > > Does anyone have any pointers or what might be causing the > > problem...?? > > > > Thanks in Advance... > > AL > > What version & SP of Outlook, and are your users using cached mode? > You might post an unedited ipconfig /all from a client & a DC. > > >
A.L. wrote: > Hi Lanwench, > > I am currently using exchange 2003 sp2 and outlook 2003 and 2000.. On > both versions it seems to delay when opening.. Ouch. I'd get rid of OL2000 - it's old & icky. For your Outlook 2003 users, are you using cached mode? You should be.... > I pulled some loggs from running... ethereal. Here are my finding.. > > I get alot of mapi unknown?! request > I get alot of mapi unknown?! response I don't use that stuff much so it won't be very useful to me.... > > from the server to me and vise visa. > > Thanks... > > Is there something that you are looking for in particular for the > ipconfig /all.. It seems that dns is accurate.. Yes, post it, just in case. > > "Lanwench [MVP - Exchange]" wrote: > >> A.L. wrote: >>> We are in the middle of moving users to a new 2003 exchange server. >>> The old 2003 exchange really need to go base on hardware.. >>> >>> After moving clients over to the new exchange. I notice that when i >>> open up emails more then 1mb in size it would take roughly >>> 30-1minute to open. >>> >>> Also, it seems that when we first open outlook, it will take 20-30 >>> second to open the connection to exchange. >>> >>> The dns seems to be fine through nslookup.. Everything seems to be >>> contacting the new exchange server right... >>> >>> Does anyone have any pointers or what might be causing the >>> problem...?? >>> >>> Thanks in Advance... >>> AL >> >> What version & SP of Outlook, and are your users using cached mode? >> You might post an unedited ipconfig /all from a client & a DC.
Lanwench, I used outlook /rpcping and it takes roughly 16-20 seconds to open. But when I used outlook /safe:1 or safe:2 or safe:3 or safe:4 is automatically comes up.. I am wondering what type of connection is made via exchange that might slow things down... Would it be a link to the old server... Thanks "Lanwench [MVP - Exchange]" wrote: > A.L. wrote: > > Hi Lanwench, > > > > I am currently using exchange 2003 sp2 and outlook 2003 and 2000.. On > > both versions it seems to delay when opening.. > > Ouch. I'd get rid of OL2000 - it's old & icky. For your Outlook 2003 users, > are you using cached mode? You should be.... > > > I pulled some loggs from running... ethereal. Here are my finding.. > > > > I get alot of mapi unknown?! request > > I get alot of mapi unknown?! response > > I don't use that stuff much so it won't be very useful to me.... > > > > from the server to me and vise visa. > > > > Thanks... > > > > Is there something that you are looking for in particular for the > > ipconfig /all.. It seems that dns is accurate.. > > Yes, post it, just in case. > > > > > "Lanwench [MVP - Exchange]" wrote: > > > >> A.L. wrote: > >>> We are in the middle of moving users to a new 2003 exchange server. > >>> The old 2003 exchange really need to go base on hardware.. > >>> > >>> After moving clients over to the new exchange. I notice that when i > >>> open up emails more then 1mb in size it would take roughly > >>> 30-1minute to open. > >>> > >>> Also, it seems that when we first open outlook, it will take 20-30 > >>> second to open the connection to exchange. > >>> > >>> The dns seems to be fine through nslookup.. Everything seems to be > >>> contacting the new exchange server right... > >>> > >>> Does anyone have any pointers or what might be causing the > >>> problem...?? > >>> > >>> Thanks in Advance... > >>> AL > >> > >> What version & SP of Outlook, and are your users using cached mode? > >> You might post an unedited ipconfig /all from a client & a DC. > > > >
A.L. wrote: > Lanwench, > > I used outlook /rpcping and it takes roughly 16-20 seconds to open. > But when I used outlook /safe:1 or safe:2 or safe:3 or safe:4 is > automatically comes up.. I am wondering what type of connection is > made via exchange that might slow things down... Would it be a link > to the old server... > > Thanks I can't say - and you haven't answered my questions.... ? > > "Lanwench [MVP - Exchange]" wrote: > >> A.L. wrote: >>> Hi Lanwench, >>> >>> I am currently using exchange 2003 sp2 and outlook 2003 and 2000.. >>> On both versions it seems to delay when opening.. >> >> Ouch. I'd get rid of OL2000 - it's old & icky. For your Outlook 2003 >> users, are you using cached mode? You should be.... >> >>> I pulled some loggs from running... ethereal. Here are my finding.. >>> >>> I get alot of mapi unknown?! request >>> I get alot of mapi unknown?! response >> >> I don't use that stuff much so it won't be very useful to me.... >>> >>> from the server to me and vise visa. >>> >>> Thanks... >>> >>> Is there something that you are looking for in particular for the >>> ipconfig /all.. It seems that dns is accurate.. >> >> Yes, post it, just in case. >> >>> >>> "Lanwench [MVP - Exchange]" wrote: >>> >>>> A.L. wrote: >>>>> We are in the middle of moving users to a new 2003 exchange >>>>> server. The old 2003 exchange really need to go base on hardware.. >>>>> >>>>> After moving clients over to the new exchange. I notice that when >>>>> i open up emails more then 1mb in size it would take roughly >>>>> 30-1minute to open. >>>>> >>>>> Also, it seems that when we first open outlook, it will take 20-30 >>>>> second to open the connection to exchange. >>>>> >>>>> The dns seems to be fine through nslookup.. Everything seems to be >>>>> contacting the new exchange server right... >>>>> >>>>> Does anyone have any pointers or what might be causing the >>>>> problem...?? >>>>> >>>>> Thanks in Advance... >>>>> AL >>>> >>>> What version & SP of Outlook, and are your users using cached mode? >>>> You might post an unedited ipconfig /all from a client & a DC.
