Cannot access a share folder with IP in R2 cluster

Hi,
I have a Windows 2008 R2 cluster. I don't think this a cluster problem
(I could be wrong) but I posted this in the Windows Server General and
did not receive a response.

I have a share that I can connect via the name \\ServerName\ShareName

But I cannot connect via the IP \\123.123.123.123\ShareName

This has always worked in the past with older OS's, and it works with
our Win2k3 and Win2k8 (non R2) servers.

Has something changed in R2?

Thanks in advance.
Jeff

JJP wrote:
> Hi,
> I have a Windows 2008 R2 cluster. I don't think this a cluster problem
> (I could be wrong) but I posted this in the Windows Server General and
> did not receive a response.
>
> I have a share that I can connect via the name \\ServerName\ShareName
>
> But I cannot connect via the IP \\123.123.123.123\ShareName
>
> This has always worked in the past with older OS's, and it works with
> our Win2k3 and Win2k8 (non R2) servers.
>
> Has something changed in R2?
>
> Thanks in advance.
> Jeff


Ok, I could be wrong about the cluster part. We built a test R2
(non-cluster) server today and tested a share and accessing by IP works
fine. So this is also not an R2 thing, unless it is R2 cluster related.

So, I have this resource group that has a network name, an IP address
and a share.

I can access the share this way:
\\sharename\folder1

I cannot access the share this way:
\\shareIP\folder1
(example, \\123.123.123.123\folder1)

I can ping the share name of course and I can do a ping -a on the IP of
the share and it brings the share name back just fine.

I cannot figure out why I cannot use the IP address.
Any ideas of what to check?

Thanks.
Jeff

This is by design. Change has happened in W2K8. Now share is scoped to the
netname, and can be accessed only using this netname.

Vladimir Petter
Clustering and High Availability.
This posting is provided "AS IS" with no warranties, and confers no rights.

"JJP" <> wrote in message
news:ey$...
> JJP wrote:
>> Hi,
>> I have a Windows 2008 R2 cluster. I don't think this a cluster problem
>> (I could be wrong) but I posted this in the Windows Server General and
>> did not receive a response.
>>
>> I have a share that I can connect via the name \\ServerName\ShareName
>>
>> But I cannot connect via the IP \\123.123.123.123\ShareName
>>
>> This has always worked in the past with older OS's, and it works with our
>> Win2k3 and Win2k8 (non R2) servers.
>>
>> Has something changed in R2?
>>
>> Thanks in advance.
>> Jeff
>
>
> Ok, I could be wrong about the cluster part. We built a test R2
> (non-cluster) server today and tested a share and accessing by IP works
> fine. So this is also not an R2 thing, unless it is R2 cluster related.
>
> So, I have this resource group that has a network name, an IP address and
> a share.
>
> I can access the share this way:
> \\sharename\folder1
>
> I cannot access the share this way:
> \\shareIP\folder1
> (example, \\123.123.123.123\folder1)
>
> I can ping the share name of course and I can do a ping -a on the IP of
> the share and it brings the share name back just fine.
>
> I cannot figure out why I cannot use the IP address.
> Any ideas of what to check?
>
> Thanks.
> Jeff

