outlook freezing
Discussion
We have exchange 2003 and outlook 2003 - everythings fine except a few laptop users where they're working in outlook and it'll freeze. if they close it and open it again it'll work fine until a bit later when it'll freeze again.
any ideas as its driving us mad - have tried new net cables / diff ports. the latops are different with diff drivers. is there any special protocol / ports etc that outlook uses that might affect it? or any other reason a laptop would be affected and not a pc?
thanks
Get similar issues here on desktop machines when comms with the (physically remote) exchange server or domain controller are interrupted. Allegedly having OL in "cached Exchange mode" should prevent such problems but it doesn't seem to...
How's the network connectivity from the laptops?
How's the network connectivity from the laptops?
pdV6 said:
Get similar issues here on desktop machines when comms with the (physically remote) exchange server or domain controller are interrupted. Allegedly having OL in "cached Exchange mode" should prevent such problems but it doesn't seem to...
How's the network connectivity from the laptops?
at the time of freezing the user can get on the net and access files on another fileserevr fine
if you ping the exchange server its fine neil_cardiff said:This MSX/OL2003 dear boy.....DNS/AD now....
WINS resolution OK?
If the machine is having problems contacting a WINS server then it'll have a fit when it comes to contacting the Exchange server?
We had a similar problem and it turned out the WINS server was having a few issues.
Neil
Tis true, but WINS is still applicable to the world of GP/AD - all very well having working DNS - but if WINS is shafted, it does cause issues...
Edited to add - I always put WINS entries into my remote users routers so's that they don't get problems when connecting to the Exchange server - try pinging your remote_exchange_server from home and the (normally configured) router (which will route DNS requests to your ISP) will fail to resolve it. Seeing as Exchange only uses fully qualified domain names ala AD, it'll fail.
I've been caught by this too many times
>> Edited by neil_cardiff on Tuesday 27th September 16:10
Edited to add - I always put WINS entries into my remote users routers so's that they don't get problems when connecting to the Exchange server - try pinging your remote_exchange_server from home and the (normally configured) router (which will route DNS requests to your ISP) will fail to resolve it. Seeing as Exchange only uses fully qualified domain names ala AD, it'll fail.
I've been caught by this too many times
>> Edited by neil_cardiff on Tuesday 27th September 16:10
neil_cardiff said:
Tis true, but WINS is still applicable to the world of GP/AD - all very well having working DNS - but if WINS is shafted, it does cause issues...
Edited to add - I always put WINS entries into my remote users routers so's that they don't get problems when connecting to the Exchange server - try pinging your remote_exchange_server from home and the (normally configured) router (which will route DNS requests to your ISP) will fail to resolve it. Seeing as Exchange only uses fully qualified domain names ala AD, it'll fail.
I've been caught by this too many times
>> Edited by neil_cardiff on Tuesday 27th September 16:10
will try - can u still use lmhosts on clients in xp/2003 environment?
billb said:
Tis true, but WINS is still applicable to the world of GP/AD - all very well having working DNS - but if WINS is shafted, it does cause issues...
Edited to add - I always put WINS entries into my remote users routers so's that they don't get problems when connecting to the Exchange server - try pinging your remote_exchange_server from home and the (normally configured) router (which will route DNS requests to your ISP) will fail to resolve it. Seeing as Exchange only uses fully qualified domain names ala AD, it'll fail.
I've been caught by this too many times
>> Edited by neil_cardiff on Tuesday 27th September 16:10
will try - can u still use lmhosts on clients in xp/2003 environment?
You can, but it's advisable not to - not for any real reason apart from administration. You'll forget, and then a year later when you've changed the IP address on a server be scratching your head as to why you cannot ping it...
It's the rock of Active Directory and Exchange in that DNS must be present and working for anything to be smoothly running.
Additionally although WINS should be dead in the water, in is still relied upon for mucho configaro as explained earlier.
While people say you can get away without WINS, it's all smoke and mirrors when they have tested it - usually in a test environment - and never in the true higgledy piggledy fashion that is our lovely production environments.
Additionally although WINS should be dead in the water, in is still relied upon for mucho configaro as explained earlier.
While people say you can get away without WINS, it's all smoke and mirrors when they have tested it - usually in a test environment - and never in the true higgledy piggledy fashion that is our lovely production environments.
eek! crc errors on an exchange server is usually something to panic about.
But lets not get too scared, make sure they are not code 12/13's (off the tops of my head) as they generally mean yer hard drives shagged.
Now, seeing as your server is a w2k3 server it should be relatively new?
Anyhow - you should have your edb and mdbs on a separate physical partition to your actual installation. If this is the case you can deal with the errors with relative ease as per the MS KB knowledgebase instructions.
Either way - I strongly suspect you have a Small Business Server, which would mean that everything is linked together - I have this problem on my Small Business Server 2000, and DNS is shagged beyond belief. Any LAN traffic is fine (Exchange, AD, etc) but anything outside of the local subnets fails to work swiftly as you would expect.
All this was linked to a physical drive failure (not completely but getting there) and curing this gave me a workaround (esp. with the CRC errors in Exchange) to alleviate some of my problems.
Anyhow, to the point - make sure you get rid of the CRC errors - they may well NOT be linked - but they may be and you'll need to methodicly work through each error bit by bit.
Neil
>> Edited by neil_cardiff on Wednesday 28th September 20:24
But lets not get too scared, make sure they are not code 12/13's (off the tops of my head) as they generally mean yer hard drives shagged.
Now, seeing as your server is a w2k3 server it should be relatively new?
Anyhow - you should have your edb and mdbs on a separate physical partition to your actual installation. If this is the case you can deal with the errors with relative ease as per the MS KB knowledgebase instructions.
Either way - I strongly suspect you have a Small Business Server, which would mean that everything is linked together - I have this problem on my Small Business Server 2000, and DNS is shagged beyond belief. Any LAN traffic is fine (Exchange, AD, etc) but anything outside of the local subnets fails to work swiftly as you would expect.
All this was linked to a physical drive failure (not completely but getting there) and curing this gave me a workaround (esp. with the CRC errors in Exchange) to alleviate some of my problems.
Anyhow, to the point - make sure you get rid of the CRC errors - they may well NOT be linked - but they may be and you'll need to methodicly work through each error bit by bit.
Neil
>> Edited by neil_cardiff on Wednesday 28th September 20:24
Podie said:
On a slight tanget...
Are you running the laptops with an *.ost..? We found that if we didn't use offline storage then we had freezing issues with 2k3...
We now use offline storage and keep *.pst files locally on the laptop too. Seems to work quite nicely.
Same problem and same resolution used here.
neil_cardiff said:
eek! crc errors on an exchange server is usually something to panic about.
But lets not get too scared, make sure they are not code 12/13's (off the tops of my head) as they generally mean yer hard drives shagged.
Now, seeing as your server is a w2k3 server it should be relatively new?
Anyhow - you should have your edb and mdbs on a separate physical partition to your actual installation. If this is the case you can deal with the errors with relative ease as per the MS KB knowledgebase instructions.
Either way - I strongly suspect you have a Small Business Server, which would mean that everything is linked together - I have this problem on my Small Business Server 2000, and DNS is shagged beyond belief. Any LAN traffic is fine (Exchange, AD, etc) but anything outside of the local subnets fails to work swiftly as you would expect.
All this was linked to a physical drive failure (not completely but getting there) and curing this gave me a workaround (esp. with the CRC errors in Exchange) to alleviate some of my problems.
Anyhow, to the point - make sure you get rid of the CRC errors - they may well NOT be linked - but they may be and you'll need to methodicly work through each error bit by bit.
Neil
>> Edited by neil_cardiff on Wednesday 28th September 20:24
not sbs its exchange enterprise on a 2 year old hp server on raid 5 disks
am concerned now! the errors are on the network card stats not in event viewer does this still point to dodgy hard drive?
billb said:
neil_cardiff said:
eek! crc errors on an exchange server is usually something to panic about.
But lets not get too scared, make sure they are not code 12/13's (off the tops of my head) as they generally mean yer hard drives shagged.
Now, seeing as your server is a w2k3 server it should be relatively new?
Anyhow - you should have your edb and mdbs on a separate physical partition to your actual installation. If this is the case you can deal with the errors with relative ease as per the MS KB knowledgebase instructions.
Either way - I strongly suspect you have a Small Business Server, which would mean that everything is linked together - I have this problem on my Small Business Server 2000, and DNS is shagged beyond belief. Any LAN traffic is fine (Exchange, AD, etc) but anything outside of the local subnets fails to work swiftly as you would expect.
All this was linked to a physical drive failure (not completely but getting there) and curing this gave me a workaround (esp. with the CRC errors in Exchange) to alleviate some of my problems.
Anyhow, to the point - make sure you get rid of the CRC errors - they may well NOT be linked - but they may be and you'll need to methodicly work through each error bit by bit.
Neil
>> Edited by neil_cardiff on Wednesday 28th September 20:24
not sbs its exchange enterprise on a 2 year old hp server on raid 5 disks
am concerned now! the errors are on the network card stats not in event viewer does this still point to dodgy hard drive?
Then prob not, especially if on Raid 5. I'd be doing some googling on it however!!!
You tried the OST/PST fix?
Edited to add: If you aren't using cached mode - then why not!? It's the nuts, especially for remote users.
>> Edited by neil_cardiff on Thursday 29th September 09:31
CRC erors aren't anything to panic about if they are on the NIC. They are if they are on the RAID controller, which in this case, they aren't.
Therefore, there should be enough info here to apply a bit of KISS logic.
Desktops aren't affected:
We can probably assume therefore that Exchange and the network is reasonably ok.
Laptops are affected and CRC errors are showing up on the server:
Laptops are using different NIC drivers to the desktops. We know the ones and zero's coming from the laptops arent the same as when they left the machine.
Suggestions:
Check for updated NIC drivers for the laptops, resolve the CRC issues and I think the problem will clear up.
Also, if you have managed switches, check the ports for errors. This should confirm my suspicions.
Therefore, there should be enough info here to apply a bit of KISS logic.
Desktops aren't affected:
We can probably assume therefore that Exchange and the network is reasonably ok.
Laptops are affected and CRC errors are showing up on the server:
Laptops are using different NIC drivers to the desktops. We know the ones and zero's coming from the laptops arent the same as when they left the machine.
Suggestions:
Check for updated NIC drivers for the laptops, resolve the CRC issues and I think the problem will clear up.
Also, if you have managed switches, check the ports for errors. This should confirm my suspicions.
Fair enough - thats a valid reason not to.
You may be stuffed then if that was/is a workaround.
There is always times when Outlook will have a funny five minutes - I'm sure its not just me when I tell of the annoying Outlook tendency to crash when losing its network connection - and vice versa, ask for a authentication password when opened offline and then[/] given a network connection (ala VPN)
Also network traffic can slow up responsivness on Outlook?
You may be stuffed then if that was/is a workaround.
There is always times when Outlook will have a funny five minutes - I'm sure its not just me when I tell of the annoying Outlook tendency to crash when losing its network connection - and vice versa, ask for a authentication password when opened offline and then[/] given a network connection (ala VPN)
Also network traffic can slow up responsivness on Outlook?
Gassing Station | Computers, Gadgets & Stuff | Top of Page | What's New | My Stuff