Hi all, thanks for the responses. 1. Yeah we did this and quadruple checked :-) 2. Quadruple checked this as well and it is enabled. 3. Not certain on this yet but will check it out. There have however been various revelations: I knocked up a little .net 1.1 windows app as a connectivity tetsing tool using the connection strings used in dnn and result was that where ever I try this from on the network it works EXCEPT on the web server in question. How frustrating. Anyhow a network guy has since discovered that if you specifically force the port to 1433 when trying from the web server all is well. I have tried it and this works but the question of course is why do i need to specify the port when connecting from the web server and not from anywhere else? Very very odd indeed.... Result is that if i modifiy the connection string in web.config to specify port it works fine. I must however add that these sql servers are NOT set to listen only on that port....

makes sure, the sql server is configured to access remote connections and full database permissions (dbowner) have been granted to the SQL server user.

---

Cheers from Germany,
Sebastian Leupold

   

Speed up your DNN Websites with TurboDNN