Re: no mapped drive
- From: v-rebc@xxxxxxxxxxxxxxxxxxxx ("Rebecca Chen [MSFT]")
- Date: Tue, 28 Jun 2005 08:24:05 GMT
Hi Mike,
Thanks for getting back to me.
A follow up questions are:
1. Are you able to use \\servername to open the share?
2. Do you have WINS installed in the network?
3. Is the file server located in the same subnet as the problematic client?
Since you are able to map the drive by using the IP address, it seems this
is a NetBIOS name resolution issue. If you get "path not found" when using
\\servername to open the share, I suggest you install WINS service on the
DC. Generally speaking, if there are many subnet, installing WINS is
recommend. The following article has addressed how to install WINS in the
network:
Install and manage WINS servers
http://www.microsoft.com/windows2000/en/advanced/help/default.asp?url=/windo
ws2000/en/advanced/help/sag_WINS_pro_ManageSrvNode.htm
If you have any update, please feel free to post back.
Best regards,
Rebecca Chen
MCSE2000 MCDBA CCNA
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
>From: "Mike Koch" <mikey@xxxxxxxxxxxxxxxxx>
>References: <#1OhiyPcFHA.2180@xxxxxxxxxxxxxxxxxxxx>
<7lSiUVWcFHA.3052@xxxxxxxxxxxxxxxxxxxxx>
>Subject: Re: no mapped drive
>Date: Mon, 27 Jun 2005 15:43:57 -0400
>Lines: 108
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2900.2527
>X-RFC2646: Format=Flowed; Original
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527
>Message-ID: <e9CmRC1eFHA.1600@xxxxxxxxxxxxxxxxxxxx>
>Newsgroups: microsoft.public.windows.terminal_services
>NNTP-Posting-Host: 65.202.11.7
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windows.terminal_services:14786
>X-Tomcat-NG: microsoft.public.windows.terminal_services
>
>Hi Rebecca,
>
>Sorry for the delay in responding.
>
>1. Yes, pinging via IP and NetBIOS name work just fine.
>2. No, the drive does not map ("network name cannot be found") from
terminal
>session or local console.
>3. We use the name in the logon script. Map by IP address DOES work.
>4. Yes, using the IP address works fine.
>
>nslookup returns the address of the file server perfectly.
>
>Flushing and re-registering the file server in DNS made no difference.
>
>Still looking,
>Mike
>
>
>""Rebecca Chen [MSFT]"" <v-rebc@xxxxxxxxxxxxxxxxxxxx> wrote in message
>news:7lSiUVWcFHA.3052@xxxxxxxxxxxxxxxxxxxxxxxx
>> Hi Mike,
>>
>> I would like to confirm the following information about this issue to
>> determine if this issue is related to the terminal session, name
>> resolution
>> or network communication.
>>
>> 1. Are you able to ping though the file server via IP address and NetBIOS
>> name?
>> 2. Does this issue only occur in terminal session? If you map the drive
on
>> a local machine, what is the result?
>> 3. Do you use name to map the drive or use the IP address? Are you able
to
>> map the drive by IP address?
>> 4. What is the result if you visit the network drive via UNC like
>> \\192.168.0.1 ?
>>
>> If you can use IP to map drive, it is a name resolution issue. Please on
>> the local machine to open CMD, issue the following command:
>>
>> Nslookup FileServerName
>>
>> Can DNS successfully resolve the name? If DNS cannot resolve the name, it
>> is possible that the A record for the FileServer is missing. Please on
the
>> FilesServer to open CMD, issue the following command:
>>
>> Ipconfig /flushdns
>> Ipconfig /registerdns
>>
>> Please check if the correct record is registered in DNS.
>>
>> I look forward to your reply.
>>
>> --------------------
>>>From: "Mike Koch" <mikey@xxxxxxxxxxxxxxxxx>
>>>Subject: no mapped drive
>>>Date: Tue, 14 Jun 2005 12:17:58 -0400
>>>Lines: 14
>>>X-Priority: 3
>>>X-MSMail-Priority: Normal
>>>X-Newsreader: Microsoft Outlook Express 6.00.2900.2527
>>>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527
>>>X-RFC2646: Format=Flowed; Original
>>>Message-ID: <#1OhiyPcFHA.2180@xxxxxxxxxxxxxxxxxxxx>
>>>Newsgroups: microsoft.public.windows.terminal_services
>>>NNTP-Posting-Host: 65.202.11.7
>>>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
>>>Xref: TK2MSFTNGXA01.phx.gbl
>> microsoft.public.windows.terminal_services:14382
>>>X-Tomcat-NG: microsoft.public.windows.terminal_services
>>>
>>>Strange, but no one can map a drive to our file server from within a
>> Windows
>>>2003 terminal session.
>>>
>>> - the file server is running Windows Server 2003 Standard (no SP1)
>>> - all other machines in the domain can map to this server with no
problem
>>>
>>>All attempts to access this one server results in "path not found"
errors.
>>>
>>>I'm stumped at the moment. Anyone have any ideas?
>>>
>>>Thanks,
>>>Mike
>>>
>>>
>>>
>>
>> Best regards,
>>
>> Rebecca Chen
>>
>> MCSE2000 MCDBA CCNA
>>
>>
>> Microsoft Online Partner Support
>> Get Secure! - www.microsoft.com/security
>>
>> =====================================================
>>
>> When responding to posts, please "Reply to Group" via your newsreader so
>> that others may learn and benefit from your issue.
>>
>> =====================================================
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>
>
>
.
- References:
- no mapped drive
- From: Mike Koch
- RE: no mapped drive
- From: "Rebecca Chen [MSFT]"
- Re: no mapped drive
- From: Mike Koch
- no mapped drive
- Prev by Date: Re: transfer files
- Next by Date: could not connect to the remote computer
- Previous by thread: Re: no mapped drive
- Next by thread: Terminal Server connections freezing\dropping
- Index(es):
Relevant Pages
|
|
