Hi,
I didn't get much help after extensive search. So thought of bringing a silly question infront of master minds.
Recently, we secured SQL Server with non-default port# (3890), disabled SQL Browser, disabled "Shared memory" protocol, disabled "Named Pipes" protocol. Finally, there is no way to connect to SQL Server without mentioning the port# and I confirm that dynamic ports are not configured.
I was very proud of what I did until I opened "SQLCMD". I opened it in the command prompt and typed "sqlcmd" without any parameters, not even a server name, login name, password or port#. It straight away connected to the local SQL Server with Windows authentication and I was able to do all operations just like any "sysadmin" does.
My question is how to enforce to use the port# while using "SQLCMD"?
If you feel that I have answered your question then please "Mark as Answer".