Also: Make sure you enabled 'Allow remote connections'. If the server is a named instance (e.g. myserver\instance) make sure the SQL Server Browser service is running (this bit me yesterday).
Paul On Thu, Feb 16, 2012 at 6:12 AM, Alan Bourke <alanpbou...@fastmail.fm> wrote: > > Did you enable named pipes and TCP inthe SQL protocols? > On Wed, Feb 15, 2012, at 06:02 PM, José Olavo Cerávolo wrote: >> Hi Guys, >> >> I installed a new environment for development with SQL Server 2008 R2 on >> Windows Server 2008 R2. >> I have a Windows 7 machine on the network. I can see the server on the >> network. >> I even mapped the server's S: drive on the W7 machine. >> I opened port 1433 on the server and on the W7, but I can't connect to >> the SQL with SQL Server Management Studio. >> I can connect fine inside the SQL server. It's up and running and I can >> use SSMS there. >> I've been all over the web looking for a solution, but I could not find >> anything that would help. >> If I am not supposed to post about SQL server here, let me know. >> >> Thanks! >> >> Jose. >> >> --- StripMime Report -- processed MIME parts --- >> multipart/alternative >> text/plain (text body -- kept) >> text/html >> --- >> [excessive quoting removed by server] _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/CADwx0+KZrn=cro7bi2npgraq+mnzuhwiukrdj-ompzbkw7y...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
