WiSM and WCS Issues

Unanswered Question
Jun 29th, 2007

1. WiSM code 4.1.171. When a user login using a wrong password and failed, WiSM still counts it as a login session. So when the same user try to login from another computer, he may get the error about too many login sessions. I think if the login fails, the WiSM should not count it as a login session.

2. Just upgraded to WCS 4.1.83 on Windows 2003 server. Once log out from the console, the WCS stops. Anyone sees this problem?


I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4.5 (2 ratings)

RE #2. In case you haven't figured this one out yet, it's a bug. Seems WCS gets started as an app instead of service regardless of config. You'll sometime notice when you exit the console (or term svc console) that you briefly see a black dos box screen & then it closes. Then wcs is no longer running. Fixed in later versions supposedly.


This Discussion



Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode