Re: IIS and port 1029? by Ken
Ken
Sun Aug 01 18:59:25 CDT 2004
Hi,
I can't point you to a URL, but you'll find a lot of systems that work this
way. Ports > 1024 (high order ports) are dynamically allocated, so if you
have a service or app that needs remote administration it will use a port >
1024. This port may vary from reboot to reboot depending on what other
services also need ports - as the services start up, they request a high
order port from the OS, and bind to it.
On Windows, the RPC Port Mapper service on port 135 tells your remote admin
tool which high-order port to connect to. So, if you open IIS Manager on a
remote machine, and decide to admin your server. It will connect to port 135
on the server to find out what port IISAdmin is listening on, and then
connect to that port.
Cheers
Ken
"tommys" <someone@microsoft.com> wrote in message
news:%23dS7j%239dEHA.3632@TK2MSFTNGP11.phx.gbl...
> Ok, when I stopped IIS Admin Service, inetinfo stopped listening on port
> 1029. Fine.
>
> However, I have noticed that after a reboot inetinfo is listening on 1029
> but after a restart of the inetinfo related services, inetinfo is
listening
> on a port different from 1029, e.g. 1076!?
>
> Hmm... Where can I find documentation on this behaviour?
>
> /TommyS
>
>
>
> > Possibly to allow remote administration via RPC
> >
> > Cheers
> > Ken
> >
> > "tommys" <tommys@discussions.microsoft.com> wrote in message
> > > Hi,
> > > on my w2k system I noticed that port 1029 is opened.
> > >
> > > TcpView (from SysInternals) reports that the process which listens on
> port
> > 1029 is inetinfo.exe
> > >
> > > Why is IIS listening on this port?
> > >
> > > /Tommy
> >
> >
>
>