Contents Exit focus mode. Is this page helpful? Please rate your experience Yes No. Any additional feedback? Submit and view feedback for This product This page. View all page feedback. If the net view command returns the following error message or any other related error message, make sure that the correct IP addresses are listed in the LMHOSTS file:.
Typically, the Active Directory side of the trust configuration has security settings that cause connectivity problems. However, the security settings must be inspected on both sides of the trust.
In Windows Server and Windows Server , the security settings may be applied or configured by Group Policy, a local policy, or an applied security template.
You must use the correct tools to determine the current values of the security settings to avoid inaccurate readings.
After you determine the current settings, you must identify the policy that is applying the settings. For example, you must determine the Group Policy in the Active Directory, or the local settings that set the security policy. However, in Windows you must view the Group Policy and the local policy to determine the policy that contains the security settings:. The following three sections identify the operating system and list the security settings that you must verify for the operating system in the information that you've collected:.
After the settings are configured correctly, you must restart your computer. The security settings are not enforced until the computer is restarted. After the computer restarts, wait 10 minutes to make sure that all security policies are applied and the effective settings are configured. We recommend that you wait 10 minutes because Active Directory policy updates occur every 5 minutes on a domain controller, and the update may change the security setting values.
After 10 minutes, use Security Configuration and Analysis or another tool to examine the security settings in Windows and Windows Server This section, method, or task contains steps that tell you how to modify the registry.
However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base: How to back up and restore the registry in Windows.
You could also consider the setting "Deny log on through Terminal Services" located in the same location. Thanks for the reply, the issue is that I ran the gold disk against one of my workstations. One of the findings was that the support account and the guest group were not added to the UR - Deny Users access to this computer from the network. I added those accounts to my domain policy, however, it added those accounts as domain accounts, not the local workstation accounts.
I need to find away to add the local workstation accounts without having to go to each workstation, install GPMC, modify the policy on that workstation and add those local users that way. It would be too tedious and time consuming. Hi Rasczak. Does the wireless router not have network ports on them 4 or more? What router is this?
Why is it necessary to have the hub? Generally you can share the whole drive which I'd never do or create a folder and share it with Everyone Full Control rights, same thing on the Server. Thanks, I'll read those articles. I unchecked IPv6 but still can't see server. Ahh ok, I'll look up that router. Ohhh I know I forgot to tell you something. Note: I just reviewed your router and found that it has it own built in firewall, so disable firewalls on both the Windows 7 machine and the server and see what happens.
Edited by cdobbs Wednesday, January 13, AM added router info. By the way IF you're using the homegroup feature, then IPv6 needs to be enabled on the Windows 7 machine.
Hi, The above links are useful to troubleshoot the issue. Assure the following services are started on each machine: Computer Browser, Server, Workstation 2. Thanks, Novak. Friday, January 15, AM. Win7 can see the server but cannot access it getting 'No Network Path' error. The server can ping Win7 but Win7 cannot ping the server. Thanks again for all the support. Joe ps sorry for the caps.
Monday, January 18, AM. Hi, Since the Server can access Windows 7 machine successfully, we can eliminate the Windows 7 machine cause. This issue can occur by incorrect settings on Windows Server machine.
I suggest you temporarily turn off firewall and antivirus program on Windows Server , and then access it from Windows 7 machine again. If the issue persists, please access the Server machine on another machine for a test. Thank you for your reply. Link to the screenshot of what I get when I try to turn off the server firewall. Antivirus is disabled. Tuesday, January 19, AM. I am able to log onto server from a Vista Ultimate SP2 machine.
Thank you. Don't know why but now I can ping the server fom Win7. Install NetMon on the server?
0コメント