“File or Network Path No Longer Exists” or “No Network Provider Accepted the Given Network Path” Error Message When You Copy or Open Files in Windows XP SP1
Microsoft Windows 2000 Server, versions SP1, SP2, SP3 Microsoft Windows 2000 Professional, versions SP1, SP2, SP3
If you copy a large file over the network in Microsoft Windows XP Service Pack 1 (SP1) and the source file is located on a Microsoft Windows 2000-based share, you may receive either of the following error messages:
File or network path no longer exists.
No network provider accepted the given network path. You may also receive other error messages, depending on the program that you are using. The error message may occur if the source file is located on a Windows 2000-based share. This is a network-related Server Message Block (SMB) packet issue that may occur if SMB signing is enabled on the source Windows 2000-based computer.
Visit Microsoft for a fix, for this problem.
You Cannot Create a Network Connection After You Restore Windows XP
Microsoft Windows XP Professional
Microsoft Windows XP Home Edition
If you install Service Pack 1 (SP1) for Windows XP and then use the System Restore feature to restore Windows to a state before the installation of the service pack, you may experience the following symptoms:
You cannot create a remote access or Dial-Up Networking connection. All items on the “Network Connection” page of the New Connection Wizard are unavailable (dimmed).
The Network Connections folder is empty.
The Internet Connection Sharing (ICS) and Internet Connection Firewall (ICF) services do not start because of a dependency failure.
The following events are displayed in the System log of the Event Viewer:
Date: date Source: Service Control Manager
Time: time Category: None
Type: Error Event ID: 7023
The Remote Access Connection Manager service terminated with the following error:
Access is denied.
Date: date Source: RASMAN
Time: time Category: None
Type: Error Event ID: 20035
Remote Access Connection Manager failed to start because it could not create buffers. Restart the computer.
Access is denied.
When you try to start the Remote Access Connection Manager service, you receive the following error message:
Could not start the Remote Access Connection Manager service on Local Computer.
Error 5: Access is denied
To resolve this problem, reinstall SP1 for Windows XP. If you cannot reinstall SP1, start Registry Editor, and then locate the following registry subkey:
Export the RasMan subkey as exported rasman key. To undo the editing of this registry key, double-click the “Exported rasman key.reg” file that you just saved. Note the Data value for the ObjectName item. If this value is not LocalSystem, modify the ObjectName item to change the value data to LocalSystem. Locate the following registry subkey:
Delete the following registry keys under the EAP subkey: 25 26
Quit Registry Editor, and then restart your computer.
Network File Errors Occur After You Install Windows XP SP1
Microsoft Windows 2000 Server, versions SP1, SP2, SP3
Microsoft Windows 2000 Professional, versions SP1, SP2, SP3
Microsoft Windows XP Professional SP1
After you install Windows XP Service Pack 1 (SP1), you may see a variety of errors relating to Windows XP SP1 client computers. you may find some errors with the following ID’s in event viewer:
Event ID: 1058
Event ID: 1030
These problems occur because of an incompatibility in Server Message Block (SMB) signing between Microsoft Windows 2000 and Windows XP SP1. By default, SMB signing is turned on on domain controllers only when possible. By default, you only experience this problem when you copy files to and from a domain controller. However, if you apply policy settings or set registry keys to servers, you may experience problems when you copy files to and from a server.
To resolve this problem, apply the Q329170 hot fix that is described in the following Microsoft Knowledge Base article: Q329170 File or Network Path No Longer Exists Error Message When You Copy Files in Windows XP SP1
Setting up w2k/XP pro to logon to domain and workgroup
Here is a way to have your workstation logon to the domain at work as well as access your home workgroup.
Make sure that your home network has the same name as the work domain
eg. work =”pctechnicians.ca”
home workgroup name = “pctechnicians”.
Your home router\dhcp assigns the same network ip range.
Create a local user on your workstation, this should exist on the workgroup machines at home.
Workstation has the same computer name on both networks
now first setup your workstation to join the workgroup, let it get an ip from the router or what ever dhcp you use.
once connected and it has access to everything, then join it to the work domain.
logoff at the logon screen in the domain list box you will now have two options:
(computer name) logon to this computer.
note : this worked in a test environment, we cannot guarantee it will work for everyone please let me know if you have any problems
If your domain and workgroup name are different you will still be able to access the workgroup network but your machine will not show in the workgroup.
Hide username in XP’s logon screen
Go to start >>RUN and type regedt32.
then go to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microso ft\Windows NT\CurrentVersion\Winlogon\SpecialA ccounts\UserList
(note that there is a space in the Windows NT).
Right click in the right pane and select New, DWord value.
Give the value the same name as the Username on the Welcome Screen (it must match) for the account you wish to hide/show.
Double click the new value and set it to 1 to show the account on the Welcome Screen, or set it to 0 to hide the account.
Example: Robert is a user on the computer, Robert would be the name you give the new value.
the next time you restart your username will be hidden, press CTRL+ALT+DEL to logon.
Cannot Use Shared Internet Connection While Connected to a VPN
When you establish a connection through a VPN, packets are by default routed to the default gateway on the remote network of your VPN connection.
This behavior is by design. more..
WinXP: Windows Messenger won’t start…
While trying to start up Windows Messenger, the mouse cursor shows an hour glass for a few seconds and then nothing. Windows Messenger doesn’t come up and no error message is shown.
Uninstall, Re-install…. makes no difference.
And the Windows XP event viewer displays the following error:
The description for Event ID ( 4 ) in Source ( (MSN/Windows) Messenger Service ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event.
Using the registry editor, follow this path:
There you should see a key called PreventRun with a value set to 1. Change the value to 0.
Try Windows Messenger again. Should work fine now.
(contributed by Marc Paulin)
Computer Does Not Resume from Standby Mode in Windows 2000
When you attempt to resume your computer from Standby mode, the computer may not wake up.
This behavior can occur if the following two conditions both exist:
Advanced Power Management (APM) is enabled in the Power Options tool in Control Panel.
Your computer’s BIOS is configured to suspend your computer and the time-out value is less than the value configured in the Power Options tool in Control Panel.
To resolve this issue, configure the time-out settings in the Power Options tool in Control Panel so that they are for a shorter time than the APM time-out settings in your computer’s BIOS. To view or modify these settings in Control Panel, click Start, point to Settings, click Control Panel, and then double-click Power Options.
For information about how to view your computer’s BIOS settings, consult the documentation from your hardware manufacturer. KB 228225
No Desktop or Blank Desktop After Logging On to Windows 2000
When you log on to Windows 2000, you may see a blank desktop or no desktop. When this occurs, you can press CTRL+ALT+DELETE to start Task Manager, but Explorer.exe is not listed in the list of running tasks or processes. Starting a new instance of Explorer.exe does not resolve the issue.
1.Press CTRL+ALT+DELETE, and then click Task Manager.
2.On the File menu, click New Task (Run).
3.Type cmd.exe, and then press ENTER.
4.If necessary, change to the %SystemRoot% folder.
5.Rename the Shdocvw.dll file by typing ren shdocvw.dll shdocvw.old.
6.Restart the computer.
XP–Windows Delayed Write Failure
Windows – Delayed Write Failure
Windows was unable to save all the data for the file
\Device\Harddisk Volume 2\Recycled\Desktop.ini
This error may be caused by a failure of your computer hardware or network connection. Please try to save the file elsewhere.
1. Update controller driver: in device manager check what driver the drive controller is using if its MS then go to motherboard manufacturer’s site and look for an XP driver.
2. Go to Start � Programs � Administrative Tools – Computer Management � Storage – Disk Management.
In the upper part of the Computer Management window, right click on each of your hard drives in turn and select �Change drive letter and path�. Select Edit, [don’t actually change anything] and then click OK in the �Edit Drive Letter or Path� window.
Next go to the lower portion of the Computer Management window, right click on the gray box for each of your peripheral drives (CD Rom, Zip drive, etc.), and repeat the procedure.
Close all the windows. You may have to reboot.
Add Users Automates Creation of a Large Number of Users
Machines randomly shutting down with the following message:
“The system is shutting down. Please save all work in progress and log off. Any unsaved changes will be lost. This shutdown was initiated by NT AUTHORITY\SYSTEM.
The system process C:\WINNT\System32\lsass.exe terminated unexpectedly with status code 128. The system will shut down and restart.”
Cause: the machines could be infected with the Sasser Worm.
Visit MS for more information
Windows XP Service Pack 2 disables network access:
In XP SP2, the firewall is enabled.
This blocks the browser NetBIOS ports.
So the browser service does not start.
If you enable the File & Print sharing exception, the browser service can be
The Computer Browser service does not start and event ID 7024 is
logged when you restart your Windows XP Service Pack 2-based
Enable RDP on remote computer:
Click File then select “connect to remote registry”
Go to SYSTEM\CurrentControlSet\Control\Terminal Server
Look for value named fDenyTSConnection
Double-click on that value to open the Edit DWORD
change the value data from 1 (Remote Desktop disabled) to 0 (Remote Desktop enabled)
Experts Exchange: the most powerful Windows 2000 resource in the world. Access instant solutions for your most demanding Windows2000 problems. Our vast IT library puts more IT information at your finger tips. You are moments away from finding your solution.
ITToolBox: ITtoolbox is a leading provider of information for the IT industry. Powering a global audience of over one million technology and business professionals each month.
TechTutorials: TechTutorials is committed to delivering the best of freely available technical resources to our users, by integrating content and functionality