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

Can connect to web server, but not network..

Discussion in 'Tomato Firmware' started by Trel, Feb 15, 2013.

  1. Trel

    Trel LI Guru Member

    I don't know if I did something wrong, but here's what I did.

    Fresh install of firmware, cleared NVRAM and reset with the button.
    -Set IP settings to

    DHCP assigns 172.16.0.x
    Statically assigned IPs assigned 172.16.1.x

    And now the problem.
    Everything looked like it was working at this point, but then any machine with a 172.16.0.x could not access a smb network on 172.16.1.x, if I moved it to 1.x, it could. What perplexes me here is that, I also have a webserver running on one of the 1.x machines on a non-standard port. 10080.

    Machines on 0.x could access via a browser, but still could not connect to it for networked file shares \\machine, nor \\

    I changed everything back to a Class C 192.168.x.x in the mean time, but I'm trying to figure out what I was doing wrong.
  2. Trel

    Trel LI Guru Member

    I would like to add, when I changed back to a Class C (192.168.1.x), everything was able to communicate again.
  3. Trel

    Trel LI Guru Member

    Hopefully enough time has passed that bumping this would not be frowned upon.
  4. koitsu

    koitsu Network Guru Member

    Your issue has more to do with your CIFS/SMB server configuration than it does with your router or a firmware. You'll be very surprised how CIFS/SMB works, especially Samba, where you have to tell it what your broadcast address is to work correctly. This forum is not about how to configure Samba or CIFS/SMB servers. :)

    If your clients can telnet to on TCP port 445 (actual CIFS/SMB protocol), as well as on TCP port 139 (NetBIOS), then the issue has nothing to do with the router or your configuration on the router, as your netmask on the router looks correct.
    eahm likes this.

Share This Page