Re: ISA 2004 - MSSQL / Listening VNC Publishing - Denied Connection
From: José Carlos (iwjcs_at_uol.com.br)
Date: 03/26/05
- Next message: Santhosh Sivarajan: "Re: Mac File Services publishing?"
- Previous message: ABH: "Re: ISA 2004 - MSSQL / VNC Publishing - Denied Connection"
- In reply to: ABH: "Re: ISA 2004 - MSSQL / VNC Publishing - Denied Connection"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 26 Mar 2005 13:00:26 -0300
Andy,
Thanks for your response, let's me explain better,
I work in a ASP Company.
I'm preparing the following solution case using our LAN:
- Site-to-remote site (WAN to WAN) VPN Client only to a specific Corba
solution synchronization; This it's ok, it's running!
- Provide firewall to our LAN that uses common application like IE, Outlook,
MSN, etc. This it's ok, it's running!
- Point-to-Point, remote assistance and supports, to our Support Team that
are working in our LAN and use VNC in listening mode;
- Remote database connection (MSSQL) to a site-to-site synchronization using
firewall blocking rules;
I don't need to publish VNC and MSSQL to the VPN. The Server was configured
as VPN client
I need to publish our Internal LAN that uses VNC (listening mode, protocol
TCP port 55xx) and MSSQL (protocol TCP port 1433) to Internet, using our
Public IP address.
This solution case is installed in a Win2003 Server with ISA 2004 Standard
and again, VPN it's running ok!
The same solution, but without VPN, it's running in ISA 2000 without
problems.
My problem is concerned in VNC and MSSQL publishing.
I've already tried the simple and very usefull instructions but without
success in:
"Publishing a SQL Server Computer with ISA Server 2004",
http://www.microsoft.com/technet/prodtechnol/isa/2004/deploy/publishingsql.m
spx#EAAA
similar tutorial:
"Publishing FTP Sites with an Alternate Port using ISA Server 2004
Firewalls", http://www.isaserver.org/tutorials/2004pubftpaltport.html
When I try to connect to MSSQL through the remote IP, I receive the
following logging message:
Destination IP:
200.x.y.z - it's correct IP Address from our server
Destination Port:
1433
Protocol:
Microsoft SQL (TCP)
Action:
Denied Connection
Rule:
Default rule
Client IP:
200.a.b.c - it's correct remote IP Address
Source Network:
External - I think it's ok
Destination Network:
Local Host - I think this it's wrong; I suppose this must be
"Internal"
The same logging message occurs with the VNC, but with a curiosity, the
Protocol appears like "Unidentified IP Traffic", but it's registered as
"VNC5xxx".
I've tried to re-register another MSSQL Server Protocol with other name than
default "Microsoft SQL (TCP)" and the new name appears right in the logging,
so I thing that's nothing wrong with the "VNC5xxx" registry.
Excuse-me by the extensivity and the multi-posts.
Any idea?
Thanks in Advance,
José Carlos.
"ABH" <andyspamfee@hotmail.com> escreveu na mensagem
news:#AePj3fMFHA.2252@TK2MSFTNGP15.phx.gbl...
> "José Carlos" <iwjcs@uol.com.br> wrote in message
> news:uxzlSyOMFHA.3760@TK2MSFTNGP12.phx.gbl...
> > Dear all,
> > I've setup the remote VPN client successfull.
> >
>
> If you've set up VPN client connectivity and want to use VNC on internal
> machines, the logical way would be to connect over VPN and then use the
> internal IP to connect using VNC.
>
> Surely you don't actually want to publish VNC on a public IP adddress ?
>
>
> --
> Andy
>
>
- Next message: Santhosh Sivarajan: "Re: Mac File Services publishing?"
- Previous message: ABH: "Re: ISA 2004 - MSSQL / VNC Publishing - Denied Connection"
- In reply to: ABH: "Re: ISA 2004 - MSSQL / VNC Publishing - Denied Connection"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
