HPE GreenLake Administration
- Community Home
- >
- Networking
- >
- Legacy
- >
- Communications and Wireless
- >
- VMI Namespace
Communications and Wireless
1830735
Members
1842
Online
110015
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-23-2004 11:19 PM
05-23-2004 11:19 PM
VMI Namespace
I've got an NC8000 with the internal, (HP), WLAN adapter. I use the computer to connect by CAT5 at work and the WLAN to connect to my router at home. Everything has been working very well until about 5 days ago. Now when I reboot my laptop I get a "VMI Namespace could not start" error message.
I can reinitiate the Atheros client manually three or four times and get it started but I get the same VMI Namespace error message the first two or three times I restart Atheros.
This started immediately after I'd upgraded from MS Office 2K Pro to MS Office 2003 Pro. I don't know whether there is any connection between the two but would welcome comments/suggestions. Thanks in advance. Dave
I can reinitiate the Atheros client manually three or four times and get it started but I get the same VMI Namespace error message the first two or three times I restart Atheros.
This started immediately after I'd upgraded from MS Office 2K Pro to MS Office 2003 Pro. I don't know whether there is any connection between the two but would welcome comments/suggestions. Thanks in advance. Dave
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP