Prev: XP - Ping one way but not other?
Next: lost ability to share files
From: BrianB on 17 Nov 2009 19:10
When my domain laptop is connected directly to the company domain network, I
can map a network server using just its name and omitting the domain suffix.
By this I mean that I and enter \\server1 instead of the fully qualified
\\server1.company.com. But when I work using the same laptop from my home
workgroup network and connect over VPN to the company network, if I try to
map a drive without using the fully qualified name, the server cannot be
found. But if I use the fully qualified name it maps without a problem.

Some time ago I made some setting change that effectively told Windows XP,
when mapping a non-qualified name, to first look on my LAN and then to
assume that the server name is qualified with ".company.com". I have no
memory how I did that. I've had to rebuild my laptop and lost that setting.
Anyone know what I need to do to get it back?

Brian


From: John Wunderlich on 18 Nov 2009 00:25
"BrianB" <brian.notthis.bygland(a)boeing.notthis.com> wrote in
news:e71MLO#ZKHA.5852(a)TK2MSFTNGP05.phx.gbl:

> When my domain laptop is connected directly to the company domain
> network, I can map a network server using just its name and
> omitting the domain suffix. By this I mean that I and enter
> \\server1 instead of the fully qualified \\server1.company.com.
> But when I work using the same laptop from my home workgroup
> network and connect over VPN to the company network, if I try to
> map a drive without using the fully qualified name, the server
> cannot be found. But if I use the fully qualified name it maps
> without a problem.
>
> Some time ago I made some setting change that effectively told
> Windows XP, when mapping a non-qualified name, to first look on my
> LAN and then to assume that the server name is qualified with
> ".company.com". I have no memory how I did that. I've had to
> rebuild my laptop and lost that setting. Anyone know what I need
> to do to get it back?

Refer to the following KB Article:

"How to configure TCP/IP to use DNS in Windows XP"
<http://support.microsoft.com/kb/305553>

Look for the section:
"How to modify the resolution behavior for unqualified DNS names"

HTH,
John

From: BrianB on 18 Nov 2009 11:14
"John Wunderlich" <jwunderlich(a)lycos.com> wrote in message
news:Xns9CC6D9F854C54wunderpsdrscray(a)207.46.248.16...
> "BrianB" <brian.notthis.bygland(a)boeing.notthis.com> wrote in
> news:e71MLO#ZKHA.5852(a)TK2MSFTNGP05.phx.gbl:
>
>> When my domain laptop is connected directly to the company domain
>> network, I can map a network server using just its name and
>> omitting the domain suffix. By this I mean that I and enter
>> \\server1 instead of the fully qualified \\server1.company.com.
>> But when I work using the same laptop from my home workgroup
>> network and connect over VPN to the company network, if I try to
>> map a drive without using the fully qualified name, the server
>> cannot be found. But if I use the fully qualified name it maps
>> without a problem.
>>
>> Some time ago I made some setting change that effectively told
>> Windows XP, when mapping a non-qualified name, to first look on my
>> LAN and then to assume that the server name is qualified with
>> ".company.com". I have no memory how I did that. I've had to
>> rebuild my laptop and lost that setting. Anyone know what I need
>> to do to get it back?
>
> Refer to the following KB Article:
>
> "How to configure TCP/IP to use DNS in Windows XP"
> <http://support.microsoft.com/kb/305553>
>
> Look for the section:
> "How to modify the resolution behavior for unqualified DNS names"
>
> HTH,
> John
>
Thank you


 | 
Pages: 1
Prev: XP - Ping one way but not other?
Next: lost ability to share files