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

shibby firmware and windows 8.1

Discussion in 'Tomato Firmware' started by tvl, Jun 2, 2014.

  1. tvl

    tvl Serious Server Member

    I am using rt n66u with the lastest shibby firmware aka 119. Everything work fine util i bought an asus desktop. My desktop is connected to router by cat 5 cable. The desktop can not connect to internet because its connection is limited, but my others computers under windows xp, the connection is fine. I flashed my router back to asus firmware. The connection is back to normal. I tried with other router, it's fine. So the problem must be between tomato firmware and windows 8.1. Plz help me. Thx
     
  2. teh_g

    teh_g Networkin' Nut Member

    I had no issues with Windows 8.1 and shibby

    Is DHCP enabled on the router?
     
  3. tvl

    tvl Serious Server Member

    Yes, and the computer is asus m11bb
     
  4. tbjerret

    tbjerret Network Guru Member

  5. BikeHelmet

    BikeHelmet Networkin' Nut Member

    Did you set Google or other DNS servers? For example:

    8.8.8.8
    8.8.4.4
     
  6. tvl

    tvl Serious Server Member

    No the network card had not been update. I tried to use the manufacture driver instead of microsoft's. But why other compters work, win xp, but not this one. I reflash the router to asus firmware and it works, weird.
    The dns is 0.0.0.0, default isp. Thx
     
  7. kthaddock

    kthaddock Network Guru Member

    Have you tried to deleted your wifi profile and reconect to new program ?
     
  8. Spyros

    Spyros LI Guru Member

    open a cmd with administrator privileges then

    Code:
    netsh advfirewall reset
    netsh branchcache reset
    netsh int ip reset
    netsh int ipv6 reset
    netsh winsock reset
    reboot
     
  9. Siff

    Siff Serious Server Member

    I don't think that the DNS should be 0.0.0.0 - try disabling and then enabling your Ethernet adapter. I had a similar issue under Windows 7 where there was DNS 0.0.0.0 before the correct DNS and disable/enable of the network card solved the issue (release/renew didn't!).

    Hope this helps.
     

Share This Page