paulfryer
asked on
Can't connect to SQLServer db via Enterprise manager on another PC
I have a new server with sql server db on it - it also has a web site that will eventually access that db, but right now is little more than a dummy place holder.
I can use SQL locally on the server, but can not connect to it via remoe pc using enterprise manager.
Some people can ping my server ip, some can not.. All can get into my web site, none can conenct to my sql server
In the sql server logs it does not say it is scanning the external ip for commands, ony the internal (192.168.0.2) and local (127.0.0.1) ips.
From my remote laptop, I can use enterprise manager and get into many other databases across the country - just not this one.
Have been fighting this for 3 days now
I can use SQL locally on the server, but can not connect to it via remoe pc using enterprise manager.
Some people can ping my server ip, some can not.. All can get into my web site, none can conenct to my sql server
In the sql server logs it does not say it is scanning the external ip for commands, ony the internal (192.168.0.2) and local (127.0.0.1) ips.
From my remote laptop, I can use enterprise manager and get into many other databases across the country - just not this one.
Have been fighting this for 3 days now
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Have you ran a port scanner? Is the port 3306 open or is there a firewall in the way?
Oops 3306 is the MySQL port. MSSQL uses TCP 1433, 1434 and others
With PHP:
mssql_connect in version 4.2.1 seems to insist on using named pipes to connect to the SQL Server. This is not secure as it requires netbios browsing (tcp/udp ports 137, 139, and 445 (with windows2000)).
With PHP:
mssql_connect in version 4.2.1 seems to insist on using named pipes to connect to the SQL Server. This is not secure as it requires netbios browsing (tcp/udp ports 137, 139, and 445 (with windows2000)).
Is SP3 installed?
What is the exact error message?
Are you local to the SQL Server (same LAN)?
If Win2K3 and no sp3, that may very well be it....TCP communications are blocked until after sp3 install. Just a wild guess until I see the error message :-)
Kevin3NF