|
Windows XP SP
Post your questions, comments, feedbacks and suggestions
Contact a consultant
Cannot run NetMeeting
after installing SP2
By default, Windows Firewall is turned on in Windows XP SP2 to block using
the Windows NetMeeting. To run the NetMeeting when Windows Firewall is turned
on, you have to configure Windows Firewall to add
conf.exe and mnmsrvc.exe on the
Exceptions tab of Windows Firewall.
Creating Network Connection problem after installing XP SP1
Symptom: After installed SP1 for Windows XP,
you may experience some difficulties:
1) You cannot create a VPN or Dial-Up. These items on the "Network Connection"
page of the New Connection Wizard are grayed out.
2) When trying to start the Remote Access Connection Manager service, you
receive "Error 5: Access is denied" or Event ID: 7023 in Event Viewer.
3) The Network Connections folder is empty.
4) ICS and ICF services do not start because of a dependency failure.
Resolution: to resolve this problem, try to
reinstall SP1 first. If you cannot reinstall SP1 or it does not work, start
Registry Editor, and then edit registry based on MS Q329441.
SYMPTOMS:
1) After installed SP1 for XP and then use the System Restore feature to
restore Windows to a state before the installation of the service pack.
2) After upgraded your computer to XP Pro from Win98, ME and XP Home. You may
experience the following symptoms: a) The Connect using
a dial-up modem or VPN option in the New Connection Wizard is
unavailable (gray out). b) The Network Connections folder is empty. c) ICS and
ICF services do not start because of a dependency failure. d) In the Event
Viewer, you may get Event ID: 7023, Event ID: 20035 or error 5 with Access is
denied, Remote Access Connection Manager failed to start because it could not
create buffers or Could not start the Remote Access Connection Manager service
on Local Computer.
Resolution: 1) To resolve this problem, reinstall
SP1 for Windows XP. 2) Delete the NextID value HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Telephony\Cards\NextID,
and then restart the computer. 3) Delete the Telephony key
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Telephony.
For
the consultants, check vpn connection is gray out page.
SYMPTOMS: when copying a large file over the
network in XP with SP1 and the source file is located on a Win2K, you may
receive one of the following error messages: 1) File or network path no
longer exists or 2) No network provider accepted the given network path.
These error messages are a network-related Server Message Block (SMB) packet
issue that may occur if SMB signing is enabled on the source W2K computer.
RESOLUTION: you need to download the fixing from
MS. Please refer to MS Q329170 .
Cause: SP2 disables the Messenger.
Symptoms: 1. Cannot install SP2. 2. Computer
does not boot after SP2 installation. 3. Computer does not work properly 4.
Hangs after reboot.
Causes: 1. Registry Security settings.
2. Conflict with other software.
3. Hardware issue.
Slower Problems
after installing XP SP1 (Re: MS Q331519)
After you install Windows XP SP1 with the SMB signing, you may see a
variety of errors relating to Windows XP SP1 client computers. These errors
may include, but are not limited to the following errors:
- When you open Microsoft Office files, they are opened as read-only (you
have to click Save As to save a file).
- You cannot copy files.
- The file or the network path no longer exists.
- Network paths are not accepted by any network provider.
- The following event ID messages are logged after you apply Group Policy
objects (GPOs)
Refer to MS Q331519 for resolution.
XP SP 2 may conflict with other software
1. Anti-virus software.
2. Display driver.
3. Spyware
4. XP-AntiSpy.
/td>
|
|
