IP Stack corrupted while Autodesk products are running.

Discussion in 'AutoCAD' started by cmyers, Sep 2, 2004.

  1. cmyers

    cmyers Guest

    I have a 12-user license served via Flexlm which is installed on an NT 4 domain controller. It serves licenses for AutoCAD 2004 and Inventor 7, and has been working fine ever since it was installed.

    The problem that I'm having on a few workstations is that within a few minutes of starting AutoCAD 2004 or Inventor 7, it's IP stack (of the workstation only) appears to crash. That particular workstation will quit responding on the network (can't ping anything), until the particular Autodesk product is closed, at which time it immediately regains network communication.

    The 3 workstations in question were members of the NT4 domain (and worked fine that way) that is controlled by the same domain controller that serves the flexlm licenses. Shortly after migrating these 3 particular workstation into an Active Directory domain (using the Active Directory Migration Tool), the problem started occurring. I have at least one other workstation that was migrated to the new domain which doesn't exhibit this behavior.

    The systems are all P-IV's with 512MB of RAM and running Windows XP Professional. Of the 3 systems with this problem, 2 are Dell's and 1 is a Gateway. I have a 3rd Dell which does NOT have the problem and is identical to the 2 Dell's that ARE having the problem (was a member or the NT domain and was subsequently migrated to the Active Directory domain). Only 1 of the machines has XP SP-2 applied.

    Basically, the IP stacks appear to be getting corrupted by these Autodesk products, and at the moment I'm suspecting something that's involved with having just migrated the user & computer accounts into the Active Directory domain.

    Any suggestions?
     
    cmyers, Sep 2, 2004
    #1
  2. cmyers

    cmyers Guest

    Resolved it. Turns out it was an updated driver from Microsoft for the Allied Telesyn AT-2700 network card. The updated driver dated 07-02-2004 caused the problem. Rolling back the driver to the previous version fixed the problem.

    -Charlie
     
    cmyers, Sep 8, 2004
    #2
Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.