Can't connect to SQL Server 2008 after P2V migration

Our server was migrated from a physical server to a virtual server and now we can't connect to SQL Server. We keep getting this error:

"A network-related or instance specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that the SQL Server is configured to allow remote connections. (Provider (TCP Provider, error: 0 - Only one usage of each socket address (protocol/network address/port) is permitted.) (Microsoft SQL Server, error 10048)

I checked and TCPIP is enable and the SQL Server process is running.
I can login to the server but I can't connect to SQL Server either using Windows authentication or database authentication.

What is missing here?

TIA!
data_bitsAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
Jeff PerryConnect With a Mentor Windows AdministratorCommented:
The 10048 error is a port in use error.

Something on the SQL server is already using the port that SQL is trying to start on.
0
 
David KrollCommented:
0
 
Jeff PerryConnect With a Mentor Windows AdministratorCommented:
Have you tried changing the port?

Something seems to have happened during the conversion that is telling SQL that the default port is in use.
0
What Kind of Coding Program is Right for You?

There are many ways to learn to code these days. From coding bootcamps like Flatiron School to online courses to totally free beginner resources. The best way to learn to code depends on many factors, but the most important one is you. See what course is best for you.

 
Miguel Angel Perez MuñozCommented:
Maybe is bind to older IP?
0
 
data_bitsAuthor Commented:
This just in, apparently it was not migrated to a VM. There are two servers with very similar names, one of which was migrated. This one that we're getting the 10048 error on, was not migrated.

However, it is suspicious that this one started to have problems after the other one was migrated.

Could a duplicate IP# cause this behaviour?
0
 
data_bitsAuthor Commented:
The decision was made to reboot the server since it had been up for a while.

When it came back up, everything was accessible.

Thanks everyone for the input.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.