Non standard port - non default instance

Hi all,
I'm trying to create a subscription for a merge replication on a sql
server mobile 2005 based application.
The publisher is on a intranet, listening on port 9091 and with a named
instance.
The merge agent is in a DMZ with port 9091 open for inbound/outbound TCP
traffic to the intranet.
Problem:
when I try to synchronize I receive the "SQL Server does not exists" error.
My subscription has the following setup:
Publisher = "ServerName\InstanceName";
PublisherNetwork = NetworkType.TcpIpSockets;
PublisherAddress = "10.xxx.xxx.xxx,9091";
PublisherDatabase = "DatabaseName";
PublisherSecurityMode = SecurityType.DBAuthentication;
PublisherLogin = "name";
PublisherPassword = "pwd";
name/pwd user has correct priviledges non publisher database.
I can connect via SQL Client to the database from the machine in DMZ.
In my (many) tries, I also created an alias on the DMZ client and used
that for the Publisher property at the subscriber.
Nothing worked.
I'm finishing options...
Cl@. ha scritto:

> Problem:
> when I try to synchronize I receive the "SQL Server does not exists" error.
I solved opening 1434 udp port.
Question is: why sql client can connect without 1434 port open and the
merge agent can't?

Non domain user receive access denied error

I am trying to run a VBScript that uses a SQL user to access a 2000 SQL SP4
clustered instance.
The script runs successfully only when I am logged on with a domain account.
What can the reason for this be?
Thanks in advance,
Ido Friedman
My first thought is that the VBScript is using NT authentication instead of
SQL Authentication.
Can you post the script?
Keith Kratochvil
"Ido friedman" <Idofriedman@.discussions.microsoft.com> wrote in message
news:A1B97509-42C7-4EBB-9BA3-786FA81E682F@.microsoft.com...
>I am trying to run a VBScript that uses a SQL user to access a 2000 SQL SP4
> clustered instance.
> The script runs successfully only when I am logged on with a domain
> account.
> What can the reason for this be?
>
> Thanks in advance,
> Ido Friedman

Node Eviction

HI,
I need to evict one node from a two node, two instance SQL Cluster.
Beyond failing over all resources and ownership to the surviving cluster
node, is there any other configuration change I need to make in SQL server
before doing this? Thanks.
John
Nope. Can I ask why you need to evict the node?
Cheers,
Rodney R. Fournier
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://www.msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner
"JT" <Jthayer@.online.nospam> wrote in message
news:D40762AF-1D29-4E5A-AA66-EE7834434122@.microsoft.com...
> HI,
> I need to evict one node from a two node, two instance SQL Cluster.
> Beyond failing over all resources and ownership to the surviving cluster
> node, is there any other configuration change I need to make in SQL server
> before doing this? Thanks.
> --
> John
|||Thanks Rodney. To answer that question, look at my thread in Windows Server
Clustering regarding adding 64 bit nodes to 32 bit node cluster where you
were joking about making us look at MVP pictures. On a related note, there
is a KB out there about difficulties adding cluster nodes to Win2003 when
using NTLMv2 only, which is what I do. The article KB is 890761. It applies
to 32 bit and IA64 Windows 2003. Do you know if it applies to x64 Windows
2003? Thanks.
John
"JT" wrote:

> HI,
> I need to evict one node from a two node, two instance SQL Cluster.
> Beyond failing over all resources and ownership to the surviving cluster
> node, is there any other configuration change I need to make in SQL server
> before doing this? Thanks.
> --
> John
|||Yes, there is an essential step. You need to run the SQL install app and
remove SQL from the node before evicting the node. If you don't do this,
SQL will still have node configuration information and won't let you
reinstall later. You can do the removal after the node is evicted and
removed, but it will throw errors since it cannot update information on the
now-missing node. BOL has information under "maintaining a failover
cluster".
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"JT" <Jthayer@.online.nospam> wrote in message
news:D40762AF-1D29-4E5A-AA66-EE7834434122@.microsoft.com...
> HI,
> I need to evict one node from a two node, two instance SQL Cluster.
> Beyond failing over all resources and ownership to the surviving cluster
> node, is there any other configuration change I need to make in SQL server
> before doing this? Thanks.
> --
> John
|||Crap! I always forget that step! You rule Geoff!
Cheers,
Rodney R. Fournier
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://www.msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:O9kdHGRSGHA.5108@.TK2MSFTNGP11.phx.gbl...
> Yes, there is an essential step. You need to run the SQL install app and
> remove SQL from the node before evicting the node. If you don't do this,
> SQL will still have node configuration information and won't let you
> reinstall later. You can do the removal after the node is evicted and
> removed, but it will throw errors since it cannot update information on
> the now-missing node. BOL has information under "maintaining a failover
> cluster".
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "JT" <Jthayer@.online.nospam> wrote in message
> news:D40762AF-1D29-4E5A-AA66-EE7834434122@.microsoft.com...
>
|||I honestly don't know, you can always PSS and ask though.
Cheers,
Rodney R. Fournier
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://www.msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner
"JT" <Jthayer@.online.nospam> wrote in message
news:630A1BF0-199E-4743-BB15-E99EA54E3687@.microsoft.com...[vbcol=seagreen]
> Thanks Rodney. To answer that question, look at my thread in Windows
> Server
> Clustering regarding adding 64 bit nodes to 32 bit node cluster where you
> were joking about making us look at MVP pictures. On a related note,
> there
> is a KB out there about difficulties adding cluster nodes to Win2003 when
> using NTLMv2 only, which is what I do. The article KB is 890761. It
> applies
> to 32 bit and IA64 Windows 2003. Do you know if it applies to x64 Windows
> 2003? Thanks.
> --
> John
>
> "JT" wrote: