|How to Implement Personal Configuration roaming in a domain
Q: the company has a local area network, the server side is Windows 2000 Server Client is Windows 2000 Professional, and a computer sharing zone is built. That is, No matter on which computer you use your account, you can obtain your previous configuration. USER environment, such as desktop, my documents, etc. C: all configurations under/Documents and Settings/% username %. After a user is enabled with a roaming user configuration file, the above functions can be implemented on some computers. But on some computers, all the required files are roaming (except C: /Documents and Settings/% username %/Local Settings/Application Data/personal folder in Microsoft/Outlook *. pst. I have previously set up a Server Policy Editor. Do I know if it is related to this ﹖
A: To solve this problem, you need to use the "Folder Redirection" function in the Group Policy of Windows 2000 Server.
Assume that the Windows 2000 Server domain name is msft.com and the computer name is w2kser. Create a directory such as public in the NTFS partition and set the sharing name to public. The folder permission and sharing permission are fully controlled by the Everyone user group.
Go to "Active Directory users and computers", right-click the domain name msft.com, select "properties" from the menu that appears, click the "Group Policy" tab, and select "default domain policy ", click "edit" and click "user configuration> Windows Settings> Folder Redirection ". You can see four options. Right-click Application Data, select "properties" from the menu that appears, and select "Basic" from the right of "Settings, redirect everyone's folders to the same location, and enter // folder in the target folder location. Click OK.
Then, redirect "desktop" to // w2kser.msft.com/public/?username=/topics top,“my documents "to // users.
You can also create an ou in msft.com, for example, your organization name, move all users in the enterprise to the new ou, and then create and edit group policies in the new ou.
Windows 98 machine cannot renew domain
Q: Local Area Network machines coexist in Windows 98, Windows 2000, Windows XP, and other operating systems. The domain is ztyb.com. A Windows 98 computer automatically logs on to the machine every time it is started, but instead of logging on to the domain, it logs on to the local machine. How can this problem be solved?
A: Right-click "Network Neighbor" on the desktop and select "attribute" from the menu that appears (or double-click "network" from "Control Panel ), double-click "Microsoft network user", select "log on to Windows NT domain" from the displayed Properties dialog box, and enter ztyb.com under "Windows NT domain, click OK to return to the Network Properties dialog box. Select "Microsoft network user" from the list under "primary network login", click "OK", and restart Windows 98 as prompted.
The system prompts "Security Operation" when adding the domain"
Q: I have created a Windows 2000 Domain Server, but when the client is added to the domain, it sometimes prompts "Domain running in security operation status ". What is the problem?
A: When you join a Windows 2000 domain, you should enter the NetBIOS Name of the domain (for example, if your domain name is msft.com, you should enter MSFT) instead of the full name of the domain, most of this problem occurs when the Windows XP Client is added to the Windows 2000 Domain. This problem is usually not found when Windows 2000 is added to the Windows 2000 domain.
Nic error at startup
Q: The following information will always appear on my computer:
Intel undipxe-build 082
Copyright c 1997-200 Intel Corporation
For RealTek rtl8139a/B/C/rtl8130 PCI Fast Ethernet controller
Client Mac addr00 E0 4C B3 32 FC GUIDFFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFFFFFF
PXE-E51NO DHCP or proxydhcp offers were received ed
PXE-MOFEXITING PXE Rom.
What is going on?
A: This is because your Nic has enabled boot ROM chip Boot, And the NIC has a PXE boot chip. It can be solved as follows:
① If the NIC is integrated on the motherboard or the boot program on the internet is written into the bios, you can modify the boot sequence of the system from the BIOS settings, such as setting the hard disk to boot first, or, disable the NIC from starting the system from the BIOS.
② If the NIC is not integrated, You can unplug the boot chip on the NIC or use the NIC setup program to disable the bootrom boot function of the NIC. After the NIC is started, when press Shift-F10 configure... appears ......" Immediately press SHIFT + F10 to enter the menu, set boot order Rom to disable from row 4th, and press F4 to save and exit.
Shared Internet access cannot browse webpages
Q: After using Windows XP as a proxy server, I found that other computers in the LAN could not browse the webpage. However, if there is data flow, I can also use QQ or other software, and machines in the network could also access each other.
The proxy server is a dual nic. in the Network Configuration Wizard, set it to "other computers in the network access the Internet through the Local Computer" (connect to the LAN through a NIC ), in the shared property, set it to "B connection shared to the network" (that is, 2nd, B Nic ). The client is set to "access the Internet through another computer in the network". The operating system has Windows 98/2000/XP and is connected through a switch. The indicator lights on the proxy server are working properly (A, B, and broadband modem connections), but the indicator lights on the client occasionally. When you open a webpage, you can see the "opening the *** webpage" in the status bar, but you cannot see the webpage for a long time. The prompt "the webpage cannot be displayed" is displayed.
A: there may be a problem with your network connection and DNS settings:
① Establish a cascade line and connect network card a directly to the broadband ADSL.
② Set the IP addresses of other clients to 192.168.0.2, 192.168.0.3, 192.168.0.4 ......, Set the subnet mask to 255.255.255.0, set the gateway address of each client to 192.168.0.1, and set DNS to your ISP's DNS address.
At the same time, you can also consider whether there is a conflict between the NIC of the proxy server, change the PCI slot, remove unnecessary peripherals, and so on.