Can ping through the printer, there is no way to print

You can ping the printer's computer, but you cannot access the printer's sharing settings. The following error occurred after \\XXX.XXX.XXX.XXX:

You may not have permission to use network resources. Please contact the administrator of this server to find out if you have access rights.
There is currently no logon server available to process requests.

Get a half-day, the original is because, I use the machine is automatically obtained IP and DNS, the printer connected to the computer with the manual set of IP and DNS;

This creates a phenomenon where the locally acquired DNS is a domain name, and the computer that the printer connects to is configured with a DNS IP, which of course cannot be accessed. Later, the printer also automatically obtains the IP to solve the problem.

But unfortunately, the first search is the following workaround:

Logon failure: The user is not granted the requested logon type on this computer. cannot be accessed. You may not have permission to use network resources. Please contact the administrator of this server to find out if you have access rights.

If the "XXX computer cannot be accessed, you may not have permission to use network resources." Please contact the administrator of this server to find out if you have access rights "error, this may be the computer's security settings have been changed, causing the target computer cannot be accessed. You can take the following steps to resolve:

1. Cancel simple file sharing.

Open My computer, and on the menu, choose Tools, Folder Options, view, and clear the option to use Simple File sharing (recommended).

2. Enable the Guest account.

Right click on "My Computer", select "Manage", select "Local Users and Groups", "User", right click on the guest user, select "Properties", clear "account is deactivated" selection.

3. Set the security policy in Group Policy.

Start-run--gpedit.msc--Computer Configuration--windows Settings-security Settings-Local policy-"User Rights Assignment", double-click on the right "access this computer from the network" to ensure that there is everyone, double-click on the left "deny access to this computer from the network", Ensure that it is empty.

4. Select "Local Policies", "security options" on the left,

A. Confirm that the "Network access: local account sharing and security mode" on the right is "classic";

B. Confirm that the "Microsoft Network client: Enable digital signature for communications (always)" to "disabled" on the right;

C. Confirm that the "Microsoft Network client: Enable digital signature for communications (if allowed by the server)" is enabled on the right;

D. Confirm that the "Microsoft Network server: Enable digital signature for communication (always)" to "disabled" on the right;

E. Confirm that the right "Microsoft Network server: Enable digital signatures for communications (if allowed by the server)" is enabled.

5. Configure the network firewall correctly

1> Many machines have installed a network firewall, it is not properly set up, also caused users to not access the shared resources of the unit, the local shared resources need to open the NetBIOS port. I take Skynet firewall as an example, in the "Custom IP Rules" window, select the "Allow local area network machine to use my shared resources" rule, and finally click the "Save" button, so that the NetBIOS port is open.

2> shut down Windows comes with a firewall.

6. Set User access Permissions reasonably

Many machines in the network use the NTFS file system, its ACL function (access control list) can control the user's access rights, the user to access the shared resources of these machines, must be given the appropriate permissions to the line. If you use the Guest account to access the CPCW shared folder of the machine, right click on the shared directory, select "Properties", switch to the "Security" tab, then add the Guest account to the list of users, and then specify the guest access rights, at least to give "read" and "List Folder Directory" permissions. If you want multiple user accounts to be able to access the shared directory, simply add the Eeryone account and give the Read and list folders?..

7, network protocol configuration problems,

A, installation and setup of network protocol

1. Installing the NetBEUI protocol in WinXP

Right, you have not read wrong, is to install the NetBEUI protocol in WinXP. Microsoft only supports the TCP/IP protocol and the NWLink Ipx/spx/netbios compatibility protocol in WinXP and officially declares that NetBEUI protocol is no longer supported. However, in the actual use of the establishment of small LAN, the use of the two Microsoft-supported protocols is not satisfactory. For example, in the process of solving the slow problem of the Network Neighborhood, the author adopted a number of methods, although the speed of the Network Neighborhood is better, but still slow as a snail; In addition, when setting up the protocol, customer and service bindings for multiple NICs, there are still bugs in the two protocols, and multiple NICs must bind all the protocols simultaneously (except NWLink NetBIOS), customers and services, even if you cancel certain bindings after rebooting the system will automatically add, which obviously does not well meet the actual needs of network construction. And when the author installs the NetBEUI agreement in the WinXP, the above two questions all get the consummation solution.

