Hi Kiran, I did start the server as a superuser to have it deliver ldap services on port 389 and 636. After having started up the server again and access it with Studio I changed the port of the KDC transports to 88.
2012/1/20 Kiran Ayyagari <[email protected]> > On Fri, Jan 20, 2012 at 12:37 PM, Pierre Smits <[email protected]> > wrote: > > Hi All, > > > > I am currently testing the M3 version of ADS 2.0 and came to a halt. > > > > I changed the port of the KDC server to 88 after doing a portscan of > ports > > in use. When I restarted ADS it came to a dead stop... > > > > Shouldn't it be so that it only disables the service (or service) and > > continue on starting up? Or that it reverts to the initial setting of the > > transport, so that I can still access it with AD Studio to correct the > > error? > > > that can be an option but it masks the real issue, I would personally > prefer it to stop > completely in such situations. > OTOH, I believe you haven't started the server as super user after > changing KDC config to use the well-known port > > Regards, > > > > Pierre > > > > -- > Kiran Ayyagari >
