NetMeeting: Cannot Resume Call If the ISP Connection Is Dropped During a Remote Desktop Sharing Session (243141)



The information in this article applies to:

  • Microsoft NetMeeting 3.0 for Windows NT 4.0
  • Microsoft NetMeeting 3.0 for Windows 98 Second Edition
  • Microsoft NetMeeting 3.0 for Windows 98
  • Microsoft NetMeeting 3.01 for Windows 95
  • Microsoft NetMeeting 3.01 for Windows 2000
  • Microsoft NetMeeting 3.01 for Windows 98
  • Microsoft NetMeeting 3.01 for Windows 98 Second Edition
  • Microsoft NetMeeting 3.01 for Windows NT 4.0

This article was previously published under Q243141

SYMPTOMS

When you connect to the Internet for a Remote Desktop Sharing session, and then get disconnected, you may be unable to reconnect to the host. You may also receive one of the following error messages:
The call was not accepted

-or-

The person you are calling cannot accept NM calls

CAUSE

If an Internet Protocol (IP) address is dynamically assigned, for example, for dial-up networking, a Remote Desktop Sharing host server cannot resume Remote Desktop Sharing sessions after the connection to the network is lost.

WORKAROUND

To work around this issue, use either of the following methods:
  • Restart the Remote Desktop Sharing host server.

    -or-

  • On the Remote Desktop Sharing host server:

    1. Disconnect, and then reconnect to the Internet service provider (ISP).
    2. Quit Remote Desktop Sharing.
    3. Run the Configuration utility (Winipcfg.exe for Microsoft Windows 95 and Windows 98 or Ipconfig.exe for Microsoft Windows NT 4.0).
    4. Click the Release All button, and then click the Renew All button.
    5. Restart Remote Desktop Sharing.

MORE INFORMATION

After you are disconnected from Remote Desktop Sharing, the call control state is not reset. If you restart or reset the IP configuration, the H323 and T120 stacks are reloaded, and the call control state is reset.

In this situation, the Remote Desktop Sharing session on the host cannot dynamically detect a lost connection and the session continues to run. Therefore, the host is unavailable to receive new calls.

Modification Type:MinorLast Reviewed:4/25/2005
Keywords:kbprb KB243141