There are 3 files in the "\\valueADD\\MSFT\\NET\\NETBEUI" Directory of the WinXP installation CD, where "NETBEUI. TXT "is the installation instructions, and the other two are the files required to install the NetBEUI protocol. The steps to install are as follows:

Copy the NBF. SYS "to"%systemroot%\\system32\\drivers\\ "directory;

Copy the NETNBF. INF "to"%systemroot%\\inf\\ "directory;

Click the Install button in the network connection properties to install the NetBEUI protocol.

Note:%systemroot% is the WinXP installation directory, such as the author's WinXP installed in the F:\\windows directory, you should use F:\\windows to replace%systemroot%.

2. Set up other network protocols in WinXP

It is recommended that you only need to install the NetBEUI protocol if your LAN is not on the Internet. In small LANs (networks with 200 or so computers), the NetBEUI is the least-memory, fastest-running protocol, and the NWLink Ipx/spx/netbios compatibility protocol should be removed.

If your local area network is on the Internet, you must install the TCP/IP protocol. However, for fast network access, it is recommended to specify the IP address of each workstation (unless there is a DHCP server in the network), or the workstation will always look for a DHCP server to slow down the Internet.

Of course, if the network is only installed TCP/IP protocol can also realize the exchange of local area network, but it is difficult to see the other machines in the net neighborhood, must first search for a machine to access it, which in many practical network use is very inconvenient.

3. Settings for other Windows computer network protocols

Careful users may have discovered that there is a "set up home or small office network" wizard in WinXP's Network Neighborhood, which makes it easy to set up LAN sharing, Internet connectivity, and small LAN. The wizard also provides a network installation floppy for other Windows computers that connect to WinXP.

However, I do not advocate the use of this network installation floppy disk. On other Windows computers that connect to WinXP, just install the NetBEUI protocol and set up the network logo; To connect to the Internet, simply install the TCP/IP protocol and specify a good one. This is exactly the same as the traditional LAN setup, and it is recommended to use less ipx/spx compatible protocols.

B. Completely disable WinXP's scheduled Tasks

When browsing My Network Places in WinXP and Win2000, the system is delayed by default by 30 seconds, and Windows will use this time to find out if the remote computer has the specified scheduled task (and possibly even search the Internet). If there is no response to the network when searching for the infinite waiting, then more than 10 minutes of delay or even error is not surprising. The following are the specific workarounds.

1. Switch off WinXP's scheduled task Service (Task Scheduler)

You can open the Properties dialog box for Task Scheduler in the Control Panel/Administrative Tools/Services, click the Stop button to stop the service, and then set the startup type to manual so that the service does not start automatically the next time you start it.

2. Delete Two subkeys in the registry

Locate the primary key in the registry

Hklm\\software\\microsoft\\windows\\currentversion\\explorer\\remotecomputer\\ NameSpace "

Delete the following two subkeys

{2227a280-3aea-1069-a2de-08002b30309d}

{D6277990-4C6A-11CF-87-00AA0060F5BF}

The first Zijian determines whether the network neighbor is searching for printers on the Internet (or even searching the Internet), which can be deleted if there is no shared printer on the web. The second Zijian determines whether the specified scheduled task needs to be found, which is a slow culprit for the network Neighborhood and must be deleted.

This question depressed me all morning,

At home three, a can be accessed by B, but a can not access b,c is normal, that is, access can also be accessed.

The afternoon finally found a solution,

1. In the run, enter Gpedit.msc to run Group Policy. In the Computer Configuration/windows Settings/security Settings/Local Policies/security options, locate network access-local account sharing and security mode-Select Classic.

2. Computer Configuration/windows Settings/security Settings/Local Policies/user rights Assignment, guests will be removed from the network access this computer, of course you first want to enable guests

