We had case like this one. Stop the mad.exe first and restart the RRAS. Or
this post may help.
Mad.exe uses port 1723 so that PPTP doesn't work
http://chicagotech.net/netforums/vie...hp?p=6812#6812
--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"hemo_jr" <(E-Mail Removed)> wrote in message
news:5e2a9295-f431-4f5e-8e53-(E-Mail Removed)...
> This morning after the "Patch Tuesday" reboot RRAS on one of our
> servers stopped accepting connections. RRAS on this server had been
> working for years.
>
> A portqry check from a local machine showed the PPTP port (1723) in a
> "NOT LISTENING" state (remote portqry shows port 1723 as "FILTERED").
>
> I used a utility named currports and it is showing port 1723 as being
> owned by mad.exe (the Exchange System Attendant). So it looks like
> Exchange is blocking RRAS from listening on port 1723. Exchange has
> been running on this server for years as well.
>
> The server is Windows 2003 server SP2 and Exchange is version 2003
> SP2.
>
> Any ideas on why Exchange would pre-empt port 1723 or how to configure
> things so there is no conflict would be appreciated. Thanks.
>
> --
> Matt Hickman
Similar Threads
Linear Mode
