Board index » delphi » MSDE and Firewall

2005-09-26 06:06:36 PM
delphi103
We've had a problem recently at a customer site where they had a problem
with their internet connection which then seemed to cause a connection error
within our application. We use ADO to connect to an MSDE database. The two
pc's are in a workgroup. The main pc with the database installed is fine but
the other one cannot connect unless the windows firewall is switched off.
I've tried adding the port to the list of exceptions which has worked here
and elsewhere but not anymore at this site. We've had firewall issues before
which have gone unresolved. We've ended up leaving the external router to
handle the firewall and switched off the windows one.
Any one else had this issue? Which connection protocols should we use? We've
always left it at the defaults of TCP/IP and named pipes although if both
are available, how do you tell the application which one to use?
Thanks
Simon
 

If the copy of MSDE is a named instance you need to make sure that you use a
static TCP/IP port and open that up or you need to ipen up 1434 for UDP.
By default the default instance of SQL Server uses 1433 but all others use
dynamic assignment.
-Euan
"Simon Bowyer" <nospam@nospam>writes

I ran into this specific problem and found that the user had selected
"Block" when she ran the application using the MSDE database :( It took a
week to figure it out and the solution was to go into the firewall software
program and remove my application from the "blocked" list.
Hope this helps.
Scott Gast
"Simon Bowyer" <nospam@nospam>writes

Was that with Windows Firewall or another product? I have seen what you are
saying in something like Zone Alarm where a user had denied IE but I haven't
seen this in Windows Firewall or where you'd go to allow the application
again.
Thanks
Simon
"Scott Gast" <XXXX@XXXXX.COM>writes

Hi Euan
Thanks for your response. How do you specify a static TCP/IP port? Looking
in the svrnetcn.exe tool and the properties of the TCP/IP protocol specifies
a port number which I understood wasn't always 1433. This is the port number
I've added to the list of exceptions in Windows Firewall. We don't specify a
port to use during installation and I think it is always different?
Simon
"Euan Garden" <XXXX@XXXXX.COM>writes

I'll dig around to see what I can find on Windows Firewall. One way for you
to check and see if it is being blocked would be to rename your .exe and run
it. This should be enough to "trick" the firewall (if, infact, the firewall
is blocking that application).
"Simon Bowyer" <nospam@nospam>writes

Try these;
support.microsoft.com/default.aspx
support.microsoft.com/kb/823938/
-Euan
"Simon Bowyer" <nospam@nospam>writes