XP Home cannot find network resource

T

Terry

The program is installed on a server. A workstation using XP Home has a
shortcut on the Desktop. Dbl-clicking the icon would bring up the
"Connect to" dialog. Entering domain\user & password would launch program.

This no longer works. When the icon is dbl-clicked, Windows searches for
the program, can't find it and offers to remove the shortcut. If
Explorer is opened and the server is typed in the address bar
(\\server), the Connect to dialog comes up. After connecting that way,
the program can be launched from the icon on the Desktop.

What can be done to get the program to run directly from the shortcut again?

Thanks,


--
Terry

***Reply Note***
Anti-spam measures are included in my email address.
Delete NOSPAM from the email address after clicking Reply.
 
C

Carey Frisch [MVP]

Windows XP Home Edition is not designed to join a domain.
Only an upgrade to Windows XP Professional will permit
joining a domain.

--
Carey Frisch
Microsoft MVP
Windows XP - Shell/User
Microsoft Newsgroups

Be Smart! Protect Your PC!
http://www.microsoft.com/athome/security/protect/default.mspx

------------------------------------------------------------------------------

:

| The program is installed on a server. A workstation using XP Home has a
| shortcut on the Desktop. Dbl-clicking the icon would bring up the
| "Connect to" dialog. Entering domain\user & password would launch program.
|
| This no longer works. When the icon is dbl-clicked, Windows searches for
| the program, can't find it and offers to remove the shortcut. If
| Explorer is opened and the server is typed in the address bar
| (\\server), the Connect to dialog comes up. After connecting that way,
| the program can be launched from the icon on the Desktop.
|
| What can be done to get the program to run directly from the shortcut again?
|
| Thanks,
|
|
| --
| Terry
 
G

GTS

I don't know what may have changed and am a bit surprised that the icon
didn't do this all along. It's usually necessary to establish access rights
to a share before opening a resource. One solution would be to map the
share with a batch file either at start up or which then launches the
program (That might need a pause between.) I have a sample that might help
on my Tech Tips and Downloads page at
http:// [Remove this and spaces] www. gtscomputerservice. com
 
T

Terry

On 2/27/2005 9:20 AM On a whim, Carey Frisch [MVP] pounded out on the
keyboard
Windows XP Home Edition is not designed to join a domain.
Only an upgrade to Windows XP Professional will permit
joining a domain.

That wasn't what I asked. I'm aware of that fact. BUT Home can access
network resources and that is what many of these workstations are doing.
The program is installed on a network server. The Home workstations have
a shortcut pointing to the program on the server
(\\server\path\program). When the icon is clicked, the "Connect to"
dialog comes up. You enter a user name & password and connect to the
network. This works. But one workstation no longer can "find" the
location and does not prompt to "Connect to" any longer. Only by opening
Explorer first, then typing "\\server" in the Address bar does the
"Connect to" dialog come up. After we're connected to the server,
dbl-clicking the icon launches the program.

Maybe now you can answer my question?

--
Terry

***Reply Note***
Anti-spam measures are included in my email address.
Delete NOSPAM from the email address after clicking Reply.
 
T

Terry

On 2/27/2005 9:45 AM On a whim, GTS pounded out on the keyboard
I don't know what may have changed and am a bit surprised that the icon
didn't do this all along. It's usually necessary to establish access rights
to a share before opening a resource. One solution would be to map the
share with a batch file either at start up or which then launches the
program (That might need a pause between.) I have a sample that might help
on my Tech Tips and Downloads page at
http:// [Remove this and spaces] www. gtscomputerservice. com

Not really. As soon as you dbl-click the icon, the request to connect is
acknowledged and the "Connect to" dialog comes up. This has always been
the case whenever a Home version is connected to a domain (yes, I know
it won't connect to the domain, but it can access resources).



--
Terry

***Reply Note***
Anti-spam measures are included in my email address.
Delete NOSPAM from the email address after clicking Reply.
 
T

Terry

On 2/27/2005 12:38 PM On a whim, Terry pounded out on the keyboard
On 2/27/2005 9:20 AM On a whim, Carey Frisch [MVP] pounded out on the
keyboard




That wasn't what I asked. I'm aware of that fact. BUT Home can access
network resources and that is what many of these workstations are doing.
The program is installed on a network server. The Home workstations have
a shortcut pointing to the program on the server
(\\server\path\program). When the icon is clicked, the "Connect to"
dialog comes up. You enter a user name & password and connect to the
network. This works. But one workstation no longer can "find" the
location and does not prompt to "Connect to" any longer. Only by opening
Explorer first, then typing "\\server" in the Address bar does the
"Connect to" dialog come up. After we're connected to the server,
dbl-clicking the icon launches the program.

Maybe now you can answer my question?

Well it happened to another classroom computer while I was installing a
printer. Windows Update installed updates and the server program was
working fine. I rebooted and Windows "could not find program" just like
the computer described above. I did a SR back a couple weeks and
everything works fine again.

So now I have to install each of the updates one at a time and find out
which one is causing the issue.



--
Terry

***Reply Note***
Anti-spam measures are included in my email address.
Delete NOSPAM from the email address after clicking Reply.
 
T

Terry

On 2/27/2005 9:48 AM On a whim, GTS pounded out on the keyboard
XP Home can access resources on a domain with the right credentials and
configuration.
See http://www.windowsnetworking.com/articles_tutorials/wxphdoms.html for
more information.

Well it happened to another classroom computer while I was installing a
printer. Windows Update installed updates and the server program was
working fine. I rebooted and Windows "could not find program" just like
the computer described above. I did a SR back a couple weeks and
everything works fine again.

So now I have to install each of the updates one at a time and find out
which one is causing the issue.

--
Terry

***Reply Note***
Anti-spam measures are included in my email address.
Delete NOSPAM from the email address after clicking Reply.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top