firewalls? port numbers? ancient curses cast upon my servers?

Hello All,
Hopefully someone has come across this...

I have the client side of my application installed in the US,
with the application and the database servers running in london.

The program language is C#, all built in .net, with the .net installer.
When the user in the US runs the program and it gets to the
import progress part (background processing occurring on London servers),
they are getting no feedback as to the progress of the import.
ie, nothing is being sent to the US from the london server.
But everything runs smooth the other way, ie, tables are written to
the sql db's in london etc... And I get data sending and receiving
here in london when i run the client app on my machine and send to
the servers here, so its some problem with the connection with the US....
firewalls? port numbers? ancient curses cast upon my servers?

Cheers mike

Is this using SQL Server Integration Services (the SQL Server 2005 replacement for DTS)?
(In any case, if the "import" part isn't giving feedback, you probably should investigate the "import" part, to see what it does, and revise it to give feedback -- it may be hard for anyone here to know what this "import" part is -- if you suspect a connection problem, network sniffing, or even simple use of sysinternals tcpview may be helpful.)

firewalls? port numbers? ancient curses cast upon my servers?

Hello All
I have the client side of my application installed in the US, with the
application and the database servers running in london.
The program language is C#, all built in .net, with the .net installer. When
the user in the US runs the program and it gets to the import progress part
(background processing occurring on London servers), they are getting no
feedback as to the progress of the import. ie, nothing is being sent to the
US from the london server. But everything runs smooth the other way, ie,
tables are written to the sql db's in london etc... And I get data sending
and receiving here in london when i run the client app on my machine and send
to the servers here, so its some problem with the connection with the US...
firewalls' port numbers' ancient curses cast upon my servers' anyone come
across anything like this?
Cheers mikeHave you tested access with Query Analyzer to see if you can connect, access
the database from both places and perform the import tasks? It's unclear
from your post whether you're just having problems with the import task or
if it's even connecting.
joe.
"blomm via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:54B0800E732D8@.SQLMonster.com...
> Hello All
> I have the client side of my application installed in the US, with the
> application and the database servers running in london.
> The program language is C#, all built in .net, with the .net installer.
> When
> the user in the US runs the program and it gets to the import progress
> part
> (background processing occurring on London servers), they are getting no
> feedback as to the progress of the import. ie, nothing is being sent to
> the
> US from the london server. But everything runs smooth the other way, ie,
> tables are written to the sql db's in london etc... And I get data
> sending
> and receiving here in london when i run the client app on my machine and
> send
> to the servers here, so its some problem with the connection with the
> US...
> firewalls' port numbers' ancient curses cast upon my servers' anyone
> come
> across anything like this?
> Cheers mike|||"It's unclear
from your post whether you're just having problems with the import task or
if it's even connecting."
Sorry, i will try and clarify:
it is connecting, theres problems with the callback functionality i think, if
that means anything to you.
okay, thanks for your pointers, i'm off to follow them up.
m

Firewall Problem

I have opened port 1433 on my firewall, but I am still not able to get
remote clients to connect via query analyser, or enterprise manager.
Are there other ports required to be opened ?Have you checked your remote clients to make sure TCP/IP sockets is the
default protocol? You may have to go SQL Client Network Utility or run
through a SQL Server ODBC System DSN (Control Panel | ODBC Data Sources) and
verify that on the user login credential page that the Client Configuration
that it says TCP/IP sockets.
I did look in SQL Server books online in the Network Libraries topic, and
read this
SQL Server uses UDP port 1434 to establish connections from SQL Server 2000
clients. This socket number is also reserved for SQL Server by Internet
Assigned Number Authority (IANA).
You can download SQL Server books online for free from MS
http://www.microsoft.com/sql/techin.../2000/books.asp
****************************************
***************************
Andy S.
MCSE NT/2000, MCDBA SQL 7/2000
andymcdba1@.NOMORESPAM.yahoo.com
Please remove NOMORESPAM before replying.
Always keep your antivirus and Microsoft software
up to date with the latest definitions and product updates.
Be suspicious of every email attachment, I will never send
or post anything other than the text of a http:// link nor
post the link directly to a file for downloading.
This posting is provided "as is" with no warranties
and confers no rights.
****************************************
***************************
"AussieRules" <someone@.nowhere.com> wrote in message
news:upbiLWY6DHA.3288@.TK2MSFTNGP11.phx.gbl...

quote:

---

> I have opened port 1433 on my firewall, but I am still not able to get
> remote clients to connect via query analyser, or enterprise manager.
> Are there other ports required to be opened ?
>
>

---

firewall ports open for tcp/ip connection on server

I would like to know what ports need to be open to access MS SQL via
TCP/IP, using W2k3 and SQL2005.
The default port is 1433. Any UDP openings. I want to use SqlManager on a
remote machine also.
Thanks
Harry
Hi Harry
http://support.microsoft.com/kb/287932 describes how to configure the
firewall.
John
"Harry" wrote:

> I would like to know what ports need to be open to access MS SQL via
> TCP/IP, using W2k3 and SQL2005.
> The default port is 1433. Any UDP openings. I want to use SqlManager on a
> remote machine also.
> Thanks
> Harry
>
>

firewall ports open for tcp/ip connection on server

I would like to know what ports need to be open to access MS SQL via
TCP/IP, using W2k3 and SQL2005.
The default port is 1433. Any UDP openings. I want to use SqlManager on a
remote machine also.
Thanks
HarryHi Harry
http://support.microsoft.com/kb/287932 describes how to configure the
firewall.
John
"Harry" wrote:

> I would like to know what ports need to be open to access MS SQL via
> TCP/IP, using W2k3 and SQL2005.
> The default port is 1433. Any UDP openings. I want to use SqlManager on a
> remote machine also.
> Thanks
> Harry
>
>

firewall ports open for tcp/ip connection on server

I would like to know what ports need to be open to access MS SQL via
TCP/IP, using W2k3 and SQL2005.
The default port is 1433. Any UDP openings. I want to use SqlManager on a
remote machine also.
Thanks
HarryHi Harry
http://support.microsoft.com/kb/287932 describes how to configure the
firewall.
John
"Harry" wrote:
> I would like to know what ports need to be open to access MS SQL via
> TCP/IP, using W2k3 and SQL2005.
> The default port is 1433. Any UDP openings. I want to use SqlManager on a
> remote machine also.
> Thanks
> Harry
>
>

Firewall Ports

What ports need to be opened between the report server and the SQL Server backend DB? Does port 135 need to be opened?Port 135 is the DCOM port. I don't think it needs to be opened, although I am not 100% sure. Are you seeing problems?

Firewall Port 1443

I installed SQL Server 2000 Enterprise Trial. I am trying to connect to my Remote database. In Enterprise Manager it won't resolve listing the server and it's tables. I can register and get a connection though. My host said that if I am behind the firewal
l, that it blocks Port 1433. I tried switching the Port to 8080 and 1222. Still no luck. I am stuck. Any ideas?
Stickfigure
Because everyone likes Figures.
can you connect using query analyser? Or osql?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
|||If it is a firewall issue, and if port 1433 is blocked then the chances are
that ports 8080 and 1222 are blocked also. You might need to take this up
with your firewall administrator.
"Stickfigure" <Stickfigure@.discussions.microsoft.com> wrote in message
news:792F6F89-F318-4E47-99FA-189E9D082BDD@.microsoft.com...
>I installed SQL Server 2000 Enterprise Trial. I am trying to connect to my
>Remote database. In Enterprise Manager it won't resolve listing the server
>and it's tables. I can register and get a connection though. My host said
>that if I am behind the firewall, that it blocks Port 1433. I tried
>switching the Port to 8080 and 1222. Still no luck. I am stuck. Any ideas?
> Stickfigure
> Because everyone likes Figures.

Firewall Port 1443

I installed SQL Server 2000 Enterprise Trial. I am trying to connect to my Remote database. In Enterprise Manager it won't resolve listing the server and it's tables. I can register and get a connection though. My host said that if I am behind the firewal
l, that it blocks Port 1433. I tried switching the Port to 8080 and 1222. Still no luck. I am stuck. Any ideas?
Stickfigure
Can you connect through query analyser to another machine?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.

Firewall Port 1443

I installed SQL Server 2000 Enterprise Trial. I am trying to connect to my R
emote database. In Enterprise Manager it won't resolve listing the server an
d it's tables. I can register and get a connection though. My host said that
if I am behind the firewal
l, that it blocks Port 1433. I tried switching the Port to 8080 and 1222. St
ill no luck. I am stuck. Any ideas?
StickfigureCan you connect through query analyser to another machine?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.

Firewall Port 1443

I installed SQL Server 2000 Enterprise Trial. I am trying to connect to my R
emote database. In Enterprise Manager it won't resolve listing the server an
d it's tables. I can register and get a connection though. My host said that
if I am behind the firewal
l, that it blocks Port 1433. I tried switching the Port to 8080 and 1222. St
ill no luck. I am stuck. Any ideas?
Stickfigure
Because everyone likes Figures.can you connect using query analyser? Or osql?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.|||If it is a firewall issue, and if port 1433 is blocked then the chances are
that ports 8080 and 1222 are blocked also. You might need to take this up
with your firewall administrator.
"Stickfigure" <Stickfigure@.discussions.microsoft.com> wrote in message
news:792F6F89-F318-4E47-99FA-189E9D082BDD@.microsoft.com...
>I installed SQL Server 2000 Enterprise Trial. I am trying to connect to my
>Remote database. In Enterprise Manager it won't resolve listing the server
>and it's tables. I can register and get a connection though. My host said
>that if I am behind the firewall, that it blocks Port 1433. I tried
>switching the Port to 8080 and 1222. Still no luck. I am stuck. Any ideas?
> Stickfigure
> Because everyone likes Figures.

Firewall and port 1433

I read in a forum that port 1433 should never be opened to the internet. Is
this true?
We are developing Windows applications that will need access to our SQL
server from outside our firewall. Is it better to connect via a VPN first an
d
then run the Windows application?
Does anyone know how to open port 1433 on Netscreen 5gt? If it's ok to open
port 1433 to the internet.
We are using Netscreen 5GT as out main firewall and then we have Windows
fireall turned on."Curtis" <Curtis@.discussions.microsoft.com> wrote in message
news:44113285-9232-4CB1-96AD-116293A830CA@.microsoft.com...
> I read in a forum that port 1433 should never be opened to the internet.
Is
> this true?
Well, it depends. Do you want any random person knocking on that port and
waiting for the next Slammer type worm to come along and own your system?
If so, leave it open.

> We are developing Windows applications that will need access to our SQL
> server from outside our firewall. Is it better to connect via a VPN first
and
> then run the Windows application?
Yes.

> Does anyone know how to open port 1433 on Netscreen 5gt? If it's ok to
open
> port 1433 to the internet.
> We are using Netscreen 5GT as out main firewall and then we have Windows
> fireall turned on.
Also, if they are connecting from a specific range of IPs, narrow anything
you open to just that range for further protection.|||Hi
Have you considered creating a web based application? A half way house may
be to use a web service instead of direct database access.
John
"Curtis" wrote:

> I read in a forum that port 1433 should never be opened to the internet. I
s
> this true?
> We are developing Windows applications that will need access to our SQL
> server from outside our firewall. Is it better to connect via a VPN first
and
> then run the Windows application?
> Does anyone know how to open port 1433 on Netscreen 5gt? If it's ok to ope
n
> port 1433 to the internet.
> We are using Netscreen 5GT as out main firewall and then we have Windows
> fireall turned on.|||Thank you both for the sound advice.
We have considered web based application. I am not well versed in web
services, so I need to do some research.
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> Have you considered creating a web based application? A half way house may
> be to use a web service instead of direct database access.
> John
> "Curtis" wrote:
>

Firewall and port 1433

I read in a forum that port 1433 should never be opened to the internet. Is
this true?
We are developing Windows applications that will need access to our SQL
server from outside our firewall. Is it better to connect via a VPN first and
then run the Windows application?
Does anyone know how to open port 1433 on Netscreen 5gt? If it's ok to open
port 1433 to the internet.
We are using Netscreen 5GT as out main firewall and then we have Windows
fireall turned on."Curtis" <Curtis@.discussions.microsoft.com> wrote in message
news:44113285-9232-4CB1-96AD-116293A830CA@.microsoft.com...
> I read in a forum that port 1433 should never be opened to the internet.
Is
> this true?
Well, it depends. Do you want any random person knocking on that port and
waiting for the next Slammer type worm to come along and own your system?
If so, leave it open.
> We are developing Windows applications that will need access to our SQL
> server from outside our firewall. Is it better to connect via a VPN first
and
> then run the Windows application?
Yes.
> Does anyone know how to open port 1433 on Netscreen 5gt? If it's ok to
open
> port 1433 to the internet.
> We are using Netscreen 5GT as out main firewall and then we have Windows
> fireall turned on.
Also, if they are connecting from a specific range of IPs, narrow anything
you open to just that range for further protection.|||Hi
Have you considered creating a web based application? A half way house may
be to use a web service instead of direct database access.
John
"Curtis" wrote:
> I read in a forum that port 1433 should never be opened to the internet. Is
> this true?
> We are developing Windows applications that will need access to our SQL
> server from outside our firewall. Is it better to connect via a VPN first and
> then run the Windows application?
> Does anyone know how to open port 1433 on Netscreen 5gt? If it's ok to open
> port 1433 to the internet.
> We are using Netscreen 5GT as out main firewall and then we have Windows
> fireall turned on.|||Thank you both for the sound advice.
We have considered web based application. I am not well versed in web
services, so I need to do some research.
"John Bell" wrote:
> Hi
> Have you considered creating a web based application? A half way house may
> be to use a web service instead of direct database access.
> John
> "Curtis" wrote:
> > I read in a forum that port 1433 should never be opened to the internet. Is
> > this true?
> >
> > We are developing Windows applications that will need access to our SQL
> > server from outside our firewall. Is it better to connect via a VPN first and
> > then run the Windows application?
> >
> > Does anyone know how to open port 1433 on Netscreen 5gt? If it's ok to open
> > port 1433 to the internet.
> >
> > We are using Netscreen 5GT as out main firewall and then we have Windows
> > fireall turned on.