SQL Program Login problem
We have two instances of SQL 2005 running. One is 2005 Express (Timeforce) and the other is the main instance (Fusion database). We had everything working by disabling the firewall for several months but now we are getting attacked from at external IP on the SA account of both instances so we enabled the Windows Server 2003 firewall. The Timeforce SQL still works for my remote users but the Fusion SQL database won't let my remote users login to the SA account from the application they need to run. I don't see where there are any specific entries in the firewall for either instance of SQL. How can I check to see why the remote users can't login to the Fusion instance under the SA account. The app that accesses the Fusion DB does run fine on the server itself.
Thanks
Thanks
Faiga Diegel
What error are you getting when they try to access using SA? Can you post the error message? It might be only a matter of SQL Authentication mode. Check if you have both the windows account and SQL authentication enabled.
ASKER
Attached are the error logs
SQL-Error-Message.bmp
SQL-Error-Message.bmp
ASKER
error code #2
SQL-Error-Message--2.bmp
SQL-Error-Message--2.bmp
Well the Fusion one is using the default port of 1433 and that will be blocked by the firewall where it was not being blocked before. The other one is using 1474 as a dynamic port and depending on whether you have SQL Browser enabled or not (I am guessing that you do since the others are able to get in to that application), the users will not see problems getting into the 1474 port.
Now, you could add a rule in the firewall for allowing 1433 port through as well as UDP 1434, but then they would be able to attack again as if the firewall was disabled.
So you either need to change the port that SQL runs on to a non-standard port than 1433 and then you could specify that port number when trying to connect.
corsair,1499
Now, you could add a rule in the firewall for allowing 1433 port through as well as UDP 1434, but then they would be able to attack again as if the firewall was disabled.
So you either need to change the port that SQL runs on to a non-standard port than 1433 and then you could specify that port number when trying to connect.
corsair,1499
ASKER
The hits are really a problem. Once I disable the firewall I literally get thousands of hits within minutes on both instances of SQL. Since the TIMEFORCE instance is running on a non-standard port why is it getting hit? Also do you recommend moving both instances of SQL to different ports? We also are letting 1433 traffic through our router. Shall I shut that down?
Thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I can't ping the corsair server but I can Remote Desktop into it from my home via a VPN. I can ping all the other servers at the office. What on the Windows Firewall settings would cause this, With the Firewall turned off pinging is no problem.
there is protocol called ICMP that is the ping responder and it could be blocked.
ASKER
Do you know where in the ICMP panel I can turn the pinging reply back on?
When you go into Windows Firewall on Windows 2003 Server you will see an Advanced tab. On the advanced tab you will see a section on ICMP. There will be a Settings button that will allow you to tell Windows how to respond to Ping requests. Check the boxes you want to allow and then save it. You should then be able to ping it.