On Windows, We are installing HUM and DFM each on separate servers. On our LMS (Server-A) we updated from LMS 2.6 to 3.0 and then ran the DEC 2007 LMS update to get to LMS 3.01. Then we installed DFM on Server-B and also ran the DEC 2007 update on that. Now on Server-B in the Windows event viewer we see tons on Critical application alerts saying ..
Source Incharge EventID 16640 ... The following information is part of the event :HTTP#1 AUTH-E-EWRITESSTREAM - While check Feature was writing to d:\progra~1\objects\smarts\bin\sm_authority.exe encounted error : Bad file descriptor.
We did a custom install to put DFM on a d disk and we create the directory program files on the D directory before we did the DFM install. Could this be due to the fact that we didn't do a standard install into the C drive ?
Hi everyone, I would like to thank you in advance for any help you can provide a newcomer like myself!
Im studying the 100-105 book by Odom and am currently on the topic of Port security. I purchased a used 2960 and I'm trying to follow a...
While deploying a number of 18xx/2802/3802 model access points (APs), which run AP-COS as their operating platform. It can be observed on some occasions that while many of their access points were able to join the fabric WLC withou...
I am going to design and build an LAN network under a tunnel underground with long distance between the switches.
I will have 2 Catalyst switches and 8 Industrial IE3000, and they will be connected with fiber.
For now I am planning on use Layer-2 s...