UNC Connection issue

I'm racking my brain trying to figure this out. We have a user in
another area of the country who's trying to access a shared drive on a
server via the UNC path. The problem is that he has to type the full
domain path in order to access the shared folder...but for the project
we're working on he MUST access it via the server name only. Example:

This is what he should be mapping a drive to:
\\servername\share$

but that path will not work for him. What does work though is:
\\servername.domain.com\share$

As I mentioned though, he MUST access it via the server name only
because we have specific requirements for the particular project we're
working on. We catalog various images, files, etc and they're all
cataloged using the \\servername\share$ path (which of course he can't
access but everyone else can).

What has to be done in order for that path to work for him?
Thanks

Hi,



can he try and do this on his PC...



nslookup servername



where servername is name of the server that he must connect to.



What does he get as result of nslookup? Does he get the correct IP address
of the server that he should connect to?



User can try and add another suffix into his TCP/IP configuration. Have user
open TCP/IP properties on his computer and instruct him to click on Advanced
button on the bottom right corner. Now he should select DNS tab and under
"Append these DNS suffixed (in order): and enter:



"domain.com"



Let me know if you need more assistance on this.


--
Mike
Microsoft MVP - Windows Security

"Spydrlink" <(E-Mail Removed)> wrote in message
news:8541564A-3CA7-45E6-AD5E-(E-Mail Removed)...
> I'm racking my brain trying to figure this out. We have a user in
> another area of the country who's trying to access a shared drive on a
> server via the UNC path. The problem is that he has to type the full
> domain path in order to access the shared folder...but for the project
> we're working on he MUST access it via the server name only. Example:
>
> This is what he should be mapping a drive to:
> \\servername\share$
>
> but that path will not work for him. What does work though is:
> \\servername.domain.com\share$
>
> As I mentioned though, he MUST access it via the server name only
> because we have specific requirements for the particular project we're
> working on. We catalog various images, files, etc and they're all
> cataloged using the \\servername\share$ path (which of course he can't
> access but everyone else can).
>
> What has to be done in order for that path to work for him?
> Thanks

In addition,

If the server has an external IP address you can create a entry in your host
file to resolve "server" to that IP.
Also, you can even have the user connect to the network via VPN, therefor
all traffic will be secured and you can use short names as well.

Hope this helps,
--
Louis Vitiello Jr.
------------------------------
MCSE, MCSA, MCP, A+/N+
ERCP XP Pro / Net Concepts



"Miha Pihler [MVP]" <mihap-(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi,
>
>
>
> can he try and do this on his PC...
>
>
>
> nslookup servername
>
>
>
> where servername is name of the server that he must connect to.
>
>
>
> What does he get as result of nslookup? Does he get the correct IP address
> of the server that he should connect to?
>
>
>
> User can try and add another suffix into his TCP/IP configuration. Have
> user open TCP/IP properties on his computer and instruct him to click on
> Advanced button on the bottom right corner. Now he should select DNS tab
> and under "Append these DNS suffixed (in order): and enter:
>
>
>
> "domain.com"
>
>
>
> Let me know if you need more assistance on this.
>
>
> --
> Mike
> Microsoft MVP - Windows Security
>
> "Spydrlink" <(E-Mail Removed)> wrote in message
> news:8541564A-3CA7-45E6-AD5E-(E-Mail Removed)...
>> I'm racking my brain trying to figure this out. We have a user in
>> another area of the country who's trying to access a shared drive on a
>> server via the UNC path. The problem is that he has to type the full
>> domain path in order to access the shared folder...but for the project
>> we're working on he MUST access it via the server name only. Example:
>>
>> This is what he should be mapping a drive to:
>> \\servername\share$
>>
>> but that path will not work for him. What does work though is:
>> \\servername.domain.com\share$
>>
>> As I mentioned though, he MUST access it via the server name only
>> because we have specific requirements for the particular project we're
>> working on. We catalog various images, files, etc and they're all
>> cataloged using the \\servername\share$ path (which of course he can't
>> access but everyone else can).
>>
>> What has to be done in order for that path to work for him?
>> Thanks
>
>

Thanks alot. I'll have him try these out and see what happens.