Mailing List Archive: Netapp: toasters

Problems connecting to CIFS share from some Windows XP clients

Index | Next | Previous | View Threaded

mcmorran at mdibl

Sep 10, 2009, 9:06 AM

Post #1 of 4 (956 views)
Permalink

Problems connecting to CIFS share from some Windows XP clients

Hello all,

I'm trying to troubleshoot an odd problem with a handful of Windows XP
clients. When trying to map a drive to a CIFS share on the NetApp, the
operation will fail with the obtuse message "a device attached to the
system is not functioning" (or system error 59 in the case of a
command-line "net use").

What is odd is that a pktt trace on the filer shows the Windows client
is trying to connect via HTTP rather than CIFS (we're not licensed for
HTTP, and that's certainly not what we want anyway):

Client:
OPTIONS / HTTP/1.1\r\n
Request Method: OPTIONS
translate: f\r\n
User-Agent: Microsoft-WebDAV-MiniRedir/5.1.2600\r\n
Host: xxx.xxx.xxx\r\n
Content-Length: 0\r\n
Connection: Keep-Alive\r\n
\r\n

Filer Response:
HTTP/1.1 503 HTTP is not licensed.<p>To administer this filer, use
<a href=/na_admin/>/na_admin/</a> .\r\n
Response Code: 503
Server: NetApp/7.2.5\r\n
Date: Thu, 10 Sep 2009 15:35:49 GMT\r\n
Content-Length: 188\r\n
Content-Type: text/html\r\n
\r\n

It never tries CIFS (SMB).

The problem machine (of the moment) is trying to connect via a wireless
router; moving it to a wired connection (on the same IP subnet as the
filer) stops the problem occurring. However, I have seen the problem
occur with wired connections as well. And also, many other clients
machines work just fine via the same wireless connection.

I doubt that this is a NetApp problem per se, but I'm hoping someone
else may have seen this before. Any thoughts?

Thanks!

--
Roy McMorran
Systems Administrator
MDI Biological Laboratory
mcmorran[at]mdibl.org

Langdon.Lock at mayo

Sep 10, 2009, 9:51 AM

Post #2 of 4 (896 views)
Permalink

RE: Problems connecting to CIFS share from some Windows XP clients [In reply to]

Have you tried the mapping with a fully qualified domain name?

-----Original Message-----
From: owner-toasters[at]mathworks.com [mailto:owner-toasters[at]mathworks.com]
On Behalf Of Roy McMorran
Sent: Thursday, September 10, 2009 9:07 AM
To: toasters[at]mathworks.com
Subject: Problems connecting to CIFS share from some Windows XP clients

Hello all,

I'm trying to troubleshoot an odd problem with a handful of Windows XP
clients. When trying to map a drive to a CIFS share on the NetApp, the
operation will fail with the obtuse message "a device attached to the
system is not functioning" (or system error 59 in the case of a
command-line "net use").

What is odd is that a pktt trace on the filer shows the Windows client
is trying to connect via HTTP rather than CIFS (we're not licensed for
HTTP, and that's certainly not what we want anyway):

Client:
OPTIONS / HTTP/1.1\r\n
Request Method: OPTIONS
translate: f\r\n
User-Agent: Microsoft-WebDAV-MiniRedir/5.1.2600\r\n
Host: xxx.xxx.xxx\r\n
Content-Length: 0\r\n
Connection: Keep-Alive\r\n
\r\n

Filer Response:
HTTP/1.1 503 HTTP is not licensed.<p>To administer this filer, use
<a href=/na_admin/>/na_admin/</a> .\r\n
Response Code: 503
Server: NetApp/7.2.5\r\n
Date: Thu, 10 Sep 2009 15:35:49 GMT\r\n
Content-Length: 188\r\n
Content-Type: text/html\r\n
\r\n

It never tries CIFS (SMB).

The problem machine (of the moment) is trying to connect via a wireless
router; moving it to a wired connection (on the same IP subnet as the
filer) stops the problem occurring. However, I have seen the problem
occur with wired connections as well. And also, many other clients
machines work just fine via the same wireless connection.

I doubt that this is a NetApp problem per se, but I'm hoping someone
else may have seen this before. Any thoughts?

Thanks!

--
Roy McMorran
Systems Administrator
MDI Biological Laboratory
mcmorran[at]mdibl.org

garyr at netapp

Sep 10, 2009, 10:09 AM

Post #3 of 4 (892 views)
Permalink

RE: Problems connecting to CIFS share from some Windows XP clients [In reply to]

Hi Roy,

Have a look here http://support.microsoft.com/kb/832161

The fact the client is advertising an agent of "
Microsoft-WebDAV-MiniRedir" shows the issue to be client/server
orientated. With webclient activated the Network Provider Order lists
Web Client Network before it lists Microsoft Windows Network. Which is
what I believe you are seeing.

-----Original Message-----
From: Langdon, Laughlin T. (Lock) [mailto:Langdon.Lock[at]mayo.edu]
Sent: Thursday, September 10, 2009 5:51 PM
To: Roy McMorran; toasters[at]mathworks.com
Subject: RE: Problems connecting to CIFS share from some Windows XP
clients

Have you tried the mapping with a fully qualified domain name?

-----Original Message-----
From: owner-toasters[at]mathworks.com [mailto:owner-toasters[at]mathworks.com]
On Behalf Of Roy McMorran
Sent: Thursday, September 10, 2009 9:07 AM
To: toasters[at]mathworks.com
Subject: Problems connecting to CIFS share from some Windows XP clients

Hello all,

I'm trying to troubleshoot an odd problem with a handful of Windows XP
clients. When trying to map a drive to a CIFS share on the NetApp, the
operation will fail with the obtuse message "a device attached to the
system is not functioning" (or system error 59 in the case of a
command-line "net use").

