SSMS 2005 on Vista SP1 can't find new named cluster instance

All,

I have two Vista SP1 machines that have SSMS 2005 installed on them. These
two machines (both used by developers) cannot see my new named SQL cluster
instance when trying to connect using SSMS. Every other PC in the office
with SSMS can find the instance. The two trouble machines can ping the
virtual cluster by name. They just can't pull up the instance in SSMS. Both
developers have permissions to connect to the instance. One developer with a
trouble PC says he can run a query against the instance from the same trouble
PC using Visual Studio 2005. I can't figure out what's going on but I need
to fix this. Any suggestions?

One possibility is loose source mapping. See the Multiple Server IP
Addresses section in Troubleshooting: Timeout Expired
http://msdn.microsoft.com/en-us/library/ms190181.aspx
Basically Vista (and Windows Server 2008) throws away UDP responses that
didn't come from the correct IP Address. (It's not a bug, it's a feature.
)
--
Rick Byham (MSFT), SQL Server Books Online
This posting is provided "AS IS" with no warranties, and confers no rights.

"Ant-nee" wrote in message
news11F54C1-90FF-4077-BFC7-CE69BE526F52-at-microsoft.com...
> All,
>
> I have two Vista SP1 machines that have SSMS 2005 installed on them.
> These
> two machines (both used by developers) cannot see my new named SQL cluster
> instance when trying to connect using SSMS. Every other PC in the office
> with SSMS can find the instance. The two trouble machines can ping the
> virtual cluster by name. They just can't pull up the instance in SSMS.
> Both
> developers have permissions to connect to the instance. One developer
> with a
> trouble PC says he can run a query against the instance from the same
> trouble
> PC using Visual Studio 2005. I can't figure out what's going on but I
> need
> to fix this. Any suggestions?

That is gonna get interesting since clusters respond from the physical IP
even when you connect to a virtual IP address. That "feature' has been
driving firewall guys nuts for years.

--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP




"Rick Byham, (MSFT)" wrote in message
news:9BB7421C-C078-4210-A457-451974720C99-at-microsoft.com...
> One possibility is loose source mapping. See the Multiple Server IP
> Addresses section in Troubleshooting: Timeout Expired
> http://msdn.microsoft.com/en-us/library/ms190181.aspx
> Basically Vista (and Windows Server 2008) throws away UDP responses that
> didn't come from the correct IP Address. (It's not a bug, it's a feature.
> )
> --
> Rick Byham (MSFT), SQL Server Books Online
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "Ant-nee" wrote in message
> news11F54C1-90FF-4077-BFC7-CE69BE526F52-at-microsoft.com...
>> All,
>>
>> I have two Vista SP1 machines that have SSMS 2005 installed on them.
>> These
>> two machines (both used by developers) cannot see my new named SQL
>> cluster
>> instance when trying to connect using SSMS. Every other PC in the office
>> with SSMS can find the instance. The two trouble machines can ping the
>> virtual cluster by name. They just can't pull up the instance in SSMS.
>> Both
>> developers have permissions to connect to the instance. One developer
>> with a
>> trouble PC says he can run a query against the instance from the same
>> trouble
>> PC using Visual Studio 2005. I can't figure out what's going on but I
>> need
>> to fix this. Any suggestions?
>

Thanks guys. I had the developers try to connect using the instance name and
port. No dice. I'm going to have them disable Windows Firewall and then
restart their PCs. It's localized to these two PCs only so it has to be
something with the PCs.

"Geoff N. Hiten" wrote:

> That is gonna get interesting since clusters respond from the physical IP
> even when you connect to a virtual IP address. That "feature' has been
> driving firewall guys nuts for years.
>
> --
> Geoff N. Hiten
> Principal SQL Infrastructure Consultant
> Microsoft SQL Server MVP
>
>
>
>
> "Rick Byham, (MSFT)" wrote in message
> news:9BB7421C-C078-4210-A457-451974720C99-at-microsoft.com...
> > One possibility is loose source mapping. See the Multiple Server IP
> > Addresses section in Troubleshooting: Timeout Expired
> > http://msdn.microsoft.com/en-us/library/ms190181.aspx
> > Basically Vista (and Windows Server 2008) throws away UDP responses that
> > didn't come from the correct IP Address. (It's not a bug, it's a feature.
> > )
> > --
> > Rick Byham (MSFT), SQL Server Books Online
> > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> >
> > "Ant-nee" wrote in message
> > news11F54C1-90FF-4077-BFC7-CE69BE526F52-at-microsoft.com...
> >> All,
> >>
> >> I have two Vista SP1 machines that have SSMS 2005 installed on them.
> >> These
> >> two machines (both used by developers) cannot see my new named SQL
> >> cluster
> >> instance when trying to connect using SSMS. Every other PC in the office
> >> with SSMS can find the instance. The two trouble machines can ping the
> >> virtual cluster by name. They just can't pull up the instance in SSMS.
> >> Both
> >> developers have permissions to connect to the instance. One developer
> >> with a
> >> trouble PC says he can run a query against the instance from the same
> >> trouble
> >> PC using Visual Studio 2005. I can't figure out what's going on but I
> >> need
> >> to fix this. Any suggestions?
> >
>
>

