work VPN connects but no apps

Discussion in 'Tomato Firmware' started by twit54, Apr 7, 2009.

  1. twit54

    twit54 Addicted to LI Member

    HI Folks,

    I'm probably missing something simple here.

    I have a Linksys WRT54GS V1.1 with one desktop XP pro machine and one work supplied laptop with XP pro. Both are wired to the router.
    The work laptop registers to HO via VPN.

    All was working well with the latest Linksys firmware.

    I recently downloaded the freephoneline client and it would not register.

    A change to Tomato cleared that problem but now my work laptop is fubar

    The VPN connects and I can see common drives but no apps work

    My Outlook will not register to exchange

    Any thoughts here?

  2. twit54

    twit54 Addicted to LI Member


    After a little more work here's an update

    Stock latest linksys firmware.....freephoneline will not register, Laptop VPN starts....apps and outlook registers to exchange

    Tomato latest firmware......freephoneline works......latptop vpn starts...apps work Outlook will not register to exchange

    DD-WRT latest firmware......same behaviour as Tomato

    Something about Tomato and DD-WRT is preventing outlook from registering to exchange
  3. occamsrazor

    occamsrazor Network Guru Member

    You don't mentiomn what type of VPN you are using to connect to work.

    I can't see any reason why if you ARE able to connect the VPN to your work, various applications aren't connecting. FYI I use Outlook/Exchange over a Juniper SSL VPN connected to my work just fine with Tomato.

    The only thing I can think of is you have some type of DNS problem... e.g. Outlook is trying to connect to an exchange server with a DNS address that is internal to your workplace, but those DNS records are not being passed on to your laptop from the work VPN software, so your laptop is trying to resolve the address e.g. using your ISP's DNS server which of course cannot find an entry.

    I believe (I'm no expert at this) that one way you could test this would be to ping the various servers WHILE AT WORK, write down their IP addresses, and then when at home over the VPN try to connect e.g. Outlook to them via internal IP address instead of DNS name.

    Or you could try manually adding your company's DNS servers to your system and try that way.

    I've no idea if any of this is actually the cause in your case, just a thought......
  4. twit54

    twit54 Addicted to LI Member

    ok....a lot of further testing reveals the following:

    The VPN is standard XP Pro type

    With stock Linksys firmware, Outlook tries to connect to exchange via name. I opened CMD and pinged using the smae name and got a response no problem

    Then reloaded Tomato with default settings. VPN connects, I can see all network drives and run all apps except outlook. Opened CMD and tried to ping the same name for exchange server and it all timed out

    I take that to mean that Tomato is blocking either the transmit or recieve packets to or from that name .

    Any thoughts as to what setting needs to be changed or how I can diagnose that through Tomato logs?

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice