Disabled SQL Server Endpoint - now I cannot login

I have SQL Server 2005 on my local machine. During the studies of SQL Server network configuration, I logged into my SQL Server Instance and ran the following script:

USE Master;
GO

ALTER ENDPOINT [TSQL Default TCP]
STATE=STOPPED;

After that I am unable to login. I can't even login using Windows authentication.

How can I revert the change above? Is there any another way to fix this situation?

STATE = STOPPED on the [TSQL Default TCP] endpoint prevents the SQL Server service from listening for incoming connections via TCP. You have several options available that will allow you to reverse this.

-
Connect with the DAC dedicated admin connection. You can connect to the DAC by specifying the name of the server as: ADMIN:MyServerName. Once connected to the DAC, you should be able to start the endpoint again with the following statement:

ALTER ENDPOINT[TSQL Default TCP] state = started;

-
Use named pipes to connect to SQL server. Use SQL Server
Configuration Manager to enable named pipes if disabled.

StackExchange Database Administrators Q#23703, answer score: 4