
UNSOLVED
Closed
Latitude D620 modem causes system to freeze
Hello,
This is my first time here. I apologize up front of this has already been posted or addressed.
We have about 20 Latitude D620 systems in our office and we are having a problem with the modem on all of them. Here is the scenario and it is the same across the board; We use AT&T Global Network Extended Access Client for dial up access and use Firebox SSL Secure Access VPN client software to tunnel into our network. We also use exchange 2003 with Outlook 2003. When anyone dials in, then connects to the VPN and opens Outlook, the system completely freezes up as soon as Outlook starts to receive data from Exchange. When it freezes there is no response on the system, it is still displaying but nothing happens the display is frozen and not even the caps lock lights up. It has to be shut down by holding the power button. If I put in a PCMCIA modem in of any brand, it works as it should. I have tried all drivers available for the modem. I have tried several BIOS revisions. I have tried with XP SP2 with/without updates. I have tried Office 2003 with/without updates/service packs. I have tried with the standard Dell image out of the box. I have modified the init commands for the modem and tried several configuration changes. I have tried different versions of our AT&T dialer. I have tried with all the startup items disabled. I have tried 10 out of 20 of our D620 systems and they all get the same result. None of our other models do this and we have a mix of Dells in use (CPx, C600, C610, C640, C800, C810, C840, D600, D610, D800, D810) as well as a handful of Compaqs and Gateways. The modem in question is the Conexant D110 MDC V.92 modem. All our systems are similarly if not identically configured and have no problems performing this same operation for remote exchange connectivity. I would call Microsoft on this but I supect this is a driver issue due to the fact that this only happens on this system and the problem is rectified by using any brand of PCMCIA modem. I hope I have provided enough info on this and appreciate your response.
Responses (10)
Solutions (0)
- Thank you for your response. I am certain it is not the VPN client due to the fact that it works great while trying to get to our intranet and network drives. It only happens while Outlook is retireving data. I have had Dell come out and replace the modem and it still has the issue. I have tried 4 different PCMCIA modems and a USB modem. It appears there is some sort of conflict between Microsoft and the modem driver. I have called Dell and they replaced the modem with a different one, however the chipset is the same, therefore it uses the same driver and the issue remains. After 3.5 hours on the phone, Dell has escalated this to level 3. Hopefully they will be able to find a resolution. This is definitely something we need resolved because our company uses dial up alot due to the remote locations our jobs take us.
- We're having a similar issue with the D620's. I have no answers, but can add a few more items tested.
We experience a hard lock on all D620's when dialing some numbers in our Fiberlink dial solution. The issue seams to be between the modem driver, the network shim on our personal firewall (Cisco's CSA), and some of our dial numbers. We have found that the issue only shows when the network shim is active, and we dial local numbers. The toll-free numbers seam to work fine when the network shim is active.
Is your issue limited to certain dial numbers, or do all number behave the same? - I have tried several other numbers including our toll free numbers and they do the same thing. If you are experiencing trouble like you say, I would call Dell on the issue since they have told me they have put out a flag for any modem related issues on these models (D620). Any extra input may help the process for both of us.
- Update:
Dell has tried several different modems including one out of a D610 and it is not resolved yet. I am working with Dell to replicate the issue with a test VPN client account and a test exchange account so they can see it first hand in their environment. I have tested this with a D620 off our domain and connected to exchange through dial up using VPN and the same issue surfaces after authenticating the username/password of the account.
I will post further updates so this can be referred to.
Here is the software configuration causing the issue;
Outlook 2003, Exchange 2003, Firebox SSL Secure Access VPN client, AT&T Global Network Extended Access client - Update 1/23/07:Dell now has a system with our software and test accounts we have set up for them. Dell has been able to replicate the issue. They are keeping me up to date as necessary, but have not come up with a solution or answer as to why this occurs.
- I have opened a case with WatchGuard on this issue and they have escalated the issue to their level 2 engineers. They seem to think there is an issue with the Citrix client portion and the way it handles the large amount data being pulled from exchange causing the TCP/IP stack to crash somehow. Most of this is beyond me at this point, but will post more when I know more. WatchGuard has tols me they will not work with Dell on the case. However, in Dell's defense they have tried to contact WatchGuard with no success.
- Here is Dell's position as of today;Dell-" I heard back from our engineers and was told that we will not be able to provide a fix or access to Microsoft. “There is a problem with the application`s interaction with the OS. The application vendor needs to engage MS for a solution.” Basically, you or Citrix/Watchguard will have to contact Microsoft directly. While our engineers have not closed the case and are still reviewing the issue, they wanted me to pass this information along."My response-"Thank you for looking into this for us. Please provide the exact details of the determination and findings so we can note this in our case and work with WatchGuard and/or Microsoft in order to pursue the next steps or alternatives. We want make sure WatchGuard is able to make the same conclusion before we can take the next step."Dell's response-"This stance came from the behavior of the WatchGaurd application during testing (unstable, disconnects, system hangs) as well as the statement in the issue "Citrix would like us to look at the dump as they claim the issue is a resource bottleneck in FileSystemNfts" FileSystemNtfs is the OS, not the system.”Not very helpful
- My response-" I just need to clarify your conclusion. It sounds to me your decision is based on two simple facts; The first being that the system freezes while using dial-up software, WatchGuard (VPN) software and replicating with Exchange on a D620 and D420 series. The second would be based on a comment made by WatchGuard.
The rationale provided is hollow and provides little to go on. Dell’s conclusion has left more questions than answers. We cannot understand why this setup works on more than 30 different brands/types of systems and only will not work on the D620 or D420 series laptops. What is the exact cause if indeed WatchGuard software is the culprit? I believe it is possible that WatchGuard’s software may be the problem, but there is no evidence to support this as of yet. I remain skeptical of the troubleshooting steps taken by your team at Dell and further state that this has been an open case for almost eight months with little insight from you (Dell) into what has been found and any steps taken to resolve this.
Unfortunately, we will not be able to accept this conclusion due to a lack of supported evidence. Honestly, it sounds like we are at the same place we have been since the case was opened back in September of 2006. Due to the lack of support and evidence provided, we will be preparing our process of returning approximately 50 laptops that are unusable in the field and clearly defective. This decision will be based on this and the many other emails in correspondence to the issue.
However, we would still like to afford the opportunity to find resolve. It is advantageous for both parties to find a solution due to the potential situation. We are open to further thoughts on this and are awaiting your response."
- The solution;Hopefully, no one else out there has purchased a WatchGuard Firebox SSL VPN box. It turns out, through further testing, that it is an issue with the Citrix based client they are using and the modem. I am quite positive this is for the newer HDA series of modems (HDA stands for High Definition Audio) which are part of the audio chipsets used on newer laptops. I tried this with an HP laptop using an "Agere Systems HDA modem" and got the same result. WatchGuard has had this case open for 5 months now and there answer has been that they are "...waiting an update from my manager" which is the same answer they have given for several months now. We are now researching other vendor products at this time.In Dell's defense, they were right to say that this is a WatchGuard issue. It is too bad that it has taken this long (11 months) to come to this conclusion.My apologies to Dell for giving them a hard time. No hard feelings guys.

fudgieguys
1308 Posts
648
0
Posted September 16th, 2006 05:00
Maybe they might have an idea on how to work with the internal moden model on the D620.
We use Cisco VPN, in fact dailup will not work with our VPN client.