The following image is an example of an RPC error. Though i've asked him to double check so lets see how that goes.You might encounter an RPC server unavailable error when connecting to Windows Management Instrumentation (WMI), SQL Server, during a remote connection, or for some Microsoft Management Console (MMC) snap-ins. I've asked the networking guy to do that (I have no access to that side of things) and he originally said it couldn't be them. Some people suggested looking into the IP-Helpers. It almost sounds like a local issue, but we've had so many different machines, i can't find any commonality between then other then they are in the same building. Our old machine was originally a 2003 R2 machine that the owners had us upgrade to 2008 R2 (it was our print server till very recently), then we realized we no longer needed it and shut it down after disabling the DHCP (not, uninstall the role, the main Sysadmin wanted to just disable the services so if there where any issues we could turn everything back on.
Our DHCP servers are now server 2008 R2, our clients are all Windows 7 pro machines. I posted here on SpiceWorks but due to projects i couldn't get back to it to nearly a week. This has happened on machines on multiple networks, multiple types of machines (HP, Dell, Toshiba, etc). With Wireshark we found that the local machines are sending the Discovery packet, and getting the Offer packet, but the local machines are not sending out the Request packet, thus the ACK packet never occurs.
The machines are refusing to take a DHCP IP after a reboot unless we set a static then take it off. Lately we are having a bizarre issue with our DHCP. Since this is causing some weird issues that seem to continue i'm trying elsewhere as well. I posted this on r/networking but kinda got mixed results, from people telling me to go elsewhere to a few people helping me out.
0 kommentar(er)
