Network paths not available after 15min to 30min of non-usage

18 – Windows XP computers are all setup in a Windows 2003 Standard
Domain. The single Windows 2003 server is running the “file server”
and “domain controller” roles.

12 of these Windows XP computers access two network paths from an
Windows XP workstation folder share (\\stn12\data) (\\stn12\od). These
paths are needed for the inventory program to work correctly. The
program itself is installed locally on each workstation; the program
just needs to access the path \\stan12\data... when it’s called up.

After 15min to 30min of non-use of the inventory program, the network
paths cannot be accessed or called up. The users have to log-out and
log back in to access the paths. Even using the run command and access
the paths directly do not work. I’ve tried mapping a network drives
for the paths and that appears to have-not fixed any problems. I’ve
also tried changing the network paths to ip (\\192.168.1.23\data)

What can I do to ensure these paths are fully accessible all the time?
Why would they be non-accessible? Should I enable DNS and DHCP
services on the windows 2003 server?

Any help would be appreciated.

Is it possible autodisconnect issue? This search result may help.

Mapping Issues
You may want to turn Autodisconnect off on the server. ... If you
would like to turn Autodisconnect off, do net config server
/autodisconnect:-1. ...
www.chicagotech.net/mapping.htm


--
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
<(E-Mail Removed)> wrote in message
news:e745433e-3761-4de9-80ce-(E-Mail Removed)...
18 – Windows XP computers are all setup in a Windows 2003 Standard
Domain. The single Windows 2003 server is running the “file server”
and “domain controller” roles.

12 of these Windows XP computers access two network paths from an
Windows XP workstation folder share (\\stn12\data) (\\stn12\od). These
paths are needed for the inventory program to work correctly. The
program itself is installed locally on each workstation; the program
just needs to access the path \\stan12\data... when it’s called up.

After 15min to 30min of non-use of the inventory program, the network
paths cannot be accessed or called up. The users have to log-out and
log back in to access the paths. Even using the run command and access
the paths directly do not work. I’ve tried mapping a network drives
for the paths and that appears to have-not fixed any problems. I’ve
also tried changing the network paths to ip (\\192.168.1.23\data)

What can I do to ensure these paths are fully accessible all the time?
Why would they be non-accessible? Should I enable DNS and DHCP
services on the windows 2003 server?

Any help would be appreciated.

(E-Mail Removed) wrote:
> 18 – Windows XP computers are all setup in a Windows 2003 Standard
> Domain. The single Windows 2003 server is running the “file server”
> and “domain controller” roles.
>
> 12 of these Windows XP computers access two network paths from an
> Windows XP workstation folder share (\\stn12\data) (\\stn12\od). These
> paths are needed for the inventory program to work correctly. The
> program itself is installed locally on each workstation; the program
> just needs to access the path \\stan12\data... when it’s called up.

Can this not be stored on the server? As in, \\server\share\folder\whatnot,
even if it's a different subfolder for each user?
>
> After 15min to 30min of non-use of the inventory program, the network
> paths cannot be accessed or called up. The users have to log-out and
> log back in to access the paths. Even using the run command and access
> the paths directly do not work. I’ve tried mapping a network drives
> for the paths and that appears to have-not fixed any problems. I’ve
> also tried changing the network paths to ip (\\192.168.1.23\data)
>
> What can I do to ensure these paths are fully accessible all the time?
> Why would they be non-accessible? Should I enable DNS and DHCP
> services on the windows 2003 server?

What's running DNS and DHCP now? If you're using AD and have only one
server, that server must run DNS (AD-integrated) and all servers/computers
should point *only* tothat IP address for DNS. If not, you're going to have
larger AD problems than just this minor irritant you're experiencing now.

Also, DHCP should run from your server as well - if it's currently running
from a router/etc on your LAN, you may have problems with dynamic DNS
updates from your clients. Change that.

NB - all of this may be irrelevant to your problem, although it is
definitely good advice. The fact that the UNC path is pointing to the
workstation itself indicates this isn't going to be something you can set up
on the server, such as the autodisconnect) - I'd really question the need to
have it using a local path to begin with. It would be much better to have
it point at the server (for data, not the application). If this software is
not network-friendly perhaps you should investigate getting some that is.
In a well-configured network, no data should be stored on workstations and
no workstations should have anything shared.

>
> Any help would be appreciated.