November 22, 2007 at 8:01 pm
Hi all, very new in this, not a dbase admin. myself, so i will make this less painful
and brief. i have accidentally change my server from domain to workgroup and now i can't access my website which returning below error:
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
Please any help to rectify this would be greatly appreciate. Thank you much in advanced.
November 23, 2007 at 3:11 am
Umm.. well, you already know that you have accidentally removed the server from it's domain.
Have the server join that domain again and see if that fixes things back as they were?
/Kenneth
November 23, 2007 at 3:15 am
Dear Kenneth,
thanks for the reply...umm....forgot to mentioned that the domain is no longer
available as the other n/work engineer has shut the Domain Controller server down....i'm screwed aren't i?
November 23, 2007 at 3:23 am
Is this 'shut down' part of the 'accident' or is it on purpose?
You obviously have a network connection/authentication problem.
In order to fix it, you need first to sort out how it's supposed to work/be configured.
ie - all those security related questions and answers that need answers before
anyone knows what and how things needs to be done to 'make it work'.
/Kenneth
November 23, 2007 at 3:31 am
Dear Kenneth,
the 'shut down' is part of the plan..thing is i can access the server locally/remotely...it is a webserver that has sql engine behind it..so when i accidentally moved it from domain to workgroup i can access other websites that hosted inside that machine..only the one with the sql engine can't be accessed...thanks again Kenneth..
November 23, 2007 at 3:42 am
Well, the biggest difference between a domainserver and a local server (workgroup) is that all authentication is performed locally on the workgroup server.
Check your logins and security settings (accounts etc) and see if they are there.
Also, do as the error suggests (never hurts) and see if there's anything up with the named pipes settings on the sql server (does it listen to that protocol or only tcpip..?)
This is one of those things that need testing before shutting down a domain 😉
/Kenneth
November 23, 2007 at 3:53 am
Thank you so much Kenneth..i will check and revert back to you the result..
November 29, 2007 at 6:37 pm
Dear Kenneth,
Thank you, thank you, thank you sooo soooo much....problem solved.....i accidentally rename the server to something else....forgot about that....i've changed it back and everything is aok.....thanks for the concerns man....
p.s. feels like couldn't thank you enough!...
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply