Cluster not visible to external IP

Hello
We have SQL 2000 with two servers clustered (one is a failover) to have one
named SQL server. This is fine internally, but external VPN connections
can't reach this server (all other machines are reachable). Permissions not
an issue.
Anyone have any ideas on where to start/look?
ThanksVPN connections will have to be enabled to the underlying node IPs, not the
virtual server IPs.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"PB" <hoopitup@.gmail.com> wrote in message
news:OdM$Zy47FHA.1148@.tk2msftngp13.phx.gbl...
> Hello
> We have SQL 2000 with two servers clustered (one is a failover) to have
> one named SQL server. This is fine internally, but external VPN
> connections can't reach this server (all other machines are reachable).
> Permissions not an issue.
> Anyone have any ideas on where to start/look?
> Thanks
>|||We are using the cluster name rather than IP. Will try the actual node name
now, but the only thing then is there is no failover protection.
"Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
news:OkktM047FHA.3224@.TK2MSFTNGP09.phx.gbl...
> VPN connections will have to be enabled to the underlying node IPs, not
> the virtual server IPs.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "PB" <hoopitup@.gmail.com> wrote in message
> news:OdM$Zy47FHA.1148@.tk2msftngp13.phx.gbl...
>|||When a client (in this case the firewall) receives an IP packet from a
virtual instance, the sender IP address is the node's physical address, not
the virtual address. You can still connect via virtual IP for name and ARP
resolution, but you will have to enable VPN access via the physical node
addresses.
GNH
"PB" <hoopitup@.gmail.com> wrote in message
news:eUtFO347FHA.1248@.TK2MSFTNGP14.phx.gbl...
> We are using the cluster name rather than IP. Will try the actual node
> name now, but the only thing then is there is no failover protection.
> "Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
> news:OkktM047FHA.3224@.TK2MSFTNGP09.phx.gbl...
>

Cluster not visible to external IP

Hello
We have SQL 2000 with two servers clustered (one is a failover) to have one
named SQL server. This is fine internally, but external VPN connections
can't reach this server (all other machines are reachable). Permissions not
an issue.
Anyone have any ideas on where to start/look?
ThanksVPN connections will have to be enabled to the underlying node IPs, not the
virtual server IPs.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"PB" <hoopitup@.gmail.com> wrote in message
news:OdM$Zy47FHA.1148@.tk2msftngp13.phx.gbl...
> Hello
> We have SQL 2000 with two servers clustered (one is a failover) to have
> one named SQL server. This is fine internally, but external VPN
> connections can't reach this server (all other machines are reachable).
> Permissions not an issue.
> Anyone have any ideas on where to start/look?
> Thanks
>|||We are using the cluster name rather than IP. Will try the actual node name
now, but the only thing then is there is no failover protection.
"Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
news:OkktM047FHA.3224@.TK2MSFTNGP09.phx.gbl...
> VPN connections will have to be enabled to the underlying node IPs, not
> the virtual server IPs.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "PB" <hoopitup@.gmail.com> wrote in message
> news:OdM$Zy47FHA.1148@.tk2msftngp13.phx.gbl...
>> Hello
>> We have SQL 2000 with two servers clustered (one is a failover) to have
>> one named SQL server. This is fine internally, but external VPN
>> connections can't reach this server (all other machines are reachable).
>> Permissions not an issue.
>> Anyone have any ideas on where to start/look?
>> Thanks
>|||When a client (in this case the firewall) receives an IP packet from a
virtual instance, the sender IP address is the node's physical address, not
the virtual address. You can still connect via virtual IP for name and ARP
resolution, but you will have to enable VPN access via the physical node
addresses.
GNH
"PB" <hoopitup@.gmail.com> wrote in message
news:eUtFO347FHA.1248@.TK2MSFTNGP14.phx.gbl...
> We are using the cluster name rather than IP. Will try the actual node
> name now, but the only thing then is there is no failover protection.
> "Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
> news:OkktM047FHA.3224@.TK2MSFTNGP09.phx.gbl...
>> VPN connections will have to be enabled to the underlying node IPs, not
>> the virtual server IPs.
>> --
>> Geoff N. Hiten
>> Senior Database Administrator
>> Microsoft SQL Server MVP
>>
>> "PB" <hoopitup@.gmail.com> wrote in message
>> news:OdM$Zy47FHA.1148@.tk2msftngp13.phx.gbl...
>> Hello
>> We have SQL 2000 with two servers clustered (one is a failover) to have
>> one named SQL server. This is fine internally, but external VPN
>> connections can't reach this server (all other machines are reachable).
>> Permissions not an issue.
>> Anyone have any ideas on where to start/look?
>> Thanks
>>
>sqlsql

Cluster not visible to external IP

Hello
We have SQL 2000 with two servers clustered (one is a failover) to have one
named SQL server. This is fine internally, but external VPN connections
can't reach this server (all other machines are reachable). Permissions not
an issue.
Anyone have any ideas on where to start/look?
Thanks
VPN connections will have to be enabled to the underlying node IPs, not the
virtual server IPs.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"PB" <hoopitup@.gmail.com> wrote in message
news:OdM$Zy47FHA.1148@.tk2msftngp13.phx.gbl...
> Hello
> We have SQL 2000 with two servers clustered (one is a failover) to have
> one named SQL server. This is fine internally, but external VPN
> connections can't reach this server (all other machines are reachable).
> Permissions not an issue.
> Anyone have any ideas on where to start/look?
> Thanks
>
|||We are using the cluster name rather than IP. Will try the actual node name
now, but the only thing then is there is no failover protection.
"Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
news:OkktM047FHA.3224@.TK2MSFTNGP09.phx.gbl...
> VPN connections will have to be enabled to the underlying node IPs, not
> the virtual server IPs.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "PB" <hoopitup@.gmail.com> wrote in message
> news:OdM$Zy47FHA.1148@.tk2msftngp13.phx.gbl...
>
|||When a client (in this case the firewall) receives an IP packet from a
virtual instance, the sender IP address is the node's physical address, not
the virtual address. You can still connect via virtual IP for name and ARP
resolution, but you will have to enable VPN access via the physical node
addresses.
GNH
"PB" <hoopitup@.gmail.com> wrote in message
news:eUtFO347FHA.1248@.TK2MSFTNGP14.phx.gbl...
> We are using the cluster name rather than IP. Will try the actual node
> name now, but the only thing then is there is no failover protection.
> "Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
> news:OkktM047FHA.3224@.TK2MSFTNGP09.phx.gbl...
>

CLR Stored Procedure Not Visible

I am trying to do some time series analysis on data that I have. I've read that the best way to do this is to use CLR to write the manipulation code in .Net and then load the assembly into SQL rather than extracting the data, manipulating it and putting it back again.

I'm using crystal reports with visual studio 2003 to do my reporting. The problem I am facing is that the CLR stored procedures I create using SQLExpress are not visible from my SQL explorer built into Visual Studio 2003. I can create stored procedures using standard transact sql and these are visible, but the CLR stored procedures are not.

I've noticed when I browse the stored procedures in my SQL Management Studio that the image of the stored procedure has a padlock shown in the icon, as if they are locked?

Do I have to explicitly enable a security attribute on CLR stored procedures to make them visible?

Any help would be greatly appreciated.

Try posting this question on the CLR forums: .NET Framework inside SQL Server.

Thanks
Laurentiu

|||

Mic,

Did you find an answer to the padlock icon next to the CLR stored procedures.

I am using sql server 2005, and trying to access them in reporting services.

I must be missing something.

I tried setting permissions to no avail.

Thanks

Tim

CLR Stored Procedure Not Visible

I am trying to do some time series analysis on data that I have. I've read that the best way to do this is to use CLR to write the manipulation code in .Net and then load the assembly into SQL rather than extracting the data, manipulating it and putting it back again.

I'm using crystal reports with visual studio 2003 to do my reporting. The problem I am facing is that the CLR stored procedures I create using SQLExpress are not visible from my SQL explorer built into Visual Studio 2003. I can create stored procedures using standard transact sql and these are visible, but the CLR stored procedures are not.

I've noticed when I browse the stored procedures in my SQL Management Studio that the image of the stored procedure has a padlock shown in the icon, as if they are locked?

Do I have to explicitly enable a security attribute on CLR stored procedures to make them visible?

Any help would be greatly appreciated.

Try posting this question on the CLR forums: .NET Framework inside SQL Server.

Thanks
Laurentiu

|||

Mic,

Did you find an answer to the padlock icon next to the CLR stored procedures.

I am using sql server 2005, and trying to access them in reporting services.

I must be missing something.

I tried setting permissions to no avail.

Thanks

Tim

client side print button not visible even in SQL Server 2005 Express SP 2.0

Hi All!

i installed SQL Server 2005 express edition Service Pack 2.0, SQL server Advance Services, and Toolkit . Still Print button in client side report is not visible in web form.

please help me.

thanks in advance.

rkraju:

Hi All!

i installed SQL Server 2005 express edition Service Pack 2.0, SQL server Advance Services, and Toolkit . Still Print button in client side report is not visible in web form.

please help me.

thanks in advance.

Wel I guess we cannot do that...printing is not available on client SSRS...Too bad...And just to let you know, if you need to send query parameters to the report forget the client SSRS again...it sucks...you have to install the report on the Web server and that way yes you can print and send query parameters and so long...other way no solution...

Read here...I'm feeling frustrated on this...

http://blogs.msdn.com/mohamed_sharafs_blog/archive/2005/12/20/LocalReportCustomCode.aspx

However if you've found another solution please let me know!!!Thanks a lot!