3. Ensure that the computer is in the same workgroup

After the Xppro version has been SP2, access from 2000 found that a request logon type issue was not granted to the user on this computer.

You can't log in with administrator. Help says you need to set up a local security policy, as follows:

1. Open the Local Policy management interface (open from the Administrative Tools interface).

2. In the user rights assignment, local policies, find the following modifications:

Access this computer from the network, and then add the users or groups that can access this computer.

3. In the security options, local policies, locate the following modification:

"Network access: Sharing and security mode for local accounts", modified to Classic mode.

(1) Always show error "Unauthorized user request login type on this computer" (login win2000\winxp\win2003)

Error "no permission to access resource" (Win98 by Login)

Cause: The guest is prevented from logging on from the network in user rights in the policy, and the error mentioned in (2).

(Note: XP default, Win2003 not default)

Workaround: Configure the Local Security policy: \ Security Settings \ Local Policies \ User Rights Assignment \ Deny access from the network

Computer ", delete the guest and save it.

The computer is inaccessible and you may not have permission to use network resources. Please contact the administrator of this server

(1) Install NWLink Ipx/spx/netbios Compatible Transport Protocol protocol.

(2) to open the Guest account: Right-click on my Computer \ Admin \ user has a guest, double-click to remove the "account has been deactivated" before the tick.

(3) Right-click My Computer \ properties \ computer name to view the LAN workgroup name that appears in this tab

(4) Exceptions to using the WinXP Firewall: The WinXP Firewall is fully enabled by default, which means that all networks running the computer

Network connections, it is difficult to achieve online neighborhood sharing. Also, because Windows Firewall is disabled by default, "file-to-Printer sharing"

, so, the firewall is enabled, often cannot share printing, the solution is: go to the "Local connection" window, point "advanced" \ "settings

"\" Exceptions \ Check "File and Printer Sharing" under Programs and services.

(5) Remove the Guest account in the "Deny access to this computer from the network" entry: Run Group Policy (gpedit.msc) \ Local computer \

Computer Configuration \ Windows Settings \ Security Settings \ Local Policies \ User Rights Assignment \ Deny access to this computer from the network. If there is Gu

EST, it is deleted. (The reason is: sometimes XP guest is not allowed to access the shared)

(6) Cancel the "Use Simple File Sharing" method: Explorer \ tools \ folder Options \ View \ Remove "Using Simple File Sharing (push

(recommended) "in front of the hook.

(7) The Working Group has the same name.

(8) Tick "File and printer Sharing for Microsoft Network".

(9) Run the service policy "services.msc". Start the "Clipbook Server" (Folder Server): This service allows

Other users on your network see your folders. Of course sometimes you can change it to start manually, and then use another program on your web

Information posted on the network.

Win98 computer cannot access WIN2000/WINXP computer because: Guest user in WIN2000/WINXP's computer

Disabled or WIN2000/WINXP in NTFS partition format with permission control set. Generally to allow Win98 access, win2000/

Do not delete the Everyone account group in the security control in WinXP.

Note: A, if you are not joined to a domain and want to view the Security tab, the settings Display the Security tab: Explorer \ Tools \

Folder Options \ View \ Remove the tick in front of "Use Simple File Sharing (recommended)". B. To view effective permissions for files and folders:

Source Manager \ Right-click the file or folder for which you want to view effective permissions \ properties \ Click the Security tab \ Advanced \ Effective permissions \

Select \ Type the name of the user or group in the Name box, and then click OK. A selected check box indicates that the user or group

Valid permissions for the item or folder. C. Set permissions only on drives formatted to use NTFS.

(11) To solve the network neighborhood is too slow method: Win98, assume that there is no Novell network, can be removed in order to be compatible with Novell NetWare

The Ipx/spx compatible protocol can be installed on the network, WIN2000/XP can delete the system drive letter \documents and

setting\ all files under the user name \nethood folder.

Can ping through the printer, there is no way to print