RE: Help with Windows NetMeeting



Jerry
Sorry but after reading the document over & over again it doesn't tell me
how to set it up on the host side. It only tells how to dial into the host.


"jerryrock" wrote:

>
>
> --------------------------------------------------------------------------------
>
> Microsoft Windows NetMeeting 3 Readme
>
> (c) Copyright Microsoft Corporation, 1999
>
> --------------------------------------------------------------------------------
>
> This document provides late-breaking information and known issues to
> supplement existing Help and other NetMeeting documentation.
>
> CONTENTS
> System Requirements and Setup Audio
> General Information Video
> General Known Issues Gatekeepers and Gateways
> Placing a Call Remote Desktop Sharing
> Receiving a Call Security
> Program Sharing Additional Known Issues
> Whiteboard Accessibility
> Chat
>
>
>
> System Requirements and Setup
> Microsoft(R) Windows(R) NetMeeting(R) enables real-time audio, video, and
> data communication over the Internet.
>
> If you have a dual or multiple boot configuration, you must install
> NetMeeting from within each operating system using separate folders.
> NetMeeting does not run properly from one default installation directory for
> multiple boot computers.
>
> Windows installs NetMeeting in the \netmeeting folder. This overwrites any
> prior Windows 95 or Windows 98 NetMeeting installation. After installing
> NetMeeting, reinstall NetMeeting on Windows 95 or Windows 98, and specify a
> different folder than \netmeeting during installation.
>
> NetMeeting works best with a fast Internet connection, such as a 56
> kilobytes per second (Kbps) or faster modem, or a local area network (LAN).
>
> For best viewing results, use 800 by 600 resolution or higher. You can also
> use compact mode.
>
> NetMeeting does not function properly over SLIP connections or other
> simulated SLIP/PPP connections.
>
> For information about product support, see the Support.txt file in your
> Windows folder or NetMeeting folder.
>
> If you're using a preinstalled OEM version of Windows, you won't be able to
> uninstall NetMeeting using Add/Remove Programs in Control Panel.
>
> Back to Contents
>
> General Information
> NetMeeting includes support for the H.323 audio and video conferencing
> standard and the T.120 data conferencing standard. NetMeeting can be used to
> place calls to and receive calls from products that are H.323 and T.120
> compatible. With appropriate equipment and services from third parties,
> NetMeeting can place a call to a telephone using an H.323 gateway. NetMeeting
> also can place calls to H.323 multipoint control units (MCUs) and participate
> in multipoint audio/video conferences.
>
> Back to Contents
>
> General Known Issues
> If you are hosting a meeting and you set preferences (others cannot share
> programs, launch Chat, etc.) in NetMeeting 3.0 or later, these preferences
> will not apply to NetMeeting 2.x computers. Users running NetMeeting 2.x will
> have access to these features.
>
> You cannot run ReachOut 5.0 on computers if NetMeeting is installed.
>
> To find the name that NetMeeting uses as your NetBIOS name, do the following
> steps:
>
> In Control Panel, double-click Network.
> Click the Identification tab.
> If you use User Profiles for multiple users to maintain your Windows
> preferences on all the computers on a network, you might have to run the
> Audio Tuning Wizard again when you switch computers.
>
> Both Microsoft(R) FrontPage(R) and NetMeeting currently use the same file
> type (.cnf). NetMeeting uses this file type for SpeedDials.
>
> Some ISDN devices are configured to automatically connect to the network.
> This might cause the ISDN device to try to connect to the network while
> NetMeeting is running. To stop this from happening, turn off Auto-Dial on the
> ISDN device.
>
> You can connect to only one other person with audio and/or video at a time.
>
> Some activities cause large amounts of data to be sent between the computers
> in your meeting (for example, using audio and sharing several programs while
> transferring a large file). In extreme cases, this might cause computers in
> the meeting to become very slow. To fix this, stop one or more of the meeting
> activities.
>
> Sharing of Microsoft(R) DirectX(R), OpenGL, MS-DOS(R), graphics-intensive
> games, and .avi files is not supported and might not function properly.
>
> Data sharing, Whiteboard, and Chat might not work properly between computers
> with different language settings and keyboard layouts.
>
> If you're using Internet Explorer 5 or later in offline mode and you try to
> start NetMeeting, NetMeeting does not automatically connect to the Internet.
> To work around this problem, dial up using Remote Access Service (RAS) for
> Windows computers. Or, in Internet Explorer, click the File menu, and then
> click Work Offline to clear the check mark.
>
> Meeting settings prevent you from starting NetMeeting programs (Chat,
> Whiteboard, File Transfer) after you've joined a meeting. However, meeting
> settings don't prevent these programs from working if they are started before
> the hosted meeting with settings is joined.
>
> MSN customers who aren't already connected to the MSN service while running
> NetMeeting may see multiple instances of the MSN logon window when opening
> the Find Someone dialog box.
>
> NetMeeting 3.0 or later may not support certain TV tuner cards as input
> sources. Check with the manufacturer of your TV tuner for current drivers.
>
> If you have specified that you should receive only secure calls, be aware
> that Office 2000 programs do not support secure conferencing. If you close
> NetMeeting and host a meeting using an Office 2000 program, the meeting will
> not be secure.
>
> Changing color depth is not recommended if NetMeeting is running, or if you
> are using Remote Desktop Sharing.
>
> Back to Contents
>
> Placing a Call
> You can place NetMeeting calls to multiple users.
>
> Microsoft maintains the Microsoft Internet Directory, which you can use to
> find other NetMeeting users. To view the Microsoft Internet Directory, click
> the Find Someone in a Directory button, and then in Select a directory, click
> Microsoft Internet Directory.
>
> NOTE You cannot call people on the Internet that you have located on
> Web-based directory servers if your Internet connection uses a proxy server
> that does not support NetMeeting.
>
> Additionally, if you cannot connect to someone by using their computer name,
> try using their IP address.
>
> If you have two active network connections using two separate network cards,
> you might not be able to connect to a directory service.
>
> Some MCUs are case-sensitive, so you should type the correct capitalization
> conference name to place a call.
>
> You may have to log on to a gatekeeper to call an MCU conference using the
> alias registered with the gatekeeper. Contact your system administrator for
> details.
>
> If you specify that you want a gatekeeper to place your calls, you can log
> on by using either your account name or phone number, or you can specify both
> options.
>
> Back to Contents
>
> Receiving a Call
> You are ready to receive incoming calls if you are running NetMeeting and
> have not selected Do Not Disturb on the Call menu.
>
> You are limited in the number of simultaneous connections you can make,
> depending on your in TCP/IP registry configuration.
>
> Back to Contents
>
> Program Sharing
> Any person in a meeting can share a program with the other participants.
> When you use the program sharing feature, other people can see the program.
> When you allow control, other people can both see and use the program.
>
> Users running NetMeeting 2.x cannot control programs shared by computers
> running NetMeeting 3.0 or later.
>
> Using this version of NetMeeting, you can share programs with large numbers
> of users. However, if a computer running NetMeeting 2.0 is in the conference,
> and more than three users are sharing, that computer will not be able to
> share a program. The total number of people who can successfully participate
> in your meeting depends on available network bandwidth and the speed of the
> participants' computers.
>
> Internet Explorer 5 or later users: If you share a Windows Explorer window
> and allow control, and the person with whom you are sharing the window closes
> the window, all programs and windows that you open afterwards are shared. To
> undo sharing in this situation, open a Windows Explorer window again, and
> unshare it.
>
> When you share a program and decide to allow someone to control it, remote
> users can use the File Open and File Save dialog boxes in your program to
> gain access to or delete files on your computer or network.
>
> If you are in control of a shared program and you use shortcut keys, the
> shortcut commands are applied to the shared program, not the shared frame
> menu. Shortcut keys will not work for menus in the shared frame.
>
> It is recommended that you do not leave your computer unattended while
> sharing a program and allowing control.
>
> When you launch another program from within the program you are sharing
> (such as a Microsoft Excel spread*** from within Microsoft Word), there is
> a possibility that the recently launched program will not be shared properly.
>
> You cannot drag an object onto a shared program or drag an object from a
> shared program to the desktop.
>
> If you are using an IntelliMouse and sharing a program, the mouse wheel
> might not work properly if you resize the sharing frame.
>
> When you share a program with an Input Method Editor (IME), you should show
> the IME status bar so that other people can use the mouse to activate the IME.
>
> If the IME does not support showing the status bar, or if other people are
> having trouble activating the IME, you can activate and deactivate the IME
> for them.
>
> If the IME window fails to redraw during a meeting, you can force it to
> redraw by clicking anywhere on the desktop.
>
> You may not be able to share programs on a computer that has a product
> installed with program sharing or remote control features (other than
> NetMeeting).
>
> While someone else is in control of a shared program, the host's sharing
> interface (shared frames, sharing dialog boxes, and any shared frames created
> from other machines) becomes "hidden" on the host's desktop. When the host is
> in control again, the sharing interface (and any programs shared by others)
> reappears.
>
> On Windows computers that are configured to use multiple languages and
> locales, the Unicode text on the host machine will appear as garbage
> characters on remote Windows computers when using program sharing.
>
> If the host computer is sharing a program and is using 16-bit color (or
> lower), elements of the shared program or desktop that normally appear gray
> will appear green on remote computers. This can include menu items, button
> bars, and status bars.
>
> Back to Contents
>
> Whiteboard
> NetMeeting users can draw simultaneously on the Whiteboard. Everyone in the
> meeting can see what is drawn on the Whiteboard. When one person in a meeting
> runs Whiteboard, it appears on everyone's screen.
>
> The Whiteboard does not maximize to the full size if you are using an 1152
> by 864 or larger display.
>
> In conferences between Windows computers and Windows 95 or 98 computers,
> double-byte character set (DBCS) characters may not be translated properly.
>
> Back to Contents
>
> Chat
> Chat enables you to type messages for other users to see. When one person in
> a meeting runs Chat, a chat window appears on everyone's screen if they are
> using NetMeeting 3.0 or later.
>
> NetMeeting 2.11 Chat participants may not be able to close the Chat window
> if they are participating in a meeting with a NetMeeting 3.0 or later Chat
> participant.
>
> Chat files can be saved with the .htm file extension, and then opened in an
> Internet browser.
>
> NetMeeting 2.x Chat does not interoperate with NetMeeting 3.0 or later Chat
> in some scenarios.
>
> Back to Contents
>
> Audio
> To use NetMeeting audio features, you need a sound card, speakers, and a
> microphone.
>
> Audio is only supported with one other person.
>
> Sound quality can vary significantly depending on your sound card,
> microphone, and connection.
>
> If you modify your sound card device driver in any way, such as upgrading to
> a full-duplex driver, you need to run the Audio Tuning Wizard again in order
> for NetMeeting to work correctly.
>
> When in a call with a NetMeeting 2.0 user, if audio stops for some reason,
> the 2.0 user may not be able to restart it. You have to quit your call and
> start over.
>
> You may receive a message in the Audio Tuning Wizard stating that your sound
> card is unsupported. This occurs when the sound card does not support some of
> the features required for it to be used by NetMeeting. The audio features in
> NetMeeting may work even if you get this message, but you might experience
> poor audio quality.
>
> If your sound card is unsupported, you might want to contact the
> manufacturer to find out if newer sound card drivers are available.
>
.


Loading