Re: can't connect to vpn if a service listens on port 1723

Hello Scott,
you were right, the port 1723 is used after the VPN connection is
established...
Every thing's clear now.
Thank you for your help,
kind regards,
Olivier.

Scott Harding a écrit :

That's what I meant. The client has some issue. I don't know of any service
that would be listening. The VPN doesn't grab the port until you start the
connection. Do the netstat command on the client to see what is holding the
port.

--
Scott Harding
MCSE, MCSA, Net +, A+
MVP - Windows Server Networking

<ggo98@xxxxxxxxx> wrote in message
news:1160151967.231319.220010@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi Scott,

no, this is not the problem I believe: the service listening on the TCP
port 1723 is started on the client side, not on the win2003 server
side...
or there's may be something I don't know...
does the client need to listen on port 1723 at some point of the
negociation ?
AFAIK, the client connects on port 1723 on the server, right ? so why
would a service listening on port 1723 on the client side be a problem.

Regards,
Olivier.


Scott Harding a écrit :

I would imagine that that service is holding the port hostage basically
and
not letting the VPN connection use it. This is not uncommon.

--
Scott Harding
MCSE, MCSA, Net +, A+
MVP - Windows Server Networking

<ggo98@xxxxxxxxx> wrote in message
news:1160033043.800654.188180@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
hi,

thank you for your answers.

well I actually do know which service listens on port 1723.
What I don't get is why does the VPN connection to the win2003 server
fails if the service listening on port 1723 is started on the winXP
client ?

Thank you,
regards,
Olivier.


.

Relevant Pages

  • Re: Remote Desktop to a Client of a Windows Server network
    ... which client is which port number. ... I prefer a VPN connection. ... We are running Server 2000 in the office. ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: file sharing issue
    ... Following KB articles might help with the detailed port numbers: ... The following ports are associated with file sharing and server message ... if i disabled the netbios under the VPN connection at ...
    (microsoft.public.windows.server.active_directory)
  • Re: CompanyWeb access
    ... Port 443 was being forwarded, ... However, since other remote sites are connecting without any issues, I have ... I have a remote site that has been using a VPN connection to ... However, since changing out their old router with a new Westell 7500, things ...
    (microsoft.public.windows.server.sbs)
  • Re: Two LANs behind a single Router - How to setup VPNs for both?
    ... I can't see this working easily as apart from TCP 1723 the other part of the PPTP protocol is GRE You could keep PPTP VPN on the existing server then setup the new one to use L2TP/IPSEC, this uses different ports so the router won't get confused and still makes use of the client inbuilt into Windows machines. ... We have this setup to allow a VPN connection remotely, and the only ports forwarded to LAN1 ... I now need to add a server to the second LAN port on the router which will be totally separate from the first LAN / Domain and setup VPN access to that server too. ...
    (microsoft.public.windows.server.sbs)
  • RE: VPN Connection Problem
    ... Here is the PPP log from the server after a VPN connection and disconnection: ... port = 6 ...
    (microsoft.public.windows.server.sbs)
Loading