Jump to content

Geezer

Members
  • Posts

    3
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Geezer's Achievements

Newbie

Newbie (1/14)

  1. Mr Protocol Windows XP doesn't allow you to change "Network Address" or "Hardware Address" so I attempted to edit the registry directly using the "regedt32" command. What I found was that SMAC had already changed the original MAC to a spoofed address but something, probably the Intel driver, was keeping it from going active. Thanks Anyway, Geezer
  2. I have a problem with SMAC 2.0 which I believe I can trace to my wireless driver. I'm looking for alternative suggestions to my current plan. I have been running SMAC successfully for about a year on a Windows XP Media Center Edition(SP3) OS with an Intel Pro/Wireless 3945 ABG network connector. I didn't use the program at all in Dec. 2010 and when I went to use it in Jan. 2011 the spoofed MAC address refused to go active. I first tried to deal with the problem by uninstalling or disabling any potentially conflicting wireless programs to ensure Windows was in control and then removed my security programs up to and including Norton 360. No Effect. After thinking about it, I decided that the only changes to my computer over that time period would have been daily security updates from Norton and a Microsoft and Intel update which included a newer wireless driver. I then tried to rollback my driver which had no effect because for some reason my OS did not save the previous driver as is usual. I then tried to manually spoof the MAC address by editing the Windows registry entry only to find that SMAC is sending the spoofed address to the registry, it's just not going active. I emailed KLC Consulting, the creators of SMAC, but only got the standard operators manual crap about not using certain characters in certain octets and then finally agreement that the driver is probably responsible. I then posed this question to the Intel wireless support community, many of whom have viewed the question, but no answers so far. Before I spend a couple of days backing up files and then rebuilding my operating system from the original diskettes and updating everything except the wireless driver, I thought I should present the problem to a community with more experience with MAC spoofing. Can you see a possible alternative problem or a better course of action. Any thoughts would be appreciated by this less experienced "old guy". Geezer
×
×
  • Create New...