This article was previously published under Q243125
This article has been archived. It is offered "as is" and will no longer be updated.
When you are in a call with NetMeeting 3.0 or 3.01 clients and NetMeeting 2.0 clients, you may not be able to transfer or send files from the 3.0/3.01 clients to the 2.0 clients.
NetMeeting 2.0 does not send the GCC Roster Update indication that contains the File Transfer record when the node joins the conference. It sends the GCC Roster Update indication only when it is ready to send file data. Because of changes in the file transfer mechanism in more recent versions, the 2.0 clients are not seen by default until this request is made.
Note that this behavior occurs only on NetMeeting 2.0 for Microsoft Windows 95.
Upgrading to the latest version of NetMeeting resolves this issue. The latest version of NetMeeting is available at the following Microsoft Web site:
To work around this behavior, transfer a file from the 2.0 client to the other participants before trying to send a file from the 3.0/3.01 clients to the 2.0 client. This allows the 3.0/3.01 clients to see the 2.0 client and send files to the 2.0 client for the duration of the call.