6 replies
by rich.good
by nikki96
Could be a few things.
If NetMeeting is already running in the background (which is an option on startup) remote access doesn't work, as it can only be started when Netmeeting is NOT running. Make sure the service is not running on the target computer before attempting remote access.
From an article...
"However, when you install NetMeeting on end users' computers, you should standardize their configurations. You do this by selecting Options from the Tools menu on the end user's machine and clicking the Show The NetMeeting Icon On The Taskbar on the General tab. Also, consider selecting the Run NetMeeting In The Background When Windows Starts option. When you enable this option, NetMeeting will automatically run on end users' systems, so you don't have to walk users through the process of starting NetMeeting. However, with this option selected, you can't use Remote Desktop Sharing because you can activate that feature only when NetMeeting isn't running. For remote sessions to run smoothly, consider disabling NetMeeting's audio and video features by clearing their options on the Audio and Video tabs. The audio feature can interfere with other operations and sometimes lock up the machine."
Another issue may be the IP address. They need to have an IP addy that can be found using ping. On another machine, attempt to ping the target computer with the ip address. Does it work? If not, there is an error with either their DNS info or their ports are blocked.
HTH
Nikki
by shanghai sam
by dklippert
See if this site has the answers you need:
by rich.good
by rich.good
This discussion is closed to new replies.
Trending Community archive posts
Sort by Trending