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.
<g>)
--
Rick Byham (MSFT), SQL Server Books Online
This posting is provided "AS IS" with no warranties, and confers no rights.

"Ant-nee" <Antnee (AT) discussions (DOT) microsoft.com> wrote

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.
<g>)
--
Rick Byham (MSFT), SQL Server Books Online
This posting is provided "AS IS" with no warranties, and confers no rights.

"Ant-nee" <Antnee (AT) discussions (DOT) microsoft.com> wrote

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.
<g>)
--
Rick Byham (MSFT), SQL Server Books Online
This posting is provided "AS IS" with no warranties, and confers no rights.

"Ant-nee" <Antnee (AT) discussions (DOT) microsoft.com> wrote

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.
<g>)
--
Rick Byham (MSFT), SQL Server Books Online
This posting is provided "AS IS" with no warranties, and confers no rights.

"Ant-nee" <Antnee (AT) discussions (DOT) microsoft.com> wrote

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.
<g>)
--
Rick Byham (MSFT), SQL Server Books Online
This posting is provided "AS IS" with no warranties, and confers no rights.

"Ant-nee" <Antnee (AT) discussions (DOT) microsoft.com> wrote

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.
<g>)
--
Rick Byham (MSFT), SQL Server Books Online
This posting is provided "AS IS" with no warranties, and confers no rights.

"Ant-nee" <Antnee (AT) discussions (DOT) microsoft.com> wrote

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.
<g>)
--
Rick Byham (MSFT), SQL Server Books Online
This posting is provided "AS IS" with no warranties, and confers no rights.

"Ant-nee" <Antnee (AT) discussions (DOT) microsoft.com> wrote

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.
<g>)
--
Rick Byham (MSFT), SQL Server Books Online
This posting is provided "AS IS" with no warranties, and confers no rights.

"Ant-nee" <Antnee (AT) discussions (DOT) microsoft.com> wrote

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.
<g>)
--
Rick Byham (MSFT), SQL Server Books Online
This posting is provided "AS IS" with no warranties, and confers no rights.

"Ant-nee" <Antnee (AT) discussions (DOT) microsoft.com> wrote