What is odd is that a pktt trace on the filer shows the Windows client
is trying to connect via HTTP rather than CIFS (we're not licensed for
HTTP, and that's certainly not what we want anyway):

Client:
OPTIONS / HTTP/1.1\r\n
Request Method: OPTIONS
translate: f\r\n
User-Agent: Microsoft-WebDAV-MiniRedir/5.1.2600\r\n
Host: xxx.xxx.xxx\r\n
Content-Length: 0\r\n
Connection: Keep-Alive\r\n
\r\n

Filer Response:
HTTP/1.1 503 HTTP is not licensed.<p>To administer this filer, use
<a href=/na_admin/>/na_admin/</a> .\r\n
Response Code: 503
Server: NetApp/7.2.5\r\n
Date: Thu, 10 Sep 2009 15:35:49 GMT\r\n
Content-Length: 188\r\n
Content-Type: text/html\r\n
\r\n

It never tries CIFS (SMB).

The problem machine (of the moment) is trying to connect via a wireless
router; moving it to a wired connection (on the same IP subnet as the
filer) stops the problem occurring. However, I have seen the problem
occur with wired connections as well. And also, many other clients
machines work just fine via the same wireless connection.

I doubt that this is a NetApp problem per se, but I'm hoping someone
else may have seen this before. Any thoughts?

Thanks!

--
Roy McMorran
Systems Administrator
MDI Biological Laboratory
mcmorran[at]mdibl.org

mcmorran at mdibl

Sep 10, 2009, 12:52 PM

Post #4 of 4 (891 views)
Permalink

Re: Problems connecting to CIFS share from some Windows XP clients [In reply to]

Hello all, thanks for the replies!

Reeves, Gary wrote:
> Have a look here http://support.microsoft.com/kb/832161
>

Yes, I have read that article already. It does seem related, but...
> With webclient activated the Network Provider Order lists
> Web Client Network before it lists Microsoft Windows Network. Which is
> what I believe you are seeing.
>

...the network provider order does list "Microsoft Windows Network"
before "Web Client Network", on both the machines that work and the
machines that fail. Furthermore. on machines that work, I can change
the order (ie. put "Web Client Network" first) and they continue to work.

I did try disabling the Web Client service as mentioned in the KB
article. In this case the filer sees virtually no traffic from the
client at all (no SMB/CIFS, no HTTP, just some ICMP pings)

Langdon, Laughlin T. wrote:
> Have you tried the mapping with a fully qualified domain name?
>
The behavior is the same with short name and fqdn.

Ryan Dorman wrote:
> Do you get a response from NBTSTAT -a for the short name?
>

Yes.
> Is there a message in the logs saying that a WINS registration succeeded and do you see the entry on your WINS server (if you have one)?

Client or server? The server is definitely there. The client has been
moved back to the wired network (where the drive mapping works properly)
so the entry (if it existed) has been overwritten. (BTW, the WINS
server is Samba)

--
Roy McMorran
Systems Administrator
MDI Biological Laboratory
mcmorran[at]mdibl.org

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact lists@gossamer-threads.com