Issue:
Unable to map network drive using the hostname of the filer but can map
using its IP address.

I have already ensure that I an ping the filer by hostname and that I am
getting correct NSLOOKUP's. I also changed my security settings to use
LM/NTLM (down from NTLMv2).
Its not a GPO issue, no GPO's are being applied. Computer is a member of a
test domain (win2k3)

This is interesting. So you can map using IP and ping by the name. what do you receive if using net view \\hostname? Please post back with the result.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"RonPaskowski" wrote in message ...
Issue:
Unable to map network drive using the hostname of the filer but can map
using its IP address.

I have already ensure that I an ping the filer by hostname and that I am
getting correct NSLOOKUP's. I also changed my security settings to use
LM/NTLM (down from NTLMv2).
Its not a GPO issue, no GPO's are being applied. Computer is a member of a
test domain (win2k3)

I get a list of all available shares. I am trying to attach to shares on a
NetApp Filer, which uses the CIFS File system.... which Windows is comp with.

This is very frustrating that I can't map using hostname. I also tested a
freshly installed version of Vista as well.



"Robert L [MVP - Networking]" wrote:

This is interesting. So you can map using IP and ping by the name. what do you receive if using net view \\hostname? Please post back with the result.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"RonPaskowski" wrote in message ...
Issue:
Unable to map network drive using the hostname of the filer but can map
using its IP address.

I have already ensure that I an ping the filer by hostname and that I am
getting correct NSLOOKUP's. I also changed my security settings to use
LM/NTLM (down from NTLMv2).
Its not a GPO issue, no GPO's are being applied. Computer is a member of a
test domain (win2k3)

What's the system error code when using net use x: \\hostname\sharedname?

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"RonPaskowski" wrote in message ...
I get a list of all available shares. I am trying to attach to shares on a
NetApp Filer, which uses the CIFS File system.... which Windows is comp with.

This is very frustrating that I can't map using hostname. I also tested a
freshly installed version of Vista as well.



"Robert L [MVP - Networking]" wrote:

This is interesting. So you can map using IP and ping by the name. what do you receive if using net view \\hostname? Please post back with the result.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"RonPaskowski" wrote in message ...
Issue:
Unable to map network drive using the hostname of the filer but can map
using its IP address.

I have already ensure that I an ping the filer by hostname and that I am
getting correct NSLOOKUP's. I also changed my security settings to use
LM/NTLM (down from NTLMv2).
Its not a GPO issue, no GPO's are being applied. Computer is a member of a
test domain (win2k3)

Also, have you tried using the FQDN of the Netapp?

"RonPaskowski" wrote in message
...
I get a list of all available shares. I am trying to attach to shares on a
NetApp Filer, which uses the CIFS File system.... which Windows is comp
with.

This is very frustrating that I can't map using hostname. I also tested a
freshly installed version of Vista as well.



"Robert L [MVP - Networking]" wrote:

This is interesting. So you can map using IP and ping by the name. what
do you receive if using net view \\hostname? Please post back with the
result.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"RonPaskowski" wrote in
message ...
Issue:
Unable to map network drive using the hostname of the filer but can map
using its IP address.

I have already ensure that I an ping the filer by hostname and that I
am
getting correct NSLOOKUP's. I also changed my security settings to use
LM/NTLM (down from NTLMv2).
Its not a GPO issue, no GPO's are being applied. Computer is a member
of a
test domain (win2k3)

Actuall Joe and Robert, I think I found the problem..

Doing some research on the issue, I came across an article on TechRepublic
(below) that identifies a known bug with Data ONTAP versions (NetApp) and MS
Vista. It’s a Kerberos issue when attempting to access the data by hostname
and the only work around is to force Vista to use NTLM authentication by
accessing the share by IP address.


NetApp apparently has a bug ID associated with the issue: Bug ID 174785 Ã*
(http://now.netapp.com/NOW/cgi-bin/bo...Display=174785)
*

Bug Detail
Bug ID 174785
Attempting to mount a filer's CIFS share with a Microsoft Vista client (Beta
1) will result in a failure when using Kerberos authentication.
Bug Severity 2 - System barely usable
Bug Status Fixed
Product Data ONTAP
Bug Type CIFS
Description

The Microsoft's Vista Operating System is unable to mount CIFS shares from a
filer when Kerberos authentication is specified.
This occurs when the user specifies a DNS name when creating the network
connection on the Vista client (e.g. net use * \\filer-name\share).

Workaround
Create the network connection using the IP address of the filer instead of
the DNS name (e.g. net use * \\x.y.z.q\share). This will cause NTLM
authentication to take place.

