I’m having a problem on a server. Here’s the situation, I have Windows Server 2008 Standard (pre-R2) server with Hyper-V enabled and SQL Server 2005 Standard installed. SQL hosts a couple of large databases. Hyper-V hosts one virtual server. All of this runs on a Dell R 710 server with 24GB of memory and a single Quad-core CPU (w/ hyper threading) and 4 physical NICs. One NIC is dedicated to the LAN. One is dedicated to Hyper-V (setup as external in Hyper-V manager). And one is (trying) to be dedicated to an iSCSI connection.
When I enable the iSCSI interface, with either IPV6 or IPV4 enabled, SQL will no longer respond to network requests (I tried using named pipes and tcp/ip). I can connect to SQL from the local host (over named pipes and tcp/ip). The SQL ERRORLOG shows SQL listening on tcp:1433 and named pipes. It also shows clients logon requests being granted. However, from client systems the logon timeouts. Using Wireshark on both client and server, I can see the initial logon request, but no response is ever sent by the server. I’ve tried disabling ‘remote connections’ and ‘tcip/ip’ on SQL Configuration after starting the iSCSI interface, then restarting SQL services, and re-enabling ‘remote connections’ and ‘tcp/ip’ in SQL Configuration, and concluding with a SQL restart. That didn’t help at all.
Last Friday I tried cleaning up the list of ‘TCP/IP’ addresses in ‘TCP/IP Properties’ in “SQL Configuration Manager”. I made sure that only the real IP addresses that are on the server are listed, and that the IP address for iSCSI port was disabled. Unfortunately, this didn’t help either. I’m stuck and this is preventing me from going forward with an important project.