Vladimir Petter wrote:
> This is by design. Change has happened in W2K8. Now share is scoped to
> the netname, and can be accessed only using this netname.
>
> Vladimir Petter
> Clustering and High Availability.
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "JJP" <> wrote in message
> news:ey$...
>> JJP wrote:
>>> Hi,
>>> I have a Windows 2008 R2 cluster. I don't think this a cluster
>>> problem (I could be wrong) but I posted this in the Windows Server
>>> General and did not receive a response.
>>>
>>> I have a share that I can connect via the name \\ServerName\ShareName
>>>
>>> But I cannot connect via the IP \\123.123.123.123\ShareName
>>>
>>> This has always worked in the past with older OS's, and it works with
>>> our Win2k3 and Win2k8 (non R2) servers.
>>>
>>> Has something changed in R2?
>>>
>>> Thanks in advance.
>>> Jeff
>>
>>
>> Ok, I could be wrong about the cluster part. We built a test R2
>> (non-cluster) server today and tested a share and accessing by IP
>> works fine. So this is also not an R2 thing, unless it is R2 cluster
>> related.
>>
>> So, I have this resource group that has a network name, an IP address
>> and a share.
>>
>> I can access the share this way:
>> \\sharename\folder1
>>
>> I cannot access the share this way:
>> \\shareIP\folder1
>> (example, \\123.123.123.123\folder1)
>>
>> I can ping the share name of course and I can do a ping -a on the IP
>> of the share and it brings the share name back just fine.
>>
>> I cannot figure out why I cannot use the IP address.
>> Any ideas of what to check?
>>
>> Thanks.
>> Jeff
>

Thanks Vladimir, this must only apply to cluster then? Because it still
works for Win2k8 R2 and non-R2 non-clustered servers.
Jeff

correct - does only applies to failover clustering.

Regards
Ramazan

"JJP" <> wrote in message
news:...
> Vladimir Petter wrote:
>> This is by design. Change has happened in W2K8. Now share is scoped to
>> the netname, and can be accessed only using this netname.
>>
>> Vladimir Petter
>> Clustering and High Availability.
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "JJP" <> wrote in message
>> news:ey$...
>>> JJP wrote:
>>>> Hi,
>>>> I have a Windows 2008 R2 cluster. I don't think this a cluster problem
>>>> (I could be wrong) but I posted this in the Windows Server General and
>>>> did not receive a response.
>>>>
>>>> I have a share that I can connect via the name \\ServerName\ShareName
>>>>
>>>> But I cannot connect via the IP \\123.123.123.123\ShareName
>>>>
>>>> This has always worked in the past with older OS's, and it works with
>>>> our Win2k3 and Win2k8 (non R2) servers.
>>>>
>>>> Has something changed in R2?
>>>>
>>>> Thanks in advance.
>>>> Jeff
>>>
>>>
>>> Ok, I could be wrong about the cluster part. We built a test R2
>>> (non-cluster) server today and tested a share and accessing by IP works
>>> fine. So this is also not an R2 thing, unless it is R2 cluster related.
>>>
>>> So, I have this resource group that has a network name, an IP address
>>> and a share.
>>>
>>> I can access the share this way:
>>> \\sharename\folder1
>>>
>>> I cannot access the share this way:
>>> \\shareIP\folder1
>>> (example, \\123.123.123.123\folder1)
>>>
>>> I can ping the share name of course and I can do a ping -a on the IP of
>>> the share and it brings the share name back just fine.
>>>
>>> I cannot figure out why I cannot use the IP address.
>>> Any ideas of what to check?
>>>
>>> Thanks.
>>> Jeff
>>
>
> Thanks Vladimir, this must only apply to cluster then? Because it still
> works for Win2k8 R2 and non-R2 non-clustered servers.
> Jeff

