Port 1720 won't shutdown after Service Pack upgrade ?
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
Port 1720 won't shutdown after Service Pack upgrade ?

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





Posted: Thu Feb 26, 2004 8:42 pm    Post subject: Port 1720 won't shutdown after Service Pack upgrade ? Reply with quote

Hello,

We have this problem and because of that we can't use any H.323 application
such as a gatekeeper or ATA, etc. It happens since we upgraded the Win 2K
server to SP4 last week.

Here is what we found out up to now, it is really strange and would
appreciate if someone could give us a hint at least on that one. So
here are the hard facts:

- There is no application running on the server
- Using "netstat -a" no application/service is listening on port 1720
- Using Telnet to 1720 from a client, we connect successfully to the server
- Doing "netstat -a" again on the server, we see that we are connected
to port 3001 (!), however on the client side, netstat shows port 1720
- Using XPort to identify who is listening on port 3001, we see that
it's a generic service (scvhost) which loaded at least 20 dll's at
windows startup
- Killing this process using XPort, shuts down the following windows
services (as reported by event log):
1- System Event Notification
2- Routing and Remote Access
3- Remote Access Connection Manager
4- Removable Storage
5- Network Connections
6- COM+ Event System
- Doing telnet on port 1720 from the client workstation now
shows us that nobody is listening anymore on port 1720 (!) it
has been freed by killing the svchost process.

Now:

Rebooting the machine leads us to the same situation even if
Netmeeting is desintalled and the Netmeeting Desktop Sharing
Service is Disabled.

So I am asking, what is happening here ! :-)

Anyone has an idea ?

Thanks for any help.

p.s. carbon copy any answers to my e-mail below please.

Frederic Jean
fjean@sun.net.bb
Back to top
Frederic
Guest





Posted: Fri Feb 27, 2004 8:10 pm    Post subject: Re: Port 1720 won't shutdown after Service Pack upgrade ? Reply with quote

Sorry all, it seems that Netmeeting is still installed, we didn't
find a way to desinstall from the server since it is not available
from the control panel. The Remote Desktop Sharing is however
disabled.

Anyone has an idea who is listening on that port ? no application
is running, Remote Desktop is disabled but there is still a
Windows process that listens to 1720.

Thanks for any advice.

Frederic


fjean@sun.net.bb (Frederic) wrote in message > Hello,
Quote:

We have this problem and because of that we can't use any H.323 application
such as a gatekeeper or ATA, etc. It happens since we upgraded the Win 2K
server to SP4 last week.

Here is what we found out up to now, it is really strange and would
appreciate if someone could give us a hint at least on that one. So
here are the hard facts:

- There is no application running on the server
- Using "netstat -a" no application/service is listening on port 1720
- Using Telnet to 1720 from a client, we connect successfully to the server
- Doing "netstat -a" again on the server, we see that we are connected
to port 3001 (!), however on the client side, netstat shows port 1720
- Using XPort to identify who is listening on port 3001, we see that
it's a generic service (scvhost) which loaded at least 20 dll's at
windows startup
- Killing this process using XPort, shuts down the following windows
services (as reported by event log):
1- System Event Notification
2- Routing and Remote Access
3- Remote Access Connection Manager
4- Removable Storage
5- Network Connections
6- COM+ Event System
- Doing telnet on port 1720 from the client workstation now
shows us that nobody is listening anymore on port 1720 (!) it
has been freed by killing the svchost process.

Now:

Rebooting the machine leads us to the same situation even if
Netmeeting is desintalled and the Netmeeting Desktop Sharing
Service is Disabled.

So I am asking, what is happening here ! :-)

Anyone has an idea ?

Thanks for any help.

p.s. carbon copy any answers to my e-mail below please.

Frederic Jean
fjean@sun.net.bb
Back to top
Brian Sullivan MVP
Guest





Posted: Fri Feb 27, 2004 8:25 pm    Post subject: Re: Port 1720 won't shutdown after Service Pack upgrade ? Reply with quote

Frederic wrote:
Quote:
Sorry all, it seems that Netmeeting is still installed, we didn't
find a way to desinstall from the server since it is not available
from the control panel. The Remote Desktop Sharing is however
disabled.

Anyone has an idea who is listening on that port ? no application
is running, Remote Desktop is disabled but there is still a
Windows process that listens to 1720.


What happens if you actually run NetMeeting? Does is start up and appear to
run normally( with audio/video function enabled)?

To guarantee the RDS is not enabled go to the Tools->Options->General Tab.

Select "Run NetMeeting in the background", then unselect it. That should
guarantee that NetMeeting does not run in the background for any reason.

Another application that could take over the H.323 port is the TAPI3 client
"dialer.exe".




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





Posted: Sun Feb 29, 2004 2:28 am    Post subject: Re: Port 1720 won't shutdown after Service Pack upgrade ? Reply with quote

Well actually, I tried to desinstall Netmeeting, but it however used to work
with the video function enabled with no audio because there is no sound
card on the server, so it seemed to be OK. The RDS wouldn't start with an
unidentified error code, most probably because port 1720 is already busy.

Dialer.exe is not working, but listen to this, this is too cool ; the server has
IIS on it so it listens to port 80 and when I shutdown the Routing and Remote
Access service from the Services window, port 1720 is freed ; I could however
still can use port 80. I bring it back up, 1720 is then occupied....!

So that means that from the Services listed above that stop when I kill
the Svchost service, it's the Routing and Remote Access service that
ir responsible for the listening on port 1720.

Another funny thing is that here on the Island of Barbados, there is an
article that appeared in the papers this morning stating that all
Internet Cafes could not provide international calls anymore because
their port would be blocked. Most of them are however not system
administrators so it would be difficult to find if there was a bug
on their machine. But there all aiming at governement policies on
that restrict international calls and that they would have blocked
port 1720. But...

So I am not sure if everybody applied the same patch at the same time
or if we all got a virus but I am really not convinced that it's an
ISP issue or governement issue since I have been able to free my port
when shutting down the service.

Anyway, we lost several days over this and we are now going to
reinstall the server. I will let you know what happened tomorrow.

Frederic
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