How to enable remote connections in SQL Server 2008?

Random socket connection failures in a VMWare VM - What might be causing it?

• Here's a product I am looking into, that is a suite of services written in different languages. These services talk to each other over TCP socket connections. When the product is run on VMWare (Windows 2008 64 bit on an ESX host), sporadically we see socket connection failures. For example, a middle tier component won't be able to connect to Oracle database server (running locally), which fails with exception likejava.sql.SQLException: Io exception: The Network Adapter could not establish the connection Sometimes socket connections keep failing for several minutes. During this time some other bizarre behaviors are observed as well. One of them is simple WQL queries such asselect Status from Win32_ComputerSystem against the localhost failing with timeout errors. This seems to be due to VM resource constraints. Is there a way to assert this? Are there any special considerations while writing applications that may need to run on virtual environments? Also, is the number of sockets available more limited on a VM as compared to a real box? When I ran 'netstat -a' I got about 650 records. The breakup of various states is as follows:CLOSE_WAIT - 115 ESTALISHED - 248 FIN_WAIT_2 -   4 LAST_ACK   - 130 LISTENING  -  75 TIME_WAIT  -  80

• Answer:

  Hi, Is it possible that you have a duplicate copy of the VM running somewhere by mistake, causing a MAC and IP address conflict? This is what I've stumbled across last week.