RCan wrote:
> correct - does only applies to failover clustering.
>
> Regards
> Ramazan
>
> "JJP" <> wrote in message
> news:...
>> Vladimir Petter wrote:
>>> This is by design. Change has happened in W2K8. Now share is scoped
>>> to the netname, and can be accessed only using this netname.
>>>
>>> Vladimir Petter
>>> Clustering and High Availability.
>>> This posting is provided "AS IS" with no warranties, and confers no
>>> rights.
>>>
>>> "JJP" <> wrote in message
>>> news:ey$...
>>>> JJP wrote:
>>>>> Hi,
>>>>> I have a Windows 2008 R2 cluster. I don't think this a cluster
>>>>> problem (I could be wrong) but I posted this in the Windows Server
>>>>> General and did not receive a response.
>>>>>
>>>>> I have a share that I can connect via the name \\ServerName\ShareName
>>>>>
>>>>> But I cannot connect via the IP \\123.123.123.123\ShareName
>>>>>
>>>>> This has always worked in the past with older OS's, and it works
>>>>> with our Win2k3 and Win2k8 (non R2) servers.
>>>>>
>>>>> Has something changed in R2?
>>>>>
>>>>> Thanks in advance.
>>>>> Jeff
>>>>
>>>>
>>>> Ok, I could be wrong about the cluster part. We built a test R2
>>>> (non-cluster) server today and tested a share and accessing by IP
>>>> works fine. So this is also not an R2 thing, unless it is R2
>>>> cluster related.
>>>>
>>>> So, I have this resource group that has a network name, an IP
>>>> address and a share.
>>>>
>>>> I can access the share this way:
>>>> \\sharename\folder1
>>>>
>>>> I cannot access the share this way:
>>>> \\shareIP\folder1
>>>> (example, \\123.123.123.123\folder1)
>>>>
>>>> I can ping the share name of course and I can do a ping -a on the IP
>>>> of the share and it brings the share name back just fine.
>>>>
>>>> I cannot figure out why I cannot use the IP address.
>>>> Any ideas of what to check?
>>>>
>>>> Thanks.
>>>> Jeff
>>>
>>
>> Thanks Vladimir, this must only apply to cluster then? Because it
>> still works for Win2k8 R2 and non-R2 non-clustered servers.
>> Jeff
>

Ok, wow, that is not a good change on MS part. Thank you both for the
replies and confirmation.
Jeff

Hi JJP,

Just my 2 cents here...

why does you so much rely on IP communications ? Do you have applications
which strongly relies on that ?
I would personally not in general exclude windows 2008 from your decision.
the x64 bit architecture (also x32) has a very solid kernel and can offer
great performance

Regards
Ramazan

"JJP" <> wrote in message
news:...
> RCan wrote:
>> correct - does only applies to failover clustering.
>>
>> Regards
>> Ramazan
>>
>> "JJP" <> wrote in message
>> news:...
>>> Vladimir Petter wrote:
>>>> This is by design. Change has happened in W2K8. Now share is scoped to
>>>> the netname, and can be accessed only using this netname.
>>>>
>>>> Vladimir Petter
>>>> Clustering and High Availability.
>>>> This posting is provided "AS IS" with no warranties, and confers no
>>>> rights.
>>>>
>>>> "JJP" <> wrote in message
>>>> news:ey$...
>>>>> JJP wrote:
>>>>>> Hi,
>>>>>> I have a Windows 2008 R2 cluster. I don't think this a cluster
>>>>>> problem (I could be wrong) but I posted this in the Windows Server
>>>>>> General and did not receive a response.
>>>>>>
>>>>>> I have a share that I can connect via the name \\ServerName\ShareName
>>>>>>
>>>>>> But I cannot connect via the IP \\123.123.123.123\ShareName
>>>>>>
>>>>>> This has always worked in the past with older OS's, and it works with
>>>>>> our Win2k3 and Win2k8 (non R2) servers.
>>>>>>
>>>>>> Has something changed in R2?
>>>>>>
>>>>>> Thanks in advance.
>>>>>> Jeff
>>>>>
>>>>>
>>>>> Ok, I could be wrong about the cluster part. We built a test R2
>>>>> (non-cluster) server today and tested a share and accessing by IP
>>>>> works fine. So this is also not an R2 thing, unless it is R2 cluster
>>>>> related.
>>>>>
>>>>> So, I have this resource group that has a network name, an IP address
>>>>> and a share.
>>>>>
>>>>> I can access the share this way:
>>>>> \\sharename\folder1
>>>>>
>>>>> I cannot access the share this way:
>>>>> \\shareIP\folder1
>>>>> (example, \\123.123.123.123\folder1)
>>>>>
>>>>> I can ping the share name of course and I can do a ping -a on the IP
>>>>> of the share and it brings the share name back just fine.
>>>>>
>>>>> I cannot figure out why I cannot use the IP address.
>>>>> Any ideas of what to check?
>>>>>
>>>>> Thanks.
>>>>> Jeff
>>>>
>>>
>>> Thanks Vladimir, this must only apply to cluster then? Because it still
>>> works for Win2k8 R2 and non-R2 non-clustered servers.
>>> Jeff
>>
>
> Ok, wow, that is not a good change on MS part. Thank you both for the
> replies and confirmation.
> Jeff