Related Solutions
Fixed-In Version:
Data ONTAP 7.1P3 (First Fixed) - Fixed
Data ONTAP 7.2RC3 (RC) - Fixed



"Joe Guidera" wrote:

Also, have you tried using the FQDN of the Netapp?

"RonPaskowski" wrote in message
...
I get a list of all available shares. I am trying to attach to shares on a
NetApp Filer, which uses the CIFS File system.... which Windows is comp
with.

This is very frustrating that I can't map using hostname. I also tested a
freshly installed version of Vista as well.



"Robert L [MVP - Networking]" wrote:

This is interesting. So you can map using IP and ping by the name. what
do you receive if using net view \\hostname? Please post back with the
result.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"RonPaskowski" wrote in
message ...
Issue:
Unable to map network drive using the hostname of the filer but can map
using its IP address.

I have already ensure that I an ping the filer by hostname and that I
am
getting correct NSLOOKUP's. I also changed my security settings to use
LM/NTLM (down from NTLMv2).
Its not a GPO issue, no GPO's are being applied. Computer is a member
of a
test domain (win2k3)

I'd be curious to know if the fix was a Netapp fix or a Vista one... I
suspect it's an issue with NTLMV2, but just curious.

J

"RonPaskowski" wrote in message
...
Actuall Joe and Robert, I think I found the problem..

Doing some research on the issue, I came across an article on TechRepublic
(below) that identifies a known bug with Data ONTAP versions (NetApp) and
MS
Vista. It’s a Kerberos issue when attempting to access the data by
hostname
and the only work around is to force Vista to use NTLM authentication by
accessing the share by IP address.


