Question on synching through RDA using port 1433

Hi,

Does SQL mobile require port 1433 to be open for RDA? I was under the impression that all synching occured through port 80. But when 1433 is restricted a connection cannot be completed.

I may be missing something really simple. My understanding of tcp/ip networking concepts are not very solid.

Thanks,

Tony.

Ok here is how things work in RDA.

Legend:

1) SQL Server Mobile/Everywhere on Client Box/Device - M1

2) IIS Box - M2

3) SQL Server Box - M3

M1, M2, M3 can be anywhere. That is, they can be on different machines or can be on same machine.

Communication Protocol [M1, M2] is HTTP or HTTPS.

Communication Protocol [M2, M3] is SQL OLEDB Connection (means port 1433).

I hope I am not too cryptic and you got what you want out of this! If not, let me know.

Thanks,

Laxmi Narsimha Rao ORUGANTI, SQL Server Everywhere, Microsoft Corporation

|||

M2 and M3 are on the same box on a remote server, and when we restrict port 1433 externally through our firewall it appears to cause the synch to fail.

Any ideas on why this would occur?

Thanks.

|||

If IIS Server and SQL Server are on the same server only the Port 80 needs to be opened up in the Firewall to allow the HTTP/HTTPS messages.

Incase the IIS Server and the SQL Server are on different servers and there is a firewall between Internet and IIS Server, and another firewall between IIS Server and SQL Server then Port 80 needs to be opened up in the Internet Firewall, and Port 80 & 1443 needs to be opened up in the Firewall between IIS Server and SQL Server.

Can you verify if the information given above applies in your network topology

Regards

Ambrish

Question on synching through RDA using port 1433

Hi,

Does SQL mobile require port 1433 to be open for RDA? I was under the impression that all synching occured through port 80. But when 1433 is restricted a connection cannot be completed.

I may be missing something really simple. My understanding of tcp/ip networking concepts are not very solid.

Thanks,

Tony.

Ok here is how things work in RDA.

Legend:

1) SQL Server Mobile/Everywhere on Client Box/Device - M1

2) IIS Box - M2

3) SQL Server Box - M3

M1, M2, M3 can be anywhere. That is, they can be on different machines or can be on same machine.

Communication Protocol [M1, M2] is HTTP or HTTPS.

Communication Protocol [M2, M3] is SQL OLEDB Connection (means port 1433).

I hope I am not too cryptic and you got what you want out of this! If not, let me know.

Thanks,

Laxmi Narsimha Rao ORUGANTI, SQL Server Everywhere, Microsoft Corporation

|||

M2 and M3 are on the same box on a remote server, and when we restrict port 1433 externally through our firewall it appears to cause the synch to fail.

Any ideas on why this would occur?

Thanks.

|||

If IIS Server and SQL Server are on the same server only the Port 80 needs to be opened up in the Firewall to allow the HTTP/HTTPS messages.

Incase the IIS Server and the SQL Server are on different servers and there is a firewall between Internet and IIS Server, and another firewall between IIS Server and SQL Server then Port 80 needs to be opened up in the Internet Firewall, and Port 80 & 1443 needs to be opened up in the Firewall between IIS Server and SQL Server.

Can you verify if the information given above applies in your network topology

Regards

Ambrish

Question on port 1433 on a remote server

Hi,I am using a remote sql server 2005 install. Our application connects directly to the dB from a desktop application and a mobile application.I was just wondering what the best way to secure this connection. Everytime we want to do a demo for a potential client we have to allow a new IP to access port 1433 in order to connect to the database. This is becoming very expensive for us. Does anyone have an idea of how we can both secure the connection to our dB and not have to keep adding new IP's too the approved list on our Firewall?Thanks very much,Tony

How about using a VPN across the firewall you could then work in the intranet.

HTH, jens Suessmeyer.

http://www.sqlserver2005.de