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

Problem using VNC on a wireless client with Tomato

Discussion in 'Tomato Firmware' started by prupert, Mar 15, 2009.

  1. prupert

    prupert Addicted to LI Member

    Hi

    I have been a happy Tomato firmware user for almost 1.5 years, since it was featured on Lifehacker.

    However, since upgrading to Vista on my laptop and the latest version of Tomato on my Linksys WRT 54GL I have had two unusua problems, specific to the latop.

    When I am on my wireless connection on the laptop, using the wifi connection from the Linksys (running tomato v1.23) I am unable to see any other of the PCs on my windows network and am unable to connect via VNC to any of these PCs. It does occasionaly see my UnPN server (which is actually MediaTomb running on my Ubuntu server, but it never actually sees the Samba shares on the same server).

    If I then turn off the wifi connection and use a wired connection (plugged into one of the ethernet ports on the router) I can see all the PCs on my windows network, can connect to all the windows shares and can connect to any VNC servers on the network.

    I have looked over the settings in wireless on tomato and searched here on the forums, but I haven't found anything the seems to relate to this.

    Does anyone have any ideas what I am doing wrong? It is clearly a setting that is adding some extra security to the Wireless connection, that is preventing it from seeing the Wired network, but I don't know what it is.

    Any help would be appreciated....
     
  2. astehn

    astehn LI Guru Member

    I'm not sure if this will help because I can't say I entirely understand how the setting works, but you should make sure that "AP Isolation" is DISABLED in "Advanced," "Wireless" settings.
     
  3. prupert

    prupert Addicted to LI Member

    yup, it is already set to Disable.

    thx for the reply and if this isn't the best place to post this question, please could someone direct me to where is best ;)
     
  4. bigclaw

    bigclaw Network Guru Member

    My understanding is that the same laptop can access network resources using a wired Ethernet connection but not a wireless connection. Correct?

    My suggestions:

    1) Compare the network settings of your wired and wireless connections. You can find them under Control Panel->Network and Sharing Center. Pay attention to the Sharing and Discovery settings. Both wired and wireless connections should show up as a "private network". "Network discovery" should be on.

    If they are the same, compare network connection settings and see if you can find any discrepancies. You do so by clicking on "manage network connections" in the left pane.

    1) Turn off Windows Firewall, or any other firewall product, temporarily. Reboot and try again. Does that resolve your problem? If so, it's firewall-related.

    3) Do you know how to do an "ipconfig /all"? If so, issue it both when using a wired and wireless connection. Compare the IP addresses (and other settings) in both cases. Are they from the same subnet? (e.g. both are 192.168.1.x). Post back the settings if you find anything suspicious.
     
  5. prupert

    prupert Addicted to LI Member

    The settings are exactly the same in the wired and wireless connections in Network and Sharing Centre.

    Turning off Windows Firewall (the only firewall running) makes no difference to the wireless connection. I can still ping the other servers on the network and view webpages hosted on those servers, but I can't see them in the Network section in Windows and VNC connections fail.

    When I switched to a different router for a while, I was able to see the Windows network and connect via VNC with the same laptop using the same settings (this was with an Asus WL 500G Premium running stock firmware and Opne-WRT).

    So, from all this, it is clearly some screwed up setting I have in the Tomato firmware, though what the heck it is I just dont know....

    iirc i was running v 1.19 for a while and this wan't a problem, I guess I could just downgrade to a rotten version, but that still doesn't work out what is wrong...

    Here are the results of ipconfig for the two connections:

    ipconfig for wired connection:

    Microsoft Windows [Version 6.0.6001]
    Copyright (c) 2006 Microsoft Corporation. All rights reserved.

    C:\Users\rupert>ipconfig /all

    Windows IP Configuration

    Host Name . . . . . . . . . . . . : xps
    Primary Dns Suffix . . . . . . . :
    Node Type . . . . . . . . . . . . : Hybrid
    IP Routing Enabled. . . . . . . . : No
    WINS Proxy Enabled. . . . . . . . : No

    Wireless LAN adapter Wireless Network Connection:

    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Intel(R) Wireless WiFi Link 4965AGN
    Physical Address. . . . . . . . . : 00-1F-3B-98-40-43
    DHCP Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes

    Ethernet adapter Local Area Connection:

    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Broadcom NetLink (TM) Fast Ethernet
    Physical Address. . . . . . . . . : 00-15-C5-73-E8-02
    DHCP Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes
    Link-local IPv6 Address . . . . . : fe80::a096:fc76:ea5d:466f%9(Preferred)
    IPv4 Address. . . . . . . . . . . : 192.168.1.131(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Lease Obtained. . . . . . . . . . : 15 March 2009 16:47:54
    Lease Expires . . . . . . . . . . : 16 March 2009 16:47:54
    Default Gateway . . . . . . . . . : 192.168.1.1
    DHCP Server . . . . . . . . . . . : 192.168.1.1
    DNS Servers . . . . . . . . . . . : 192.168.1.1
    NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter Local Area Connection* 6:

    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
    Physical Address. . . . . . . . . : 02-00-54-55-4E-01
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 7:

    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : isatap.{DC9CC488-58DB-4DA8-86A5-9BDE59793
    723}
    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 11:

    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes

    ifconfig for wireless

    Microsoft Windows [Version 6.0.6001]
    Copyright (c) 2006 Microsoft Corporation. All rights reserved.

    C:\Users\rupert>ipconfig /all

    Windows IP Configuration

    Host Name . . . . . . . . . . . . : xps
    Primary Dns Suffix . . . . . . . :
    Node Type . . . . . . . . . . . . : Hybrid
    IP Routing Enabled. . . . . . . . : No
    WINS Proxy Enabled. . . . . . . . : No

    Ethernet adapter Bluetooth Network Connection:

    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
    Physical Address. . . . . . . . . : 00-1F-E1-F2-90-51
    DHCP Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes

    Wireless LAN adapter Wireless Network Connection:

    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Intel(R) Wireless WiFi Link 4965AGN
    Physical Address. . . . . . . . . : 00-1F-3B-98-40-43
    DHCP Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes
    Link-local IPv6 Address . . . . . : fe80::14ab:6cf9:3f08:3fe9%10(Preferred)
    IPv4 Address. . . . . . . . . . . : 192.168.1.139(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Lease Obtained. . . . . . . . . . : 13 March 2009 21:27:11
    Lease Expires . . . . . . . . . . : 16 March 2009 23:37:17
    Default Gateway . . . . . . . . . : 192.168.1.1
    DHCP Server . . . . . . . . . . . : 192.168.1.1
    DNS Servers . . . . . . . . . . . : 192.168.1.1
    NetBIOS over Tcpip. . . . . . . . : Enabled

    Ethernet adapter Local Area Connection:

    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Broadcom NetLink (TM) Fast Ethernet
    Physical Address. . . . . . . . . : 00-15-C5-73-E8-02
    DHCP Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 6:

    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
    Physical Address. . . . . . . . . : 02-00-54-55-4E-01
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    IPv6 Address. . . . . . . . . . . : 2001:0:cf2e:3096:1c37:2222:3f57:fe74(Pref
    erred)
    Link-local IPv6 Address . . . . . : fe80::1c37:2222:3f57:fe74%8(Preferred)
    Default Gateway . . . . . . . . . : ::
    NetBIOS over Tcpip. . . . . . . . : Disabled

    Tunnel adapter Local Area Connection* 7:

    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : isatap.{DC9CC488-58DB-4DA8-86A5-9BDE59793
    723}
    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 10:

    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 11:

    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes

    C:\Users\rupert>

    The only difference I can see is a different IP address, surely that makes no difference...
     
  6. bigclaw

    bigclaw Network Guru Member

    I'm out of ideas. Did you do a NVRAM reset before/after upgrading to 1.23? If not, you can try that. It's been known to eliminate weird problems.
     
  7. prupert

    prupert Addicted to LI Member

    ooh, I dont think I did.

    Could you point me in the right direction to where instructions to do that are, I don't recall seeing them on the tomato firmware page?

    Cheers

    It's a wierd one aint it.
     
  8. astehn

    astehn LI Guru Member

    To reset NVRAM, go to "Administration," "Configuration," then select "Erase all data in NVRAM memory" from the Restore Default Configuration dropdown box.

    Bear in mind that this will erase ALL your settings, and you will have to reconfigure from scratch. But as bigclaw said, this is the best way to ensure that your problem doesn't stem from some accidental, hidden setting.
     
  9. prupert

    prupert Addicted to LI Member

    Ok, I will try that out and see what happens. Cheers for everyone's help.
     
  10. baldrickturnip

    baldrickturnip LI Guru Member

    can you connect to the VNC server by using the IP address of the server rather than the hostname ?

    I connect to various VNC machines from my laptop via wifi to a 54gl with tomato 1.23 and I have never noticed a problem. Inside my network I use the IP address of the machine I want to get to.
     
  11. prupert

    prupert Addicted to LI Member

    I always use the IP address, never the hostname - but I just get an error message saying it could not connect to the address.

    I will try clearing the NVRAM and seeing if that sorts it out...
     
  12. bripab007

    bripab007 Network Guru Member

    For years I've used all manner of VNC servers in conjunction with all manner of VNC clients (viewers) on my Tomato'd home network and have had nary a problem.
     
  13. prupert

    prupert Addicted to LI Member

    Yeah, that is why I am so confused, internet searches never revealed anything - I even resorted to a full re-install of Vista to try and fix the issue, assuming it must be something wrong with the laptop, but it did not fix it. Thus I am assuming it must be a misconfiguration in Tomato on my side.
     
  14. bripab007

    bripab007 Network Guru Member

    So, did you do the NVRAM erase yet?
     
  15. prupert

    prupert Addicted to LI Member

    Sure did

    and

    no luck :(

    Exactly the same as before.

    VNC logs show the following:

    Deregistered connection from app
    Exiting
    VNC viewer closing down


    Not exactly enlightening.

    Man this is annoying....hmm, I have an idea, I dual boot Linux on the laptop, I will see if I can VNC in that way.....will update soon.
     
  16. bripab007

    bripab007 Network Guru Member

    I think it's a Vista/Windows issue. Do you have a password defined for your user account in Vista?
     
  17. prupert

    prupert Addicted to LI Member

    I just booted into Unbuntu (Intrepid) on the laptop and it also failed to connect to my VNC server under Ubuntu.

    Interestingly, I CAN connect via VNC to a client that is also connected to the same wireless network provided by the tomato firmware. However, both fail to see the Windows Network that my wired PCs are connected to.

    To answer your question, I do have a password to log in to Vista.
     
  18. bigclaw

    bigclaw Network Guru Member

    Hey. I have another idea. Are you sure you are connected to your own wireless network, not a neighbor's?

    I know it's a crazy idea, but hey it explains the symptoms... :)
     
  19. prupert

    prupert Addicted to LI Member

    there is only one plumternet near me and that's my wireless network ;)

    but that is a crazy enough possibiilty to explain away this odd situation....

    but no, I am defo connected to my own wireless network
     
  20. prupert

    prupert Addicted to LI Member

    I figured it out.

    It's really embarassing. I worked out that my IDS system (thin client running Snort in inline mode) was messing with VNC connections. It (use to) site between my Router and a switch. All wired VNC traffic hit the switch first, thus didn't go through teh router and hence didn't go through snort. Wireless traffic obviously went through the Router and snort and even though I had turned off all VNC rules, there were obviously some that caused snort to drop all VNC traffic.

    So, I moved the IDS and fixed my problem.

    Sorry for all your wasted time.
     

Share This Page