none
Network Connector Dropping session after 1 - 3 mins RRS feed

  • Question

  • A client is currently running IAG SP2 Update1 and we seem to be having problems with the Network Connector dropping the session after 1 - 3 mins.  The client is connecting using a T-Mobile 3G dongle. Connectivity through Wireless or LAN connection seems to be fine.

    Has anybody got any ideas of what may be causing this problem. The dongle shows good reception and somestimes it shows this behaviour and then other times it we work okay.

    Thanks in advance

    Darren

    Monday, November 9, 2009 3:37 PM

Answers

  • Hi,
    Replying to the last message, and in general. I'm afraid it is impossible to adjust the period it takes the client components to notify you of the disconnection, and it's also impossible to set this to automatically reconnect. However, the new version of IAG that's coming out shortly has a new functionality called DA (Direct Access) that offers significant improvements over Network Connector.

    Thanks a lot for posting your findings. I can also confirm that on other cases we worked on, the disconnects were caused by various issues with the network infrastructure, from weak wireless signals to ISP-generated interruptions. In almost all cases, it's possible to isolate the cause by carefully eliminating the variables.
    Ben Ari
    Microsoft CSS IAG Support
    Sammamish, WA
    • Marked as answer by Erez Benari Tuesday, November 10, 2009 4:44 PM
    Tuesday, November 10, 2009 4:44 PM

All replies

  • Hi Darren,

    From NC perspective it doesnt matter either you use WiFi or 3G connection, its not doing any sort of QoS. What I could think of is probably the signal strength of your 3G connection and the timing for NC is forcing the connection to drop. Dont know if taking packet level dumps would help because your issue is intermittent and it works fine with WiFi anyways.
    if issue is across many client machines and if its specific to a particualr versio of OS, like only evident on Windows VIsta then its worth looking into it.
    Faisal :>
    Monday, November 9, 2009 4:04 PM
  • The client machines are a corprate build of XP Prfessional with service pack 3 and numwerous GPO's applied. I'll continue to investigate.
    Monday, November 9, 2009 4:23 PM
  • Hi,

    We're experiencing very similar issues, however, the disconnect does not always happen within the first few minutes.  We've done fairly extensive testing with an external PC, using various internet connections, wireless 802.11, cellular EVDO, hardwired connection, etc.

    In an attempt to isolate the many variables that are present when dealing with this type of issue (client PC, client ISP, ISP route) we finally ended up connecting a PC straight to our corporate internet router, which is outside our firewall, so essentailly the only difference between connecting at this point and a user connecting from home would be fewer hops, and the stability of the connection is completely within our control.

    We could maintain this connection for as long as we needed to, meaning that neither the PC itslef, or the IAG client software was the culprit.  We then begain expirementing with disconnecting the link between the PC and the router, first try we got an immediate notification on the client that "the network cable has been unplugged" realizing this was not the normal home user configuration (most have cable/DSL modem -> router -> PC) we added a small switch between the PC and the internet router.  This time if we disconnected the cable between the small switch and the internet router we got the problems our users have been complaining about for months.

    For about 45 seconds all network apps open over the VPN (email client, intranet pages, etc.) freeze.  After that 45 seconds has passed we are then notified that the network connector has been disconnected.  We've been frustrated by this greatly.  It's been explained to us by Celestix that due to the secure nature of VPN, that any interruption of service will cause the tunnel to fail and it will need to be reinitated.

    They are working on workarounds for us, but also, we've posed the question that if we can not adjust the sensitivity of the Network Connector to network issues, can we perhaps adjust the client time-out.  In other words, instead of waiting 45 frustrating seconds for a message about the disconnection, can we instead have that pop up after only 3 or 4 seconds (as the "cable unplugged" message does)

    Also we're wondering if there's any way to configure the VPN to be smart enough to reestablish itself once it realizes the connection has been lost, and eliminate the need for the user to click on the link agian.

    Anyway, no real help here, just more info on what we've found and to let you know others are facing the same frustrating problems.

    Monday, November 9, 2009 7:07 PM
  • Hi,
    Replying to the last message, and in general. I'm afraid it is impossible to adjust the period it takes the client components to notify you of the disconnection, and it's also impossible to set this to automatically reconnect. However, the new version of IAG that's coming out shortly has a new functionality called DA (Direct Access) that offers significant improvements over Network Connector.

    Thanks a lot for posting your findings. I can also confirm that on other cases we worked on, the disconnects were caused by various issues with the network infrastructure, from weak wireless signals to ISP-generated interruptions. In almost all cases, it's possible to isolate the cause by carefully eliminating the variables.
    Ben Ari
    Microsoft CSS IAG Support
    Sammamish, WA
    • Marked as answer by Erez Benari Tuesday, November 10, 2009 4:44 PM
    Tuesday, November 10, 2009 4:44 PM