RCan wrote:
> Hi JJP,
>
> Just my 2 cents here...
>
> why does you so much rely on IP communications ? Do you have
> applications which strongly relies on that ?
> I would personally not in general exclude windows 2008 from your
> decision. the x64 bit architecture (also x32) has a very solid kernel
> and can offer great performance
>
> Regards
> Ramazan
>
> "JJP" <> wrote in message
> news:...
>> RCan wrote:
>>> correct - does only applies to failover clustering.
>>>
>>> Regards
>>> Ramazan
>>>
>>> "JJP" <> wrote in message
>>> news:...
>>>> Vladimir Petter wrote:
>>>>> This is by design. Change has happened in W2K8. Now share is scoped
>>>>> to the netname, and can be accessed only using this netname.
>>>>>
>>>>> Vladimir Petter
>>>>> Clustering and High Availability.
>>>>> This posting is provided "AS IS" with no warranties, and confers no
>>>>> rights.
>>>>>
>>>>> "JJP" <> wrote in message
>>>>> news:ey$...
>>>>>> JJP wrote:
>>>>>>> Hi,
>>>>>>> I have a Windows 2008 R2 cluster. I don't think this a cluster
>>>>>>> problem (I could be wrong) but I posted this in the Windows
>>>>>>> Server General and did not receive a response.
>>>>>>>
>>>>>>> I have a share that I can connect via the name
>>>>>>> \\ServerName\ShareName
>>>>>>>
>>>>>>> But I cannot connect via the IP \\123.123.123.123\ShareName
>>>>>>>
>>>>>>> This has always worked in the past with older OS's, and it works
>>>>>>> with our Win2k3 and Win2k8 (non R2) servers.
>>>>>>>
>>>>>>> Has something changed in R2?
>>>>>>>
>>>>>>> Thanks in advance.
>>>>>>> Jeff
>>>>>>
>>>>>>
>>>>>> Ok, I could be wrong about the cluster part. We built a test R2
>>>>>> (non-cluster) server today and tested a share and accessing by IP
>>>>>> works fine. So this is also not an R2 thing, unless it is R2
>>>>>> cluster related.
>>>>>>
>>>>>> So, I have this resource group that has a network name, an IP
>>>>>> address and a share.
>>>>>>
>>>>>> I can access the share this way:
>>>>>> \\sharename\folder1
>>>>>>
>>>>>> I cannot access the share this way:
>>>>>> \\shareIP\folder1
>>>>>> (example, \\123.123.123.123\folder1)
>>>>>>
>>>>>> I can ping the share name of course and I can do a ping -a on the
>>>>>> IP of the share and it brings the share name back just fine.
>>>>>>
>>>>>> I cannot figure out why I cannot use the IP address.
>>>>>> Any ideas of what to check?
>>>>>>
>>>>>> Thanks.
>>>>>> Jeff
>>>>>
>>>>
>>>> Thanks Vladimir, this must only apply to cluster then? Because it
>>>> still works for Win2k8 R2 and non-R2 non-clustered servers.
>>>> Jeff
>>>
>>
>> Ok, wow, that is not a good change on MS part. Thank you both for the
>> replies and confirmation.
>> Jeff
>

We don't need to rely "so much" on accessing shares via IP but
completely removing the ability to do so is excessive and is causing
people problems. How many things are there where you can access a
resource by name but not by IP? The other way around I could understand.

I found this thread yesterday and I hope the people who of
multi-function devices have found a solution:

http://social.technet.microsoft.com/...9-1ccf61689342