How do I fix "Netmeeting could not start." problem?
DComTalk.com Forum Index DComTalk.com
Discussion of VoIP, VPN, Video Conferencen, DSL and other data commucations.
 
 FAQFAQ   MemberlistMemberlist     RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
 
Google
 
Web dcomtalk.com
How do I fix "Netmeeting could not start." problem?

 
Post new topic   Reply to topic    DComTalk.com Forum Index -> Netmeeting
Author Message
Richard Sutterfield
Guest





Posted: Tue May 11, 2004 9:40 pm    Post subject: How do I fix "Netmeeting could not start." problem? Reply with quote

Hello all,

I have a Windows 2000 Server that has recently begun giving an error at boot up. The error is "Netmeeting could not start. Please restart your computer and try again."

Restarting has fixed the problem a few times but is now failing to help.

The server is running SP2 and hasn't had any new software installed that I know of.

This is a remote machine that I use Terminal Service to connect to and then use Netmeeting to connect to workstations on the LAN to do remote support.

Any ideas on how to resolve this?

Thanks for any help.
Back to top
Brian Sullivan MVP
Guest





Posted: Tue May 11, 2004 10:17 pm    Post subject: Re: How do I fix "Netmeeting could not start." problem? Reply with quote

"Richard Sutterfield" <richardnospam@kellpro.com> wrote in message
news:uzv2b83NEHA.2716@tk2msftngp13.phx.gbl...
Hello all,

I have a Windows 2000 Server that has recently begun giving an error at boot
up. The error is "Netmeeting could not start. Please restart your computer
and try again."

Restarting has fixed the problem a few times but is now failing to help.

The server is running SP2 and hasn't had any new software installed that I
know of.

This is a remote machine that I use Terminal Service to connect to and then
use Netmeeting to connect to workstations on the LAN to do remote support.

Any ideas on how to resolve this?

Thanks for any help.
----------------------------------------------------------------------------
-----------------------------------------------------------------------

I don't know of any specific "NetMeeting could not start." problem.

I know such a message can appear if there is some other program using tcp
1503 ( the T.120 port) when NetMeeting starts. I can't think of why a reboot
would solve the problem ( unless it just shuts down the program causing the
problem).

Is there some other program listening on tcp 1503 ( try a netstat to see)?



