Are port numbers supported in server principal names?

Microsoft's ODBC driver for SQLServer appends a port number after a colon to the domain name in a service principal name, as in MSSQLSvc/db0.ad.cl.cam.ac.uk:1433@ ^ and even relies on that port number to distinguish different service instances on the same hos

Re: Are port numbers supported in server principal names?

On 03/27/2018 11:02 AM, Markus Kuhn wrote: > For example, the above SPN works in kvno (krb5-1.13.2, Ubuntu 16.04) > only after I remove the port number (whereas both SPNs are registered > in our Active Directory KDC): > > $ kvno MSSQLSvc/db0.ad.cl.cam.ac.uk:1433@ > kvno: Server not found in Kerber

Re: Are port numbers supported in server principal names?

On Tue, Mar 27, 2018 at 6:02 PM, Markus Kuhn wrote: > Microsoft's ODBC driver for SQLServer appends a port number > after a colon to the domain name in a service principal name, > as in > >MSSQLSvc/db0.ad.cl.cam.ac.uk:1433@ >^ > > and even relies on that por

Re: Problems with kinit invocations

I’ve noticed that the kinit failures correlate to situations in which TCP fails and UDP is used. In every case when the client waits a second and switches to UDP the kinit invocation fails. Does this ring any bells? > On Mar 26, 2018, at 10:35 AM, Jonathan Maron > wrote: > > > >> On Mar 2