Cross domain map network drive across VPN

  • Thread starter Thread starter BrianB
  • Start date Start date
B

BrianB

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
 
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?
Click to expand...

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
 
Back
Top