Make sure that the SQL Browser is enabled and running. It's probably disabled or stopped.
Also make sure that the instance is configured to allow remote connections.
I think i can tell you exactly what the issue is,
I spent over 48 hours trying to sort this. didnt find anything on the net. also happen to be with 1and1
look at these settings:
IP security policies.....
which opens box...............Packet Filter Properties
near the bottom of the list there is a box ticked called :
'Close MSDE (TCP/UDP)' (I am asuming that MSDE = Microsoft SQL Database Engine?)
Select it
Press Edit...
which opens box............... Edit Rule Properties
Select (again) >> 'Close MSDE (TCP/UDP)'
Press Edit...
which opens box................IP filter List
then you will see a list of ports tcp 1433, udp 1434
{Thats our list of ports all down as a blocking rule.....}
I think what needs to be done from here is
either....
close that screen ..IP filter List
on the screen Edit Rule Properties
there is a tab Filter action, could just change that from Block to permit?
(maybe changing it to permit, will allow us to tick the "Block All" option again - which sounds safer, but the support guys said there is a know bug, so might not work)
or
on the Packet Filter Properties
just untick the the rule 'Close MSDE (TCP/UDP)'
you might have to untick the rule 'Block ALL' to get it running
its probably to late for this to help you, but hopefully will help someone else with the same issue.
Best Answer
OK, so the path is:
client --> CCProxy --> SQL Server
Right?
First step is probably to use telnet to walk the walk:
On proxy box:
telnet sql-server-host 1433
(Or whatever your sql server port is, if not sure, check errorlog on sql server to see what port it is listening on)
If that telnet connects, the next step is to telnet from client to ccproxy, which should cause connection to go through ccproxy to sql server.
This should help surface where the issue is.