We have a share on our Windows 2003 server that we can map network drives to
by using the address

\\192.168.1.100\t$

If we use the map network drive command in My Computer from Windows XP, the
mapping works fine. If we try to do the mapping by creating a shortcut icon
on the desktop of the XP machine (right click on the desktop, click New, and
then Shortcut, and key in \\192.168.1.100\d$ for the location of the item),
we get an error indicating that "the file cannot be found".

How would you go about doing this? This server does not have a FQD name
that we can reference. We need to reference the IP Address.

Thanks.

Rog

On Fri, 7 Mar 2008 09:16:01 -0800, Roger Smith III
<(E-Mail Removed)> wrote:

>We have a share on our Windows 2003 server that we can map network drives to
>by using the address
>
>\\192.168.1.100\t$
>
>If we use the map network drive command in My Computer from Windows XP, the
>mapping works fine. If we try to do the mapping by creating a shortcut icon
>on the desktop of the XP machine (right click on the desktop, click New, and
>then Shortcut, and key in \\192.168.1.100\d$ for the location of the item),
>we get an error indicating that "the file cannot be found".
>
>How would you go about doing this? This server does not have a FQD name
>that we can reference. We need to reference the IP Address.
>
>Thanks.
>
>Rog

A shortcut using an IP address should work fine.

You said that the shortcut is to "\\192.168.1.100\d$". Should that be
"t$" instead of "d$"?

Does connecting to the shared drive require entering a user name? You
can specify a user name when mapping a network drive, but not in a
shortcut.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com

On Mar 7, 12:16*pm, Roger Smith III
<RogerSmith...@discussions.microsoft.com> wrote:
> We have a share on our Windows 2003 server that we can map network drives to
> by using the address
>
> \\192.168.1.100\t$
>
> If we use the map network drive command in My Computer from Windows XP, the
> mapping works fine. *If we try to do the mapping by creating a shortcut icon
> on the desktop of the XP machine (right click on the desktop, click New, and
> then Shortcut, and key in \\192.168.1.100\d$ for the location of the item),
> we get an error indicating that "the file cannot be found".
>
> How would you go about doing this? *This server does not have a FQD name
> that we can reference. *We need to reference the IP Address.
>
> Thanks.
>
> Rog

Any shared folder names with "$" seem to tell the Windows that this
is an "administrator" accessable share.

Did you type path \\192.168.1.100\t$ and \\192.168.1.100\d$ correctly?

--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"Roger Smith III" <(E-Mail Removed)> wrote in message
news:61097C8A-E0D4-47A2-84B3-(E-Mail Removed)...
> We have a share on our Windows 2003 server that we can map network drives
> to
> by using the address
>
> \\192.168.1.100\t$
>
> If we use the map network drive command in My Computer from Windows XP,
> the
> mapping works fine. If we try to do the mapping by creating a shortcut
> icon
> on the desktop of the XP machine (right click on the desktop, click New,
> and
> then Shortcut, and key in \\192.168.1.100\d$ for the location of the
> item),
> we get an error indicating that "the file cannot be found".
>
> How would you go about doing this? This server does not have a FQD name
> that we can reference. We need to reference the IP Address.
>
> Thanks.
>
> Rog
>
>

You guys must have waved the magic stick over my computer. It now works just
fine.

I right clicked on the desktop, selected New Shortcut. Keyed in

\\192.168.1.100\temptroll.

The server then prompted me for credentials, and the drive mapped fine.

Not sure why it didn't work before.

Thanks