- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Microsoft
- >
- Changing MAC address caused Windows to need to rea...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
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
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- 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
тАО10-06-2004 01:43 AM
тАО10-06-2004 01:43 AM
Changing MAC address caused Windows to need to reactivate itself
After rebooting with the new MAC address windows came back with a popup message that said the hardware had changed severly since Windows was activated and I needed to reactivate Windows. When I put in my coporate liscense for Windows XP, it didn't take. Any suggestions on how to get past this.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-06-2004 03:08 AM
тАО10-06-2004 03:08 AM
Re: Changing MAC address caused Windows to need to reactivate itself
Are you referring to the IP address? in any case you can unplug the network when the server is coming up change it to the right ip and plug it back in which will not cause any duplicate IP on the network.
Rgds
Gopi
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-06-2004 04:00 AM
тАО10-06-2004 04:00 AM
Re: Changing MAC address caused Windows to need to reactivate itself
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-07-2004 12:03 AM
тАО10-07-2004 12:03 AM
Re: Changing MAC address caused Windows to need to reactivate itself
I cant image, that the MAC address is somewhere stored within windows. The MAC address is an unique ethernet hardware address that is stored within your NIC!
In general I would never, ever enter a MAC address in the MAC address field of the NIC driver, because you can never be sure, that nobody within your segment does have the same.
Using ipconfig should work to determine the MAC address. If it is the case the Windwos caches the MAC address after the clone. I would remove the NIC using the device manager and have it windows find again.
Regards,
Dietmar
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-07-2004 12:12 AM
тАО10-07-2004 12:12 AM
Re: Changing MAC address caused Windows to need to reactivate itself
The NIC cards we are using are built on NICs of a ASUS P4S533-MX motherboard. We found out that the factory drivers for this NIC card have a static MAC address that it assigns to the computer. In order to fix this we had to update the driver to the latest version. At this point the NIC card then used its own unique MAC address, and was able to get a different IP Address.