1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Stupid mistake Spoofing my mac address. I have no internet now. Please Help!

Discussion in 'Windows - General discussion' started by FREELOWDR, Dec 1, 2008.

  1. FREELOWDR

    FREELOWDR Member

    Joined:
    Jan 4, 2006
    Messages:
    69
    Likes Received:
    0
    Trophy Points:
    16
    Hi All and thanks for reading.

    I had some trouble connecting to hotspot shield and decided to look for some help online. I have connected b4 without a problem a couple months ago and wanted to use it again today, but was encountering a daemon error according to the program.

    On one site I come across it said that spoofing your mac address could be a workaround and after downloading mac makeup that is exactly what I did. Now comes the problem.

    After switching the mac address on my wired lan adapter successfully I noticed the problem wasn't solved so I switched it back to normal. After restarting my computer the first problem I encountered was that windows claimed it needed to confirm it's validity due to my system not meeting it's origional specification. I had hoped that maybe a system restore would fix this issue but it did not.

    After confirming it's validity manually I was back in windows and found that my internet was not working at all. After checking my firewall, my ip and my mac address it still wasn't working. I restarted my computer and my router and it's still not working. I have even tried a different network adapter and reinstalled my origional one and still the problem remains. My other computers connect fine on the network. I have no kind of protection against spoofing which could have blocked me by accident.

    I am at my wits end which means I've had to turn to you good people for help.

    If there is any kind of troubleshooting I have missed please let me know. I am about to perform a reinstall if worse comes to worst.

    I have Windows XP SP 2

    Nforce networking controller with static IP
     
  2. tripplite

    tripplite Guest

    your connected through wired Ethernet right? good then it isn't some gay wep/wpa thingy...

    if you changed your NIC then a messed card from a botched mac spoof isn't causing your problems as long as you haven't spoofed this NIC,

    you said you had a static ip?
    check to make sure your computer isn't trying to connect to your network with an existing IP address that has already been leased, windows gives a false message sometimes saying its connected when it isn'tt...change back to a dynamic IP and reboot, see if it connects then, also go to your network settings and make sure you network gateway and other properties are the same as on other computers that are connected to your network (except the Ip of course)

    OH DO PLEASE! check your router and make sure it hasn't got some mac filtering that blocked your system after you spoofed your mac, when you set it up (with the CD my gawd!) it may have given you a option to enable some strict security options and what not....maybe gave you directions on how add a system to the network with the filtering...



    best of luck
    -tripplite



    ...please explain the situation better to...
     
  3. FREELOWDR

    FREELOWDR Member

    Joined:
    Jan 4, 2006
    Messages:
    69
    Likes Received:
    0
    Trophy Points:
    16
    Thank You, tripplite.

    I was actually on a couple of days ago trying to post that I solved this problem. There seemed to be a problem with afterdawn and it wouldn't post. Now I can finally add how i fixed it and I'm sorry to have wasted your time.

    It turned out to be an issue with AVG firewall, I think it was on the fritz bigtime. I ran a winsock fix as an extra since I was gonna reinstall my antivirus anyway at that point just to be sure. After reinstalling the firewall all was well again.

    Thanks again as all of your suggestions are on point and I had checked everything you mentioned by the time I got it working. take care
     
  4. tripplite

    tripplite Guest

    thanks for responding how you fixed it, that's excellent for reference if someone google searches a similar issue:D

    now they have a solution!!

    -tripplite

     
  5. LDee

    LDee Regular member

    Joined:
    Jun 29, 2005
    Messages:
    496
    Likes Received:
    0
    Trophy Points:
    26
    I think this could have possibly been something to do with your tcp/ip network stack (or registry entries relating to) being blocked from being altered by your firewall when you spoofed your mac address, therefore no movement from mac address (physical layer) to ip possible, hence no networking.

    When you say windows needed to confirm it's validity did the sfc kick in or something to do with wga?
     
  6. FREELOWDR

    FREELOWDR Member

    Joined:
    Jan 4, 2006
    Messages:
    69
    Likes Received:
    0
    Trophy Points:
    16
    That is a good question, LDee?

    I would say your more knowledgable on this issue, but I'll throw in my opinion if it's worth anything.

    From what I've read SFC needs to be run manually so it running automatically seems doubtful, even after the system restore.

    I would say WGA kicked in, though I fail to see why it would, even though it reported that it was due to system changes. I don't see how a change of mac address would produce this kind of result considering it isn't any more significant than the changing of a network card in my opinion. It's not like I changed out the mobo in which case I may have understood.

    It would be great if you could explain why it did this.

    Thanks for the response.
     
  7. LDee

    LDee Regular member

    Joined:
    Jun 29, 2005
    Messages:
    496
    Likes Received:
    0
    Trophy Points:
    26
    As far as my memory serves me, but I might be wrong, sfc /scannow can kick in and ask you if you want to run it on certain occasions. But no it wouldn't run automatically in the background as far as I know.

    I still think your firewall stopped registry entires being changed which left your nic unusable with its new mac (and then perhaps a system file pertaining to this is also altered by that program you used and then sfc detected it?).
     

Share This Page