General discussion

Locked

network going to sleep

By sroberts ·
Hi Guys and Girls :)
I have a school that has 18 computers with win XP OS networked to a WIN 2003 SERVER the problem i have is when the kids log on and start using office programs after a while when the want to save to the server they can not do it it comes up with a window asking for user name and password or says it can not find the certain folder on the server can any one help me out i am absolutely brain dead over this
cheers
steve

This conversation is currently closed to new comments.

13 total posts (Page 1 of 2)   01 | 02   Next
| Thread display: Collapse - | Expand +

All Comments

Collapse -

by jireland607 In reply to network going to sleep

Try mapping a drive to the server. I often find this a lot more reliable than browsing the network.

The username and password is usually required because the person who has logged into the client has not got permission to access the server. When you map a drive in xp, you have the option to map using a different username. Use a name that has access to the required folder.

Collapse -

by sroberts In reply to

Poster rated this answer.

Collapse -

by pierrejamme In reply to network going to sleep

Also make sure "Power Management" feature is turned off in the NIC configuration.
Control Panel\Network\Local Area Connection\Properties. Highlight NIC and "Configure" button, Power management tab and uncheck "Allow the computer to turn off this device to save power".
I haven't figured out a good use for this yet??

Collapse -

by sroberts In reply to

Poster rated this answer.

Collapse -

by sgt_shultz In reply to network going to sleep

could this be you?
support.microsoft.com mksb 830471
You experience intermittent connectivity when you connect to a network from a computer that is running Windows XP or Windows Server 2003
View products that this article applies to.
SYMPTOMS
You experience intermittent connectivity when you try to connect to a network from a computer that is running Microsoft Windows XP or Microsoft Windows Server 2003. If the computer connects to the network, you may receive the following error message:

The Windows Time Service was not able to find a Domain Controller. A time and date update was not possible.
CAUSE
This problem occurs because Transport Control Protocol/Internet Protocol (TCP/IP) Internet Protocol security (IPSec) frames that pass through NAT-T are not correctly acknowledged by TCP/IP.

This problem has been reported to occur on computers that have one of the following network adapters:
Intel Pro/100VE and Intel Pro Wireless LAN 2100 3B Mini
Intel Pro/100VE and ORiNOCO Wireless PCI
SiS 9000 PCI
RealTek 8139

Collapse -

by sgt_shultz In reply to

RESOLUTION
Hotfix information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Windows Server 2003 or Windows XP service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/default.aspx?scid=fh;[LN];CNTACTMS

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
Prerequisites
No prerequisites are required.
Restart requirement
Applying this hotfix may stop and restart network services.

Collapse -

by sgt_shultz In reply to

The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Windows Server 2003 IA-64
Date Time Version Size File name
--------------------------------------------------------------
16-Oct-2003 14:24 5.2.3790.93 970,240 Tcpip.sys
16-Oct-2003 15:12 5.2.3790.83 29,696 Wmspatcha.dll
26-Sep-2003 18:18 271 Branches.inf
16-Oct-2003 19:23 9,981 Kb830471.cat
16-Oct-2003 15:15 354 Updatebr.inf
16-Oct-2003 15:16 5,352 Update_rtmqfe.inf
Windows Server 2003 x86
Date Time Version Size File name
--------------------------------------------------------------
16-Oct-2003 17:25 5.2.3790.93 333,824 Tcpip.sys
26-Sep-2003 21:19 271 Branches.inf
16-Oct-2003 22:23 9,628 Kb830471.cat
16-Oct-2003 18:13 354 Updatebr.inf
16-Oct-2003 18:14 5,077 Update_rtmqfe.inf
Windows XP IA-64
Date Time Version Size File name
--------------------------------------------------------------
15-Oct-2003 19:48 5.1.2600.1310 1,106,432 Tcpip.sys
Windows XP x86
Date Time Version Size File name
--------------------------------------------------------------
16-Oct-2003 00:39 5.1.2600.1310 337,920 Tcpip.sys
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Collapse -

by sgt_shultz In reply to

maybe trying changing media type on nic from auto sense to 10mb half duplex on couple xp boxes for test?

Collapse -

by sroberts In reply to

Poster rated this answer.

Collapse -

by CG IT In reply to network going to sleep

I'm with Pierrejamme. I think it's the NICs power setting and the computer turns the NIC off to conserver power. That would account for lost connectivity.

Back to Windows Forum
13 total posts (Page 1 of 2)   01 | 02   Next

Related Discussions

Related Forums