--
Brian Sullivan
Meeting by Wire ( http://www.meetingbywire.com)
------------
Is your PC protected? --
http://www.microsoft.com/security/protect/default.asp
Back to top
Richard Sutterfield
Guest





Posted: Tue May 11, 2004 11:20 pm    Post subject: Re: How do I fix "Netmeeting could not start." problem? Reply with quote

"Brian Sullivan MVP" <brians@WORMTIREDmeetingbywire.com> wrote in message
news:%23dAdpQ4NEHA.2560@TK2MSFTNGP11.phx.gbl...
Quote:

I don't know of any specific "NetMeeting could not start." problem.

I know such a message can appear if there is some other program using tcp
1503 ( the T.120 port) when NetMeeting starts. I can't think of why a
reboot
would solve the problem ( unless it just shuts down the program causing
the
problem).

Is there some other program listening on tcp 1503 ( try a netstat to see)?


Nothing is listening on 1503.

I have pasted a copy of what netstat returned below. Took a long time to
gather this info - probably 3-4 minutes. My local servers take only
seconds. Does that sound normal?

Thanks again.

Active Connections

Proto Local Address Foreign Address State
TCP nt4server:ldap nt4server.LCCLERK.ORG:1089 ESTABLISHED
TCP nt4server:ldap nt4server.LCCLERK.ORG:1090 ESTABLISHED
TCP nt4server:ldap nt4server.LCCLERK.ORG:1092 ESTABLISHED
TCP nt4server:ldap nt4server.LCCLERK.ORG:1118 ESTABLISHED
TCP nt4server:1089 nt4server.LCCLERK.ORG:ldap ESTABLISHED
TCP nt4server:1090 nt4server.LCCLERK.ORG:ldap ESTABLISHED
TCP nt4server:1092 nt4server.LCCLERK.ORG:ldap ESTABLISHED
TCP nt4server:1118 nt4server.LCCLERK.ORG:ldap ESTABLISHED
TCP nt4server:1467 nt4server.LCCLERK.ORG:ldap CLOSE_WAIT
TCP nt4server:netbios-ssn LEFLORE-F6WAJ2N:2324 ESTABLISHED
TCP nt4server:netbios-ssn KELLI:1094 ESTABLISHED
TCP nt4server:netbios-ssn PUBLIC:1031 ESTABLISHED
TCP nt4server:netbios-ssn FRAN:1041 ESTABLISHED
TCP nt4server:ldap nt4server.LCCLERK.ORG:1131 ESTABLISHED
TCP nt4server:ldap nt4server.LCCLERK.ORG:1693 TIME_WAIT
TCP nt4server:ldap nt4server.LCCLERK.ORG:1694 TIME_WAIT
TCP nt4server:ldap nt4server.LCCLERK.ORG:1699 TIME_WAIT
TCP nt4server:ldap nt4server.LCCLERK.ORG:1700 TIME_WAIT
TCP nt4server:ldap nt4server.LCCLERK.ORG:1715 TIME_WAIT
TCP nt4server:ldap nt4server.LCCLERK.ORG:1716 TIME_WAIT
TCP nt4server:ldap nt4server.LCCLERK.ORG:1718 TIME_WAIT
TCP nt4server:microsoft-ds nt4server.LCCLERK.ORG:pptp ESTABLISHED
TCP nt4server:1026 nt4server.LCCLERK.ORG:1133 ESTABLISHED
TCP nt4server:1026 nt4server.LCCLERK.ORG:1265 ESTABLISHED
TCP nt4server:1131 nt4server.LCCLERK.ORG:ldap ESTABLISHED
TCP nt4server:1133 nt4server.LCCLERK.ORG:1026 ESTABLISHED
TCP nt4server:1223 POPSERVER_0087:netbios-ssn ESTABLISHED
TCP nt4server:1261 nt4server.LCCLERK.ORG:ldap CLOSE_WAIT
TCP nt4server:1265 nt4server.LCCLERK.ORG:1026 ESTABLISHED
TCP nt4server:ms-sql-s LEFLORE-F6WAJ2N:2325 ESTABLISHED
TCP nt4server:ms-sql-s KELLI:1095 ESTABLISHED
TCP nt4server:ms-sql-s PUBLIC:1067 ESTABLISHED
TCP nt4server:ms-sql-s FRAN:1049 ESTABLISHED
TCP nt4server:1689 nt4server.LCCLERK.ORG:microsoft-ds
TIME_WAIT
TCP nt4server:1690 nt4server.LCCLERK.ORG:epmap TIME_WAIT
TCP nt4server:1691 nt4server.LCCLERK.ORG:1026 TIME_WAIT
TCP nt4server:1695 nt4server.LCCLERK.ORG:epmap TIME_WAIT
TCP nt4server:1696 nt4server.LCCLERK.ORG:1026 TIME_WAIT
TCP nt4server:1702 192.168.1.30:printer TIME_WAIT
TCP nt4server:1703 PUBLIC:netbios-ssn TIME_WAIT
TCP nt4server:1706 192.168.1.30:printer TIME_WAIT
TCP nt4server:1707 PUBLIC:netbios-ssn TIME_WAIT
TCP nt4server:1710 192.168.1.30:printer TIME_WAIT
TCP nt4server:1711 PUBLIC:netbios-ssn TIME_WAIT
TCP nt4server:1717 nt4server.LCCLERK.ORG:microsoft-ds
TIME_WAIT
TCP nt4server:1721 192.168.1.30:printer TIME_WAIT
TCP nt4server:1722 PUBLIC:netbios-ssn TIME_WAIT
TCP nt4server:pptp nt4server.LCCLERK.ORG:microsoft-ds
ESTABLISHED
TCP nt4server:1724 nt4server.LCCLERK.ORG:epmap TIME_WAIT
TCP nt4server:1725 nt4server.LCCLERK.ORG:1026 TIME_WAIT
TCP nt4server:1726 nt4server.LCCLERK.ORG:epmap TIME_WAIT
TCP nt4server:1727 nt4server.LCCLERK.ORG:1026 TIME_WAIT
Back to top
Brian Sullivan MVP
Guest





Posted: Tue May 11, 2004 11:35 pm    Post subject: Re: How do I fix "Netmeeting could not start." problem? Reply with quote

Richard Sutterfield wrote:
Quote:
"Brian Sullivan MVP" <brians@WORMTIREDmeetingbywire.com> wrote in
message news:%23dAdpQ4NEHA.2560@TK2MSFTNGP11.phx.gbl...

I don't know of any specific "NetMeeting could not start." problem.

I know such a message can appear if there is some other program
using tcp 1503 ( the T.120 port) when NetMeeting starts. I can't
think of why a reboot would solve the problem ( unless it just shuts
down the program causing the problem).

Is there some other program listening on tcp 1503 ( try a netstat to
see)?


Nothing is listening on 1503.

It seems to show nothing listening on any port which is unlikely I think --
this is a "server" right? -- did you use netstat option to see listening
ports? "netstat -a" I believe

Quote:

I have pasted a copy of what netstat returned below. Took a long
time to gather this info - probably 3-4 minutes. My local servers
take only seconds. Does that sound normal?



I don't know about the time to gather the netstat -- can't comment on
whether it is normal or not.



--
Brian Sullivan
Meeting by Wire ( http://www.meetingbywire.com)
------------
Is your PC protected? --
http://www.microsoft.com/security/protect/default.asp
Back to top
Neil Smith [MVP Digital M
Guest





Posted: Wed May 12, 2004 1:20 am    Post subject: Re: How do I fix "Netmeeting could not start." problem? Reply with quote

Looks to me like you have an LDAP server listening on the local
machine. If it's using port 389 (netstat -an to get port #numbers#)
then it might conflict with Netmeetings anticipated ability to open
outbound on port 389 for ILS connections. That could be the cause of
'could not start'. Hope that helps

Neil

On Tue, 11 May 2004 14:20:32 -0500, "Richard Sutterfield"
<richardnospam@kellpro.com> wrote:

Quote:
"Brian Sullivan MVP" <brians@WORMTIREDmeetingbywire.com> wrote in message
news:%23dAdpQ4NEHA.2560@TK2MSFTNGP11.phx.gbl...

I don't know of any specific "NetMeeting could not start." problem.

I know such a message can appear if there is some other program using tcp
1503 ( the T.120 port) when NetMeeting starts. I can't think of why a
reboot
would solve the problem ( unless it just shuts down the program causing
the
problem).

Is there some other program listening on tcp 1503 ( try a netstat to see)?


Nothing is listening on 1503.

I have pasted a copy of what netstat returned below. Took a long time to
gather this info - probably 3-4 minutes. My local servers take only
seconds. Does that sound normal?

Thanks again.

Active Connections

Proto Local Address Foreign Address State
TCP nt4server:ldap nt4server.LCCLERK.ORG:1089 ESTABLISHED
TCP nt4server:ldap nt4server.LCCLERK.ORG:1090 ESTABLISHED
TCP nt4server:ldap nt4server.LCCLERK.ORG:1092 ESTABLISHED
TCP nt4server:ldap nt4server.LCCLERK.ORG:1118 ESTABLISHED
TCP nt4server:1089 nt4server.LCCLERK.ORG:ldap ESTABLISHED
TCP nt4server:1090 nt4server.LCCLERK.ORG:ldap ESTABLISHED
TCP nt4server:1092 nt4server.LCCLERK.ORG:ldap ESTABLISHED
TCP nt4server:1118 nt4server.LCCLERK.ORG:ldap ESTABLISHED
TCP nt4server:1467 nt4server.LCCLERK.ORG:ldap CLOSE_WAIT
TCP nt4server:netbios-ssn LEFLORE-F6WAJ2N:2324 ESTABLISHED
TCP nt4server:netbios-ssn KELLI:1094 ESTABLISHED
TCP nt4server:netbios-ssn PUBLIC:1031 ESTABLISHED
TCP nt4server:netbios-ssn FRAN:1041 ESTABLISHED
TCP nt4server:ldap nt4server.LCCLERK.ORG:1131 ESTABLISHED
TCP nt4server:ldap nt4server.LCCLERK.ORG:1693 TIME_WAIT
TCP nt4server:ldap nt4server.LCCLERK.ORG:1694 TIME_WAIT
TCP nt4server:ldap nt4server.LCCLERK.ORG:1699 TIME_WAIT
TCP nt4server:ldap nt4server.LCCLERK.ORG:1700 TIME_WAIT
TCP nt4server:ldap nt4server.LCCLERK.ORG:1715 TIME_WAIT
TCP nt4server:ldap nt4server.LCCLERK.ORG:1716 TIME_WAIT
TCP nt4server:ldap nt4server.LCCLERK.ORG:1718 TIME_WAIT
TCP nt4server:microsoft-ds nt4server.LCCLERK.ORG:pptp ESTABLISHED
TCP nt4server:1026 nt4server.LCCLERK.ORG:1133 ESTABLISHED
TCP nt4server:1026 nt4server.LCCLERK.ORG:1265 ESTABLISHED
TCP nt4server:1131 nt4server.LCCLERK.ORG:ldap ESTABLISHED
TCP nt4server:1133 nt4server.LCCLERK.ORG:1026 ESTABLISHED
TCP nt4server:1223 POPSERVER_0087:netbios-ssn ESTABLISHED
TCP nt4server:1261 nt4server.LCCLERK.ORG:ldap CLOSE_WAIT
TCP nt4server:1265 nt4server.LCCLERK.ORG:1026 ESTABLISHED
TCP nt4server:ms-sql-s LEFLORE-F6WAJ2N:2325 ESTABLISHED
TCP nt4server:ms-sql-s KELLI:1095 ESTABLISHED
TCP nt4server:ms-sql-s PUBLIC:1067 ESTABLISHED
TCP nt4server:ms-sql-s FRAN:1049 ESTABLISHED
TCP nt4server:1689 nt4server.LCCLERK.ORG:microsoft-ds
TIME_WAIT
TCP nt4server:1690 nt4server.LCCLERK.ORG:epmap TIME_WAIT
TCP nt4server:1691 nt4server.LCCLERK.ORG:1026 TIME_WAIT
TCP nt4server:1695 nt4server.LCCLERK.ORG:epmap TIME_WAIT
TCP nt4server:1696 nt4server.LCCLERK.ORG:1026 TIME_WAIT
TCP nt4server:1702 192.168.1.30:printer TIME_WAIT
TCP nt4server:1703 PUBLIC:netbios-ssn TIME_WAIT
TCP nt4server:1706 192.168.1.30:printer TIME_WAIT
TCP nt4server:1707 PUBLIC:netbios-ssn TIME_WAIT
TCP nt4server:1710 192.168.1.30:printer TIME_WAIT
TCP nt4server:1711 PUBLIC:netbios-ssn TIME_WAIT
TCP nt4server:1717 nt4server.LCCLERK.ORG:microsoft-ds
TIME_WAIT
TCP nt4server:1721 192.168.1.30:printer TIME_WAIT
TCP nt4server:1722 PUBLIC:netbios-ssn TIME_WAIT
TCP nt4server:pptp nt4server.LCCLERK.ORG:microsoft-ds
ESTABLISHED
TCP nt4server:1724 nt4server.LCCLERK.ORG:epmap TIME_WAIT
TCP nt4server:1725 nt4server.LCCLERK.ORG:1026 TIME_WAIT
TCP nt4server:1726 nt4server.LCCLERK.ORG:epmap TIME_WAIT
TCP nt4server:1727 nt4server.LCCLERK.ORG:1026 TIME_WAIT
Back to top
Alejandro Madrigal
Guest





Posted: Fri May 21, 2004 7:07 am    Post subject: Re: How do I fix "Netmeeting could not start." problem? Reply with quote

The Netmeeting Remote Desktop Sharing service is set to start on automatic and is running. Stopping the service and setting it to start manually should fix the problem.
"Richard Sutterfield" <richardnospam@kellpro.com> escribió en el mensaje news:uzv2b83NEHA.2716@tk2msftngp13.phx.gbl...
Hello all,

I have a Windows 2000 Server that has recently begun giving an error at boot up. The error is "Netmeeting could not start. Please restart your computer and try again."

Restarting has fixed the problem a few times but is now failing to help.

The server is running SP2 and hasn't had any new software installed that I know of.

This is a remote machine that I use Terminal Service to connect to and then use Netmeeting to connect to workstations on the LAN to do remote support.

Any ideas on how to resolve this?

Thanks for any help.
Back to top
 
Post new topic   Reply to topic    DComTalk.com Forum Index -> Netmeeting All times are GMT
Page 1 of 1

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum




VoIP Solutions: Telephone Systems Electronics Satellite TV Tech & Gadgets
Powered by phpBB