But this is the Business Version not the Smart Security with firewall and spamfilter. So no Firewall is active - Not really true, because the Windows Firewall is active, but knows that the network is a Domain network and not a Private or Public network. And I deactivated the firewall for Domain networks. Even if I Allow every rule for Domain inbound it is not working. Also SP1 is not applied yet. I walked through the articles and commands from this post.
I do not see what a re-joining will solve, but i will try it. I am not onsite now. I will test it on wednesday next week.
I'm not sure why, but for a few people I've helped out, removing and rejoining a relatively new machine has solved the WMI connection problem after many of the typical WMI connection resolutions were tried. Ok, problem found! Windows 7 was not the problem. Our spiceworks server is in a different ip segment then these Windows 7 computers. I added a static route on the Win7 pc's to the gateway Cisco device between the IP segments.
Now the machines are read correctly by Spiceworks. I am having the same problem on my network with newly installed Windows 7 machines. I have done all the troubleshooting steps mentioned in this thread. The machines are on the same subnet, so routing should not be an issue. We even turned off our gateway to further isolate the subnet. Curt - One of the first things to check is that these x64 computers are responding to the Spiceworks ping and that nslookup returns the correct information.
If these don't work, Spiceworks will not be able to locate and identify those devices. How are your scan ranges set up? Are there any scan exceptions that could be causing Spiceworks to ignore some of those computers? Did you also test the ping and nslookup with the same account credentials that are used for the Spiceworks scan? The unseen Windows 7 machines are part of a standard scan range using the same credentials I am using to ping and run nslookup.
I also setup scans for the individual IP addresses that are assigned to the computers on which I am experimenting so I do not need to scan the entire range each time I change a setting.
I am also running the following command from the Spiceworks machine to see if the WMI is working correctly:. The response from a Windows 7 machine seen by Spiceworks is the serial number.
From the unseen machines it is the following:. I have also used dcomcnfg to confirm the correct setup of DCOM. If this is a workgroup computer, there may be some extra configuration required. When you can specify a dedicated server port, you know what traffic flows between the hosts across the firewall, and you can define what traffic is allowed in a more directed manner.
As a server port, please choose a port outside of the range you may want to specify below. You can find a comprehensive list of server ports that are used in Windows and major Microsoft products in the article Service overview and network port requirements for Windows. The response has the server port number, and a subsequent RPC Bind on this port is then allowed to pass.
The RPC Port key values discussed below are all located in the following key in the registry:. In this example ports through inclusive have been arbitrarily selected to help illustrate how the new registry key can be configured. This is not a recommendation of a minimum number of ports needed for any particular system.
Restart the server. All applications that use RPC dynamic port allocation use ports through , inclusive. You should open up a range of ports above port Port numbers below may already be in use by other applications and could cause conflicts with your DCOM application s.
Furthermore, previous experience shows that a minimum of ports should be opened, because several system services rely on these RPC ports to communicate with each other. The minimum number of ports required may differ from computer to computer. Computers with higher traffic may run into a port exhaustion situation if the RPC dynamic ports are restricted. Take this into consideration when restricting the port range.
If there is an error in the port configuration or there are insufficient ports in the pool, the Endpoint Mapper Service will not be able to register RPC servers with dynamic endpoints. Add a comment. Active Oldest Votes. Open Windows Firewall.
Allow app or feature through Windows Firewall. There are some other things also that you can check. The remote computer is blocked by the firewall. Host name or IP address is wrong or the remote computer is shutdown.
Solution: Verify correct host name or IP address. Solution: Open services. The "Windows Management Instrumentation" service is not running on the remote computer. Verity that Windows Management Instrumentation service is running and set to auto start after restart. Improve this answer. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown.
0コメント