If it's the loose source mapping issue, it only happens from clients that
are Vista or Windows Server 2008. If it is the loose source mapping issue,
you should be able to bypass the SQL Server Browser Service (and UDP) by
connecting straight to the IP and port, as in 157.22.155.231,1433
The port number (1433 in the above string) is listed in the SQL Server error
log.
--
Rick Byham (MSFT), SQL Server Books Online
This posting is provided "AS IS" with no warranties, and confers no rights.

"Ant-nee" wrote in message
news:01F67EB0-860C-443B-9539-F9A539802F99-at-microsoft.com...
> Thanks guys. I had the developers try to connect using the instance name
> and
> port. No dice. I'm going to have them disable Windows Firewall and then
> restart their PCs. It's localized to these two PCs only so it has to be
> something with the PCs.
>
> "Geoff N. Hiten" wrote:
>
>> That is gonna get interesting since clusters respond from the physical IP
>> even when you connect to a virtual IP address. That "feature' has been
>> driving firewall guys nuts for years.
>>
>> --
>> Geoff N. Hiten
>> Principal SQL Infrastructure Consultant
>> Microsoft SQL Server MVP
>>
>>
>>
>>
>> "Rick Byham, (MSFT)" wrote in
>> message
>> news:9BB7421C-C078-4210-A457-451974720C99-at-microsoft.com...
>> > One possibility is loose source mapping. See the Multiple Server IP
>> > Addresses section in Troubleshooting: Timeout Expired
>> > http://msdn.microsoft.com/en-us/library/ms190181.aspx
>> > Basically Vista (and Windows Server 2008) throws away UDP responses
>> > that
>> > didn't come from the correct IP Address. (It's not a bug, it's a
>> > feature.
>> > )
>> > --
>> > Rick Byham (MSFT), SQL Server Books Online
>> > This posting is provided "AS IS" with no warranties, and confers no
>> > rights.
>> >
>> > "Ant-nee" wrote in message
>> > news11F54C1-90FF-4077-BFC7-CE69BE526F52-at-microsoft.com...
>> >> All,
>> >>
>> >> I have two Vista SP1 machines that have SSMS 2005 installed on them.
>> >> These
>> >> two machines (both used by developers) cannot see my new named SQL
>> >> cluster
>> >> instance when trying to connect using SSMS. Every other PC in the
>> >> office
>> >> with SSMS can find the instance. The two trouble machines can ping
>> >> the
>> >> virtual cluster by name. They just can't pull up the instance in
>> >> SSMS.
>> >> Both
>> >> developers have permissions to connect to the instance. One developer
>> >> with a
>> >> trouble PC says he can run a query against the instance from the same
>> >> trouble
>> >> PC using Visual Studio 2005. I can't figure out what's going on but I
>> >> need
>> >> to fix this. Any suggestions?
>> >
>>
>>

It might be a network VLAN issue. Since SQL replies on the physical port,
the VLAN filters may think it is not the original stream and block it.


--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP




