How to configure SQL Server database mirroring between 2
instances on a standalone server     • Comments 1  There are
lots of troubleshooting articles about how to diagnose
connectivity problems when setting up database mirroring,
especially errors such as these:  Msg 1418, Level 16, State 1,
Line 2  The server network address "tcp://" can not be reached
or does not exist. Check the network address name and that the
ports for the local and remote endpoints are operational.   Msg
1456, Level 16, State 3, Line 1   but here's something a little
different.  Imagine that you have a server which is not
connected to a domain. It might just be a standalone machine, it
could be a virtual machine that you've just built. I've done
this a few times in virtual environments to do demos on laptops
and the like. It's a not a production scenario that you'd come
across really, but it works really well in test.  The questions
that usually come up are how can I configure the partners (and
endpoints) without having a FQDN, since