Windows 7 Unidentified Network Terror Returns [Help meeeee]

Ninja Edit: Ive tried a multitude of things like deleting the 0.0.0.0 thing. Ive tried both netsh commands. Ive tried flushing DNS. I know the cable isnt the problem since I used a cable tester. I have no idea what to do.

Yea so I got this problem ._.
I got Windows 7 64-Bit.
I can provide a combofix log. Here is my CMD prompt... ipconfig /all


Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Simon>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : Simon-PC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : hsd1.fl.comcast.net.

Wireless LAN adapter Wireless Network Connection:

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) 82579V Gigabit Network Connectio
n
Physical Address. . . . . . . . . : 40-61-86-75-B9-E2
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::4dab:32c3:4707:47ab%12(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.71.171(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 272654726
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-79-A1-A7-40-61-86-75-B9-E2

DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled


C:\Users\Simon>
75 answers Last reply
More about windows unidentified network terror returns help meeeee
  1. It would appear that we have a similar issue.

    See my post here: Win 7 Home Premium 64 Bit - Cannot obtain automatic IP.
  2. Could both of you please press your Windows key and R together then into the Open box, type regedit and press Enter. Although I'm not asking you to change anything at this stage, it's good practice to make a backup of the Registry from the File>Export menu. Note the name and location of that backup file just in case.

    Next, navigate to H_KEY_LOCAL_MACHINE>SYSTEM>CurrentControlSet>services>Winsock>Parameters and take a note of the contents of that key. Close eth Registry editor from the File>Exit menu and post back those details.
  3. SharcBate1 said:
    Ninja Edit: 169.254.71.171(Preferred)


    That's a dud IP for starters. Set it according to the router's manual, so if the Default gateway is, say, for a Netgear, 192.168.0.1, set the IP address as 192.168.0.100 and the subnet will set itself.
  4. That's a dud IP for starters. Set it according to the router's manual, so if the Default gateway is, say, for a Netgear, 192.168.0.1, set the IP address as 192.168.0.100 and the subnet will set itself.

    Im sorry, what? Do you want me to set the ip address on my computer or the router?

    oh and here is what you asked for
  5. escribblings said:
    It would appear that we have a similar issue.

    See my post here: Win 7 Home Premium 64 Bit - Cannot obtain automatic IP.



    Dude, thats so funny, I looked at your post before I posted mine. Yeah, I tried all the things you tried. I downloaded combofix but it didnt solve any problems :/
  6. Right click that key and select Modify then add RFCOMM as one of the entries. It's best to use the Enter key to make a gap between your existing four and add the new one in that space. I do recommend making that possibly crucial Registry backup before doing this though. Restart the system afterwards and see if you can get online.

    That IP address change needs to be made in the computer, in the Properties of the network and under the IPV4 Properties.
  7. Right click which key? The transports one? I dont want to do anything by mistake xD. I made the backup by the way.
  8. Right click that key and select Modify then add RFCOMM as one of the entries. It's best to use the Enter key to make a gap between your existing four and add the new one in that space. I do recommend making that possibly crucial Registry backup before doing this though. Restart the system afterwards and see if you can get online.

    That IP address change needs to be made in the computer, in the Properties of the network and under the IPV4 Properties.



    Did everything. Still not working
  9. Could both of you please press your Windows key and R together then into the Open box, type regedit and press Enter. Although I'm not asking you to change anything at this stage, it's good practice to make a backup of the Registry from the File>Export menu. Note the name and location of that backup file just in case.

    Next, navigate to H_KEY_LOCAL_MACHINE>SYSTEM>CurrentControlSet>services>Winsock>Parameters and take a note of the contents of that key. Close eth Registry editor from the File>Exit menu and post back those details.



    I am away from work now, but I will try this tomorrow. Thank you.

    @SharcBate1 - good luck with yours.
  10. OK



    Right click that key and select Modify then add RFCOMM as one of the entries. It's best to use the Enter key to make a gap between your existing four and add the new one in that space. I do recommend making that possibly crucial Registry backup before doing this though. Restart the system afterwards and see if you can get online.

    ...


    Did not work I am afraid.

    I can connect if I hardwire my IP, but I want the DHCP to auto assign it. :(
  11. Is that a before or after screenshot? If it's after, I didn't make myself sufficiently clear. I should have said right click on Transports and click Modify then add RFCOMM. It's odd that a fixed internal IP works but DHCP doesn't. Is there another machine in the system that does work with a DHCP allocated address or could the router be handing out only fixed ones?
  12. After screen shot.

    If you re-read my thread[1] you will see that this machine is 1 of 4, all the others are still receiving their dynamic IP. I have limited rights to the router, but the MAC address of this troublesome machine is there as I reserved it and address when DHCP was working. But even before I tried your regedit I could get static working.

    Removing that reservation makes no difference to the situation. Strangely this machine also does not show up in "attached devices" even with a static IP.

    I am beginning to wonder if a port has been blocked somewhere.

    1 - Win 7 Home Premium 64 Bit - Cannot obtain automatic IP.
  13. SharcBate1 said:
    Ninja Edit: Ive tried a multitude of things like deleting the 0.0.0.0 thing. Ive tried both netsh commands. Ive tried flushing DNS. I know the cable isnt the problem since I used a cable tester. I have no idea what to do.

    Yea so I got this problem ._.
    I got Windows 7 64-Bit.
    I can provide a combofix log. Here is my CMD prompt... ipconfig /all


    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.

    C:\Users\Simon>ipconfig /all

    Windows IP Configuration

    Host Name . . . . . . . . . . . . : Simon-PC
    Primary Dns Suffix . . . . . . . :
    Node Type . . . . . . . . . . . . : Hybrid
    IP Routing Enabled. . . . . . . . : No
    WINS Proxy Enabled. . . . . . . . : No
    DNS Suffix Search List. . . . . . : hsd1.fl.comcast.net.

    Wireless LAN adapter Wireless Network Connection:

    Ethernet adapter Local Area Connection 2:

    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Intel(R) 82579V Gigabit Network Connectio
    n
    Physical Address. . . . . . . . . : 40-61-86-75-B9-E2
    DHCP Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes
    Link-local IPv6 Address . . . . . : fe80::4dab:32c3:4707:47ab%12(Preferred)
    Autoconfiguration IPv4 Address. . : 169.254.71.171(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.0.0
    Default Gateway . . . . . . . . . :
    DHCPv6 IAID . . . . . . . . . . . : 272654726
    DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-79-A1-A7-40-61-86-75-B9-E2

    DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
    fec0:0:0:ffff::2%1
    fec0:0:0:ffff::3%1
    NetBIOS over Tcpip. . . . . . . . : Enabled


    C:\Users\Simon>



    Had the same problem and tried everything, i fixded finaly. in wiareless adapter preferencec ----- configuration-------

    wireless mode ----- changed from auto to b/g. result no uidentified network a huray and internet available

    the problem comes with atheros ar9285
  14. Quote:
    Had the same problem and tried everything, i fixded finaly. in wiareless adapter preferencec ----- configuration-------

    wireless mode ----- changed from auto to b/g. result no uidentified network a huray and internet available

    the problem comes with atheros ar9285


    Its an unidentified network on an ethernet connection.
  15. Can you delete that connection completely and restart so it reconstitutes itself? It might just get it right this time.
  16. Mine us an atheros adapter - but not wireless.

    I will try un-installing and re-installing it when I go back in on Thursday. In the mean time I am happy to hear any other suggestions.


    Also, a question to SharcBate - have you tried configuring a static IP or are you just trying to get it to connect automatically?
  17. Diagnostika sítě Podrobnosti o vydavateli

    Nalezené problémy
    Problém s bezdrátovým adaptérem nebo přístupovým bodemProblém s bezdrátovým adaptérem nebo přístupovým bodem Opraveno
    Resetujte bezdrátový adaptér. Dokončeno
    Zkontrolujte, zda nedochází k potížím se směrovačem nebo přístupovým bodem Nespuštěno
    Další informace o problémech s bezdrátovým připojením naleznete v Nápovědě a podpoře systému Windows. Nespuštěno


    Nalezené problémy Podrobnosti o zjištění

    6 Problém s bezdrátovým adaptérem nebo přístupovým bodem Opraveno

    Resetujte bezdrátový adaptér. Dokončeno

    Protokol diagnostiky sítě
    Název souboru: 39D15246-B8EB-439F-92F6-C06DA16FE22F.Repair.1.etl


    Zkontrolujte, zda nedochází k potížím se směrovačem nebo přístupovým bodem Nespuštěno

    Jste-li připojeni k hotspotu nebo doménové síti, obraťte na správce sítě. V opačném případě: 1. Odpojte zařízení ze zásuvky nebo jej vypněte. 2. Jakmile zhasnou všechny kontrolky zařízení, počkejte alespoň 10 sekund. 3. Zapněte znovu zařízení nebo jej zapojte do zásuvky. Chcete-li restartovat směrovač nebo přístupový bod s integrovanou baterií, stiskněte a rychle uvolněte tlačítko Reset.
    Další informace o problémech s bezdrátovým připojením naleznete v Nápovědě a podpoře systému Windows. Nespuštěno

    Systém Windows nemůže vyřešit problém s bezdrátovým připojením.


    Podrobnosti o zjištění

    Diagnostické informace (Síťový Adaptér)
    Podrobnosti diagnostiky síťový adaptér:

    Informace o ovladači síťového adaptéru Wireless Network Connection:

    Popis . . . . . . . . . . : Atheros AR9285 Wireless Network Adapter
    Výrobce . . . . . . . . . : Atheros Communications Inc.
    Poskytovatel . . . . . . . . . . . : Microsoft
    Verze . . . . . . . . . . . : 2.0.0.74
    Název souboru INF . . . . . . . . . : C:\Windows\INF\netathr.inf
    Datum souboru INF . . . . . . . . . : Monday, July 13, 2009 8:46:26 PM
    Název oddílu . . . . . . . . . : ATHR_DEV_OS61_10891A3B.ndi
    ID hardwaru . . . . . . . . . . : pci\ven_168c&dev_002b&subsys_10891a3b
    Příznaky stavu instance . . . . . : 0x180200a
    Stavový kód správce zařízení . . : 0
    IfType . . . . . . . . . . . . : 71
    Typ fyzického média . . . . . . : 9



    Diagnostické informace (Bezdrátové Připojení)
    Podrobnosti diagnostiky bezdrátové připojení:

    Informace o diagnostikovaných připojeních
    Identifikátor GUID rozhraní: 52b051bb-db9c-4264-9ee3-343983591b56
    Název rozhraní: Atheros AR9285 Wireless Network Adapter
    Typ rozhraní: Nativní Wi-Fi

    Problém s připojením byl diagnostikován.
    ID automatické konfigurace: 1
    ID připojení: 1

    Souhrnný stav připojení
    Čas navázání připojení: 2013-01-09 13:42:51-349
    Shoda profilu: Úspěch
    Předběžné přidružení: Úspěch
    Přidružení: Úspěch
    Zabezpečení a ověřování: Úspěch

    Seznam viditelných přístupových bodů: Celkem položek: 1, zobrazeno položek: 1
    BSSID Síť PHY typu BSS Signál (dB) Kanál/frekvence SSID
    -------------------------------------------------------------------------
    80-B6-86-11-09-18 Infra <neznámý> -69 10 hamburger

    Historie připojení

    Informace pro automatickou konfiguraci, ID = 1

    Seznam viditelných sítí: Celkem položek: 1, zobrazeno položek: 1
    Síť PHY typu BSS Zabezpečení Signál (RSSI) Kompatibilní SSID
    ------------------------------------------------------------------------------
    Infra <neznámý> Ano 60 Ano hamburger

    Seznam upřednostňovaných sítí: Počet položek: 1
    Profil: hamburger
    SSID: hamburger
    Délka identifikátoru SSID: 9
    Režim připojení: Infra
    Zabezpečení: Ano
    Nastaveno zásadami skupiny: Ne
    Připojit se i v případě, že síť nevysílá: Ne
    Lze připojit: Ano

    Informace pro připojení, ID = 1
    Čas navázání připojení: 2013-01-09 13:42:51-349
    ID automatické konfigurace: 1
    Profil: hamburger
    SSID: hamburger
    Délka identifikátoru SSID: 9
    Režim připojení: Infra
    Zabezpečení: Ano
    Předběžné přidružení a přidružení
    Nastavení připojení poskytnuté výrobcem zařízení (nezávislým): Ne
    Nastavení zabezpečení poskytnuté výrobcem zařízení (nezávislým): Ne
    Profil splňuje požadavky sítě: Úspěch
    Stav předběžného přidružení: Úspěch
    Stav přidružení: Úspěšné
    Poslední přístupový bod (AP): 80-b6-86-11-09-18
    Zabezpečení a ověřování
    Nakonfigurovaný typ zabezpečení: WPA-PSK
    Nakonfigurovaný typ šifrování: CCMP(AES)
    Protokol 802.1X: Ne
    Výměna klíčů byla zahájena: Ano
    Přijaté klíče jednosměrného vysílání: Ano
    Přijatý klíč vícesměrového vysílání: Ano
    Počet přijatých paketů zabezpečení: 3
    Počet odeslaných paketů zabezpečení: 3
    Stav pokusu o zabezpečení: Úspěch
    Připojení
    Statistika paketů
    Ndis Rx: 45
    Ndis Tx: 160
    Úspěšné dešifrování jednosměrového vysílání: 45
    Úspěšné dešifrování vícesměrového vysílání: 0
    Chybné dešifrování jednosměrového vysílání: 0
    Chybné dešifrování vícesměrového vysílání: 0
    Úspěšně přijato: 45
    Chybně přijato: 56
    Úspěšně odesláno: 290
    Chybně odesláno: 0
    Opakování Tx: 5
    Vícenásobné opakování Tx: 1
    Překročena max. životnost Tx: 0
    Chybné potvrzení Tx: 66
    Historie roamingu: Počet položek: 0

    i dont know why but every time i made my wireless adpt. work after restart it didnt
    this works even after restart hope it help . i will send screens of my router setup.
  18. Microsoft Windows [Verze 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation. Vsechna práva vyhrazena.

    C:\Users\Petra>ipconfig /all

    Konfigurace protokolu IP systému Windows

    Název hostitele . . . . . . . . . : Skorm-PC
    Primární prípona DNS. . . . . . . :
    Typ uzlu . . . . . . . . . . . . : hybridní
    Povoleno smerování IP . . . . . . : Ne
    WINS Proxy povoleno . . . . . . . : Ne

    Adaptér síte Ethernet Local Area Connection:

    Stav média . . . . . . . . . . . : odpojeno
    Prípona DNS podle pripojení . . . :
    Popis . . . . . . . . . . . . . . : Atheros AR8131 PCI-E Gigabit Ethernet Con
    troller (NDIS 6.20)
    Fyzická Adresa. . . . . . . . . . : 48-5B-39-E7-09-3C
    Protokol DHCP povolen . . . . . . : Ano
    Automatická konfigurace povolena : Ano

    Adaptér bezdrátové síte LAN Wireless Network Connection:

    Prípona DNS podle pripojení . . . :
    Popis . . . . . . . . . . . . . . : Atheros AR9285 Wireless Network Adapter
    Fyzická Adresa. . . . . . . . . . : 1C-4B-D6-D5-EB-16
    Protokol DHCP povolen . . . . . . : Ano
    Automatická konfigurace povolena : Ano
    Adresa IPv4 . . . . . . . . . . . : 10.0.0.140(Preferované)
    Maska podsíte . . . . . . . . . . : 255.255.255.0
    Zapujceno . . . . . . . . . . . . : Wednesday, January 09, 2013 1:44:23 PM
    Zápujcka vyprsí . . . . . . . . . : Saturday, February 15, 2149 8:26:06 PM
    Vychozí brána . . . . . . . . . . : 10.0.0.138
    Server DHCP . . . . . . . . . . . : 10.0.0.138
    Servery DNS . . . . . . . . . . . : 10.0.0.138
    Rozhraní NetBios nad protokolem TCP/IP. . . . . . . . : Povoleno

    Adaptér pro tunelové pripojení isatap.{52B051BB-DB9C-4264-9EE3-343983591B56}:

    Stav média . . . . . . . . . . . : odpojeno
    Prípona DNS podle pripojení . . . :
    Popis . . . . . . . . . . . . . . : Microsoft ISATAP Adapter #2
    Fyzická Adresa. . . . . . . . . . : 00-00-00-00-00-00-00-E0
    Protokol DHCP povolen . . . . . . : Ne
    Automatická konfigurace povolena : Ano

    Adaptér pro tunelové pripojení Teredo Tunneling Pseudo-Interface:

    Prípona DNS podle pripojení . . . :
    Popis . . . . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
    Fyzická Adresa. . . . . . . . . . : 00-00-00-00-00-00-00-E0
    Protokol DHCP povolen . . . . . . : Ne
    Automatická konfigurace povolena : Ano
    IPv6 adresa. . . . . . . . . . . : 2001:0:4137:9e76:24a9:2dbe:f5ff:ff73(Prefe
    rované)
    Místní IPv6 adresa v rámci propojení . . . : fe80::24a9:2dbe:f5ff:ff73%12(Pre
    ferované)
    Vychozí brána . . . . . . . . . . : ::
    NetBIOS nad TCP/IP. . . . . . . . : zakázáno

    C:\Users\Petra>
  19. Can you delete that connection completely and restart so it reconstitutes itself? It might just get it right this time.

    Sorry I responded so late, I didn't see if you replied. I tried that but nothing happened.
  20. By chance have you installed an Apple\Adobe product (IIRC SKYPE also installs and uses this service) on this system lately ?? (I-tunes, Photoshop CS, etc.) I was experiencing a similar problem awhile back and found that the cause was the Bonjour service added by Adobe for it's Photoshop CS --- It was installing prior to the network drivers and thus setting up an unknown Network that was then keeping my network card from initializing. By going into the boot settings and setting the service to a delayed start it fixed the problem.

    To do this if you think it may be the problem for you as well -- type services.msc in run or services in search (win7)
    look for the id string on top that points to bonjour (on my system it was ##Id_String2.6844F930_1628_4223_B5CC_5BB94B879762##) and right click to bring up the properties
    On the Startup type pick the Automatic (delayed start) and save the change

    Doing this makes the service start after a delay and lets your network driver load first keeping the bonjour service from installing that unknown network.

    This has solved my issue so far
  21. If I could give a Best Answer in this thread, JDFan would definitely get it.
  22. JDFan said:
    By chance have you installed an Apple\Adobe product (IIRC SKYPE also installs and uses this service) on this system lately ?? (I-tunes, Photoshop CS, etc.) I was experiencing a similar problem awhile back and found that the cause was the Bonjour service added by Adobe for it's Photoshop CS --- It was installing prior to the network drivers and thus setting up an unknown Network that was then keeping my network card from initializing. By going into the boot settings and setting the service to a delayed start it fixed the problem.

    To do this if you think it may be the problem for you as well -- type services.msc in run or services in search (win7)
    look for the id string on top that points to bonjour (on my system it was ##Id_String2.6844F930_1628_4223_B5CC_5BB94B879762##) and right click to bring up the properties
    On the Startup type pick the Automatic (delayed start) and save the change

    Doing this makes the service start after a delay and lets your network driver load first keeping the bonjour service from installing that unknown network.

    This has solved my issue so far



    In my case this is not so. No Bonjour service at all.

    I don't know if it is important, but when I went:

    Control Panel > Network and Internet > Network Sharing Centre > View Network Computers and Devices

    I got a yellow pop-up at the top of the screen

    "Network discovery and file sharing are turned off. Network computers and devices are not visible. Click to change..."

    I click, and no matter what option I select, that message stays there.

    This is on the static IP, either set as home or work network.

    I am about to try removing the adapter.

    "
  23. OK, that didn't work - I will try with an updated driver another day.

    In the mean time - would doing anything with the advanced configurations help? DNS, WINS, LMHOSTS?
  24. In the mean time - would doing anything with the advanced configurations help? DNS, WINS, LMHOSTS?

    I really thought JDFan had nailed it that time - it's a brilliant solution but just not for you.

    DNS should have ticks in both Append options. WINS should have Enable LM Hosts look up" ticked and Default selected. More importantly if XP - but not if Vista or 7/8 - is the last tab marked Options. Click the Advanced button and make sure all three are marked "Permit All". If they aren't, it would explain a thing or two.
  25. OK, I'll double check those.

    I think the best thing I can do is screen shots - and lots of them ;)

    I'll come back tomorrow.
  26. Ok, everything was already as you suggest - only I can't find the Options tab you mention!

    Screenies as promised. Let me know if there is any more info you want.

    The static Ip below works fine, it is the DHCP that does not. I am typing this reply on the aforementioned machine.

    Interestingly the other 3 machines on the LAN receive DHCP fine. including an identical (same make, model, OS, bought at the same time) machine.









  27. After Saga Lout's comment to get the registry info for H_KEY_LOCAL_MACHINE>SYSTEM>CurrentControlSet>services>Winsock>Parameters
    I found that Tcpip6 was in front of Tcpip in my registry, I switched it so it looks like

    Tcpip Tcpip6 NetBIOS Psched RFCOMM

    this has solved my "unidentified Network" issue, I did this after a clean "route delete 0.0.0.0" and "netsh winsock reset catalog", rebooted.
    Also for me it was a wi-fi connection I also deleted that "known" network before rebooting.
  28. Nice one, jkal - by the look of escribblings Registry screenshot, he might benefit form your suggestion. Welcome to Tom's Hardware Forums, by the way.
  29. jkal said:
    After Saga Lout's comment to get the registry info for H_KEY_LOCAL_MACHINE>SYSTEM>CurrentControlSet>services>Winsock>Parameters
    I found that Tcpip6 was in front of Tcpip in my registry, I switched it so it looks like

    Tcpip Tcpip6 NetBIOS Psched RFCOMM

    this has solved my "unidentified Network" issue, I did this after a clean "route delete 0.0.0.0" and "netsh winsock reset catalog", rebooted.
    Also for me it was a wi-fi connection I also deleted that "known" network before rebooting.


    Nice one, jkal - by the look of escribblings Registry screenshot, he might benefit form your suggestion. Welcome to Tom's Hardware Forums, by the way.

    I was so hoping this would sort it, bu alas no.

    I am begining to give up all hope on this machine ever using DHCP again :(

    I switch Tcpip and Tcpip6. I even added NetBIOS when that didn't work.

    I did the

    route delete 0.0.0.0
    netsh winsock catalog


    I rebooted many times, disabled and re-enabled the adapter.

    I even tried disabling the adapter, changing its properties to automatic, "cleaning" and rebooting the machine before re-enabling the adapter.

    I even tried changing NetBIOS from Default to Enable NetBIOS over TCP/IP

    Nothing is working except assigning a static IP.

    It is not the cabling or the router port as these work with the other machines, so it has to be software or hardware in the machine itself.
  30. Darn it - it looked though that may have done it for you as well. Try netsh winsock reset catalog but I doubt it's that simple. I'm almost tempted to suggest getting a download of ComboFix from bleepingcomputer.com, after reading the Tutorial. Is there anything interesting or slightly dubious in your Hosts file? Check it in c:\windows\system32\drivers\etc and open it using Notepad.
  31. I am away from the machine now, but I'll check that later.
  32. How is your router setup? Do you by chance have DD-WRT flashed to it?
  33. I am having the same problem as well. Around two weeks ago it was working fine, I rarely used it; but now I have a reason too!

    Done the following:

    Re-installed Windows 7
    Reset router
    Plugged PC directly to modem

    :(
  34. ha2fb said:
    How is your router setup? Do you by chance have DD-WRT flashed to it?


    Router is as was when installed. No DD-WRT as it is monitored remotely. I am lucky I have the access to it that I do, but have to be very careful about re configuring it.

    However, I do not believe the router to be at fault. The other 3 machines and the countless wireless devices connect without issue. 1 machine is identical to the one with the issue.

    The cable and router port are not the issue either as these work with the other machines when swapped over.

    Here is some router info - by I don't think the router is the problem (I have masked the WAN IP and SSID for security reasons.

     	 
      		 Host Name:	 P-660HW-T1_v2
     	Model Number:	 P-660HW-T1 v2
     	MAC Address:	 00:23:f8:97:a1:2d
     	ZyNOS Firmware Version:	 V3.40(AXL.1) | 11/21/2007
     	WAN Information	 
     	    - DSL Mode:	 ADSL2 DELT
     	    - IP Address:	 ###.###.###.###
     	    - IP Subnet Mask:	 255.255.255.255
     	    - VPI/VCI:	 0/38
     	    - MTU :	 1500
     	LAN Information	 
     	    - IP Address:	 192.168.1.1
     	    - IP Subnet Mask:	 255.255.255.0
     	    - DHCP:	 Server
     	WLAN Information	 
     	    - SSID:	 ###############
     	    - Channel:	 1
     	    - Security:	 WPA-PSK
     	Security	 
     	    - Firewall:	 Enabled
     	    - Content Filter:	 Disable
  35. 14. - DHCP: Server

    Can that entry not be changed to Automatic by DHCP? Does accessing the router from one of the other wirelessly connected systems produce an identical report?
  36. 14. - DHCP: Server

    Can that entry not be changed to Automatic by DHCP? Does accessing the router from one of the other wirelessly connected systems produce an identical report?

    The options are Server, Relay or None.

    That report is from the routers homepage, and was accessed, copied and pasted through my mobile phone.

    However it does not change if you log in from another machine.
  37. Well, I hate to give up on you, escribblings but I'm out of ideas. Unless there's a background Proxy running in your system, I can't see what can be wrong. Could someone have enabled, say, FoxyProxy in Firefox without your knowledge. I take it there's nothing ticked in Internet Options>Connections tab>LAN button Proxy boxes. Sorry I couldn't be more help.
  38. Man this sucks, I have no idea what to do from this point on. Even with a fresh reinstall of Windows 7 it is not working!

    Saga Lout, thoughts?
  39. Without going back through the entire thread, I can't remember if I suggested delaying the start of the Bonjour Service at any time. If you have any Apple or Quick Time software, that Service can cause problems if it loads before some others. Apart form that, I'm out of ammo on this one and I can't even force a duplication of the circumstances in one of my own systems.
  40. Do a restore point going back to where everything worked.... Then see what happens.
    169.254.x.x is no DHCP server
    Static works but not picking up the IP from the router.
    Get another wireless card and see if it works.
    Still not working ???
    Not running any spoofing tools?
    BackTrack?
    Caine & Abel?
    Remove everything....

    If it's still not working then wipe the drive clean, no partitians, no OS, nothing.
    Clean is clean ....and BTW where did you get the OS from? Is it legal?
  41. Without going back through the entire thread, I can't remember if I suggested delaying the start of the Bonjour Service at any time. If you have any Apple or Quick Time software, that Service can cause problems if it loads before some others. Apart form that, I'm out of ammo on this one and I can't even force a duplication of the circumstances in one of my own systems.
    You didn't - but JDFan did, and nope - no Bonjour or similar service that I can tell is running.

    Anonymous said:
    Do a restore point going back to where everything worked.... Then see what happens.
    169.254.x.x is no DHCP server
    Static works but not picking up the IP from the router.
    Get another wireless card and see if it works.
    Still not working ???
    Not running any spoofing tools?
    BackTrack?
    Caine & Abel?
    Remove everything....

    If it's still not working then wipe the drive clean, no partitians, no OS, nothing.
    Clean is clean ....and BTW where did you get the OS from? Is it legal?


    I know it is not DHCP, it is Automatic Private IP.

    It's not wireless, it is hard wired. There is nothing wrong with the cable or router/router port as these work with the other machines on the network and this machine does not receive DHCP on their cables/ports.

    No spoofing tools that I am aware of.

    I will be running more checkup software on it soon, when I have time (only have my lunch breaks at the moment).

    Re-install is not an option at the moment - as much as I want this working with DHCP, it is working with static IP - and due to my time contraints, while it is working at all I cannot justify the re-install.

    As for is the OS legal. I should bloody hope so, it came pre-installed from PC-World. I bought to identical machines at the same time, same spec same OS. One is still working on DHCP and thee other is not.
  42. In my instance this is not a notebook and I dont have Bonjour installed.

    Fresh install on a desktop.
  43. I'm beginning to think the answer to this is in the router's settings somewhere so I'm going to set up a dummy router (rather than play around with my server systems) to see if I can duplicate the problem. Meantime, if you fellows could share router details, i might be useful.
  44. I'm beginning to think the answer to this is in the router's settings somewhere so I'm going to set up a dummy router (rather than play around with my server systems) to see if I can duplicate the problem. Meantime, if you fellows could share router details, i might be useful.

    My router is a Zyzel, I posted the setup details above. The DHCP pool starts at 101. I can't seem to segregate wifi from wired though, so they both share the pool of 101-255.

     	 
      		 Host Name:	 P-660HW-T1_v2
     	Model Number:	 P-660HW-T1 v2
     	MAC Address:	 00:23:f8:97:a1:2d
     	ZyNOS Firmware Version:	 V3.40(AXL.1) | 11/21/2007
     	WAN Information	 
     	    - DSL Mode:	 ADSL2 DELT
     	    - IP Address:	 ###.###.###.###
     	    - IP Subnet Mask:	 255.255.255.255
     	    - VPI/VCI:	 0/38
     	    - MTU :	 1500
     	LAN Information	 
     	    - IP Address:	 192.168.1.1
     	    - IP Subnet Mask:	 255.255.255.0
     	    - DHCP:	 Server
     	WLAN Information	 
     	    - SSID:	 ###############
     	    - Channel:	 1
     	    - Security:	 WPA-PSK
     	Security	 
     	    - Firewall:	 Enabled
     	    - Content Filter:	 Disable
  45. IP pool sharing between wired and wireless devices is quite normal. I can't think what could cause your problem but if there are any firewall or other access restrictions to your machine, it could be that those restrictions are overarched by a fixed IP. See if you can find anything.
  46. If your other Windows 7 systems don't show those 04 RunOnce entries for mctadmin.exe, re-run HJT and tick to remove them. If the other machiens have the same entries, don't bother because it isn't the problem.
Ask a new question

Read More

LAN Windows 7 Networking