"Ant-nee" wrote in message
news:01F67EB0-860C-443B-9539-F9A539802F99-at-microsoft.com...
> Thanks guys. I had the developers try to connect using the instance name
> and
> port. No dice. I'm going to have them disable Windows Firewall and then
> restart their PCs. It's localized to these two PCs only so it has to be
> something with the PCs.
>
> "Geoff N. Hiten" wrote:
>
>> That is gonna get interesting since clusters respond from the physical IP
>> even when you connect to a virtual IP address. That "feature' has been
>> driving firewall guys nuts for years.
>>
>> --
>> Geoff N. Hiten
>> Principal SQL Infrastructure Consultant
>> Microsoft SQL Server MVP
>>
>>
>>
>>
>> "Rick Byham, (MSFT)" wrote in
>> message
>> news:9BB7421C-C078-4210-A457-451974720C99-at-microsoft.com...
>> > One possibility is loose source mapping. See the Multiple Server IP
>> > Addresses section in Troubleshooting: Timeout Expired
>> > http://msdn.microsoft.com/en-us/library/ms190181.aspx
>> > Basically Vista (and Windows Server 2008) throws away UDP responses
>> > that
>> > didn't come from the correct IP Address. (It's not a bug, it's a
>> > feature.
>> > )
>> > --
>> > Rick Byham (MSFT), SQL Server Books Online
>> > This posting is provided "AS IS" with no warranties, and confers no
>> > rights.
>> >
>> > "Ant-nee" wrote in message
>> > news11F54C1-90FF-4077-BFC7-CE69BE526F52-at-microsoft.com...
>> >> All,
>> >>
>> >> I have two Vista SP1 machines that have SSMS 2005 installed on them.
>> >> These
>> >> two machines (both used by developers) cannot see my new named SQL
>> >> cluster
>> >> instance when trying to connect using SSMS. Every other PC in the
>> >> office
>> >> with SSMS can find the instance. The two trouble machines can ping
>> >> the
>> >> virtual cluster by name. They just can't pull up the instance in
>> >> SSMS.
>> >> Both
>> >> developers have permissions to connect to the instance. One developer
>> >> with a
>> >> trouble PC says he can run a query against the instance from the same
>> >> trouble
>> >> PC using Visual Studio 2005. I can't figure out what's going on but I
>> >> need
>> >> to fix this. Any suggestions?
>> >
>>
>>

Going in with server IP comma port worked.


"Rick Byham, (MSFT)" wrote:

> If it's the loose source mapping issue, it only happens from clients that
> are Vista or Windows Server 2008. If it is the loose source mapping issue,
> you should be able to bypass the SQL Server Browser Service (and UDP) by
> connecting straight to the IP and port, as in 157.22.155.231,1433
> The port number (1433 in the above string) is listed in the SQL Server error
> log.
> --
> Rick Byham (MSFT), SQL Server Books Online
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Ant-nee" wrote in message
> news:01F67EB0-860C-443B-9539-F9A539802F99-at-microsoft.com...
> > Thanks guys. I had the developers try to connect using the instance name
> > and
> > port. No dice. I'm going to have them disable Windows Firewall and then
> > restart their PCs. It's localized to these two PCs only so it has to be
> > something with the PCs.
> >
> > "Geoff N. Hiten" wrote:
> >
> >> That is gonna get interesting since clusters respond from the physical IP
> >> even when you connect to a virtual IP address. That "feature' has been
> >> driving firewall guys nuts for years.
> >>
> >> --
> >> Geoff N. Hiten
> >> Principal SQL Infrastructure Consultant
> >> Microsoft SQL Server MVP
> >>
> >>
> >>
> >>
> >> "Rick Byham, (MSFT)" wrote in
> >> message
> >> news:9BB7421C-C078-4210-A457-451974720C99-at-microsoft.com...
> >> > One possibility is loose source mapping. See the Multiple Server IP
> >> > Addresses section in Troubleshooting: Timeout Expired
> >> > http://msdn.microsoft.com/en-us/library/ms190181.aspx
> >> > Basically Vista (and Windows Server 2008) throws away UDP responses
> >> > that
> >> > didn't come from the correct IP Address. (It's not a bug, it's a
> >> > feature.
> >> > )
> >> > --
> >> > Rick Byham (MSFT), SQL Server Books Online
> >> > This posting is provided "AS IS" with no warranties, and confers no
> >> > rights.
> >> >
> >> > "Ant-nee" wrote in message
> >> > news11F54C1-90FF-4077-BFC7-CE69BE526F52-at-microsoft.com...
> >> >> All,
> >> >>
> >> >> I have two Vista SP1 machines that have SSMS 2005 installed on them.
> >> >> These
> >> >> two machines (both used by developers) cannot see my new named SQL
> >> >> cluster
> >> >> instance when trying to connect using SSMS. Every other PC in the
> >> >> office
> >> >> with SSMS can find the instance. The two trouble machines can ping
> >> >> the
> >> >> virtual cluster by name. They just can't pull up the instance in
> >> >> SSMS.
> >> >> Both
> >> >> developers have permissions to connect to the instance. One developer
> >> >> with a
> >> >> trouble PC says he can run a query against the instance from the same
> >> >> trouble
> >> >> PC using Visual Studio 2005. I can't figure out what's going on but I
> >> >> need
> >> >> to fix this. Any suggestions?
> >> >
> >>
> >>
>