NetApp apparently has a bug ID associated with the issue: Bug ID 174785 Ã*
(http://now.netapp.com/NOW/cgi-bin/bo...Display=174785)
*

Bug Detail
Bug ID 174785
Attempting to mount a filer's CIFS share with a Microsoft Vista client
(Beta
1) will result in a failure when using Kerberos authentication.
Bug Severity 2 - System barely usable
Bug Status Fixed
Product Data ONTAP
Bug Type CIFS
Description

The Microsoft's Vista Operating System is unable to mount CIFS shares from
a
filer when Kerberos authentication is specified.
This occurs when the user specifies a DNS name when creating the network
connection on the Vista client (e.g. net use * \\filer-name\share).

Workaround
Create the network connection using the IP address of the filer instead of
the DNS name (e.g. net use * \\x.y.z.q\share). This will cause NTLM
authentication to take place.

Related Solutions
Fixed-In Version:
Data ONTAP 7.1P3 (First Fixed) - Fixed
Data ONTAP 7.2RC3 (RC) - Fixed



"Joe Guidera" wrote:

Also, have you tried using the FQDN of the Netapp?

"RonPaskowski" wrote in message
...
I get a list of all available shares. I am trying to attach to shares on
a
NetApp Filer, which uses the CIFS File system.... which Windows is comp
with.

This is very frustrating that I can't map using hostname. I also tested
a
freshly installed version of Vista as well.



"Robert L [MVP - Networking]" wrote:

This is interesting. So you can map using IP and ping by the name.
what
do you receive if using net view \\hostname? Please post back with the
result.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"RonPaskowski" wrote in
message ...
Issue:
Unable to map network drive using the hostname of the filer but can
map
using its IP address.

I have already ensure that I an ping the filer by hostname and that
I
am
getting correct NSLOOKUP's. I also changed my security settings to
use
LM/NTLM (down from NTLMv2).
Its not a GPO issue, no GPO's are being applied. Computer is a
member
of a
test domain (win2k3)

Joe,

There is a Microsoft Patch
(http://support.microsoft.com/kb/933664/en-us#appliesto), its a HOTFIX and
not planned to be released until SP1 for Vista. We were able to get a copy of
the HOTFIX from MS and it worked like a charm.



"Joe Guidera" wrote:

I'd be curious to know if the fix was a Netapp fix or a Vista one... I
suspect it's an issue with NTLMV2, but just curious.

J

"RonPaskowski" wrote in message
...
Actuall Joe and Robert, I think I found the problem..

Doing some research on the issue, I came across an article on TechRepublic
(below) that identifies a known bug with Data ONTAP versions (NetApp) and
MS
Vista. It’s a Kerberos issue when attempting to access the data by
hostname
and the only work around is to force Vista to use NTLM authentication by
accessing the share by IP address.


NetApp apparently has a bug ID associated with the issue: Bug ID 174785 Ã*
(http://now.netapp.com/NOW/cgi-bin/bo...Display=174785)
*

Bug Detail
Bug ID 174785
Attempting to mount a filer's CIFS share with a Microsoft Vista client
(Beta
1) will result in a failure when using Kerberos authentication.
Bug Severity 2 - System barely usable
Bug Status Fixed
Product Data ONTAP
Bug Type CIFS
Description

The Microsoft's Vista Operating System is unable to mount CIFS shares from
a
filer when Kerberos authentication is specified.
This occurs when the user specifies a DNS name when creating the network
connection on the Vista client (e.g. net use * \\filer-name\share).

Workaround
Create the network connection using the IP address of the filer instead of
the DNS name (e.g. net use * \\x.y.z.q\share). This will cause NTLM
authentication to take place.

Related Solutions
Fixed-In Version:
Data ONTAP 7.1P3 (First Fixed) - Fixed
Data ONTAP 7.2RC3 (RC) - Fixed



"Joe Guidera" wrote:

Also, have you tried using the FQDN of the Netapp?

"RonPaskowski" wrote in message
...
I get a list of all available shares. I am trying to attach to shares on
a
NetApp Filer, which uses the CIFS File system.... which Windows is comp
with.

This is very frustrating that I can't map using hostname. I also tested
a
freshly installed version of Vista as well.



"Robert L [MVP - Networking]" wrote:

This is interesting. So you can map using IP and ping by the name.
what
do you receive if using net view \\hostname? Please post back with the
result.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"RonPaskowski" wrote in
message ...
Issue:
Unable to map network drive using the hostname of the filer but can
map
using its IP address.

I have already ensure that I an ping the filer by hostname and that
I
am
getting correct NSLOOKUP's. I also changed my security settings to
use
LM/NTLM (down from NTLMv2).
Its not a GPO issue, no GPO's are being applied. Computer is a
member
of a
test domain (win2k3)

Thanks. I have access to that hotfix. Good to know if I experience that
specific issue.

Joe

"RonPaskowski" wrote in message
...
Joe,

There is a Microsoft Patch
(http://support.microsoft.com/kb/933664/en-us#appliesto), its a HOTFIX and
not planned to be released until SP1 for Vista. We were able to get a copy
of
the HOTFIX from MS and it worked like a charm.



"Joe Guidera" wrote:

I'd be curious to know if the fix was a Netapp fix or a Vista one... I
suspect it's an issue with NTLMV2, but just curious.

J

"RonPaskowski" wrote in message
...
Actuall Joe and Robert, I think I found the problem..

Doing some research on the issue, I came across an article on
TechRepublic
(below) that identifies a known bug with Data ONTAP versions (NetApp)
and
MS
Vista. It’s a Kerberos issue when attempting to access the data by
hostname
and the only work around is to force Vista to use NTLM authentication
by
accessing the share by IP address.


NetApp apparently has a bug ID associated with the issue: Bug ID 174785
Ã*
(http://now.netapp.com/NOW/cgi-bin/bo...Display=174785)
*

Bug Detail
Bug ID 174785
Attempting to mount a filer's CIFS share with a Microsoft Vista client
(Beta
1) will result in a failure when using Kerberos authentication.
Bug Severity 2 - System barely usable
Bug Status Fixed
Product Data ONTAP
Bug Type CIFS
Description

The Microsoft's Vista Operating System is unable to mount CIFS shares
from
a
filer when Kerberos authentication is specified.
This occurs when the user specifies a DNS name when creating the
network
connection on the Vista client (e.g. net use * \\filer-name\share).

Workaround
Create the network connection using the IP address of the filer instead
of
the DNS name (e.g. net use * \\x.y.z.q\share). This will cause NTLM
authentication to take place.

Related Solutions
Fixed-In Version:
Data ONTAP 7.1P3 (First Fixed) - Fixed
Data ONTAP 7.2RC3 (RC) - Fixed



"Joe Guidera" wrote:

Also, have you tried using the FQDN of the Netapp?

"RonPaskowski" wrote in
message
...
I get a list of all available shares. I am trying to attach to shares
on
a
NetApp Filer, which uses the CIFS File system.... which Windows is
comp
with.

This is very frustrating that I can't map using hostname. I also
tested
a
freshly installed version of Vista as well.



"Robert L [MVP - Networking]" wrote:

This is interesting. So you can map using IP and ping by the name.
what
do you receive if using net view \\hostname? Please post back with
the
result.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"RonPaskowski" wrote in
message ...
Issue:
Unable to map network drive using the hostname of the filer but
can
map
using its IP address.

I have already ensure that I an ping the filer by hostname and
that
I
am
getting correct NSLOOKUP's. I also changed my security settings
to
use
LM/NTLM (down from NTLMv2).
Its not a GPO issue, no GPO's are being applied. Computer is a
member
of a
test domain (win2k3)