Q: Interesting problem here. At work, the company is an NT domain, but access to the Internet via a proxy will be part of our parent company in Europe. For general browsing it works well enough, but when our IT guys try all the files was painfully slow to download. Our solution was to establish a “secret” DSL connection we connect via a wireless router (like home) 0.
When I just connected to the DSL line, it works great. However, once I plug the network back online, I can not connect to the Internet unless I make the proxy settings for the LAN, even though the wireless connection to the router is unaffected. How do I get both connections to work at once?
I.E. associated with both:
Proxy settings enabled = LAN settings disabled = proxy
Proxy via Internet through DSL
This on a WinXP Pro machine without Windows Firewall. What am I missing here?
Best Answer: This could be the router for you
http://reviews.cnet.com/routers/linksys-…
The router says it has Dynamic DNS and QoS so it could be a good fit for your network. Listed at less than $160.
But I don't think it's DSL capable, you should be able to work it in behind your 2Wire, and lighten up the firewall rules on the 2Wire since this has Stateful packet inspection, and your users shouldn't get to your servers much slower, especially if your 2Wire has a gig interface to connect to this router.
Then set up the link to this router as the DMZ or this could give you options to further segment your traffic.
Hope this helps, if so check out my site
http://trifutec.com
Also try this one, says it has QoS and DMZ option, plus it's a DSL router, fits right in!
http://www.linksysbycisco.com/US/en/prod…
Re:You, sir, are a gentleman and a scholar. Problem solved.
Thanks! :beer:
Re:route /delete 0.0.0.0 0.0.0.0 <your lan gateway IP address here>
Re:Originally posted by: guy
Originally posted by: guy
Let's get back to the issue then. Is there a way for me to get this working like I want, or should I just say screw it and pull the LAN cable when I need to use the other connection?
I already provided a solution. Remove the default gateway/route on the LAN side with the "route" command. You could even write a little batch file to switch it around.
Sorry I'm a bit dense today. I hate to say it, but treat me like a noob on this one. I see the route command is something I would do on a DOS command line, but after reading the /? I'm a bit fuzzy on implementation. Would it be something like:
route -f [my LAN IP address]
Re:Originally posted by: guy
Let's get back to the issue then. Is there a way for me to get this working like I want, or should I just say screw it and pull the LAN cable when I need to use the other connection?
I already provided a solution. Remove the default gateway/route on the LAN side with the "route" command. You could even write a little batch file to switch it around.
Re:Let's get back to the issue then. Is there a way for me to get this working like I want, or should I just say screw it and pull the LAN cable when I need to use the other connection?
Re:I predict this thread going down hill fast.
Re:Good point, but it is password protected and not bridged to the LAN. The worst that happens is someone breaks into the router is that we provide some free internet access. We do regular checks of the logs and such anyway…
Re:Onsite at HP it's <2 hours for a rogue AP to get found. Policy is to contact a manager, and request a leave during investigation.
Re:Heh, some of us actively scan for rogue devices. (switches, routers, access points, IPs outside of the defined range, more than one mac on a port, etc).
This is normally done by the "head office" using automated tools that look for this stuff.
Re:That won't happen either.;) It's legit as far as management is concerned, we're just keeping knowledge of the DSL connection among a few select people.
Edit: By legit, I mean that the company is paying for it. It's easier for us to pay for the extra connection to use for file transfers than deal with the asshats managing the proxy in Europe.
Re:Originally posted by: guy
Interesting problem here. At work, the company is an nt domain but internet access goes through a proxy belonging to our parent company in Europe. For general surfing this works well enough, but when us IT guys try to download any files it is painfully slow. Our solution was to setup a "secret" DSL connection which we connect to through a wireless router (just like at home).
When I am connected only to the DSL line, it works great. However, as soon as I plug in the LAN line again, I can no longer connect to the internet unless I enable the proxy settings for the LAN, even though the wireless connection to the router is unaffected. How do I get both connections to work at once?
I.E. with both connected:
Proxy settings enabled=LAN internet through proxy
Proxy settings disabled=internet through DSL
This is on a WinXP Pro machine with no windows firewall. What am I missing here?
I am smelling a suspension or maybe even a firing if they find it, and they will eventually 
Re:remove the route from the LAN (the default gateway)
you can do this with the route commands.
And I should warn you that what your doing puts your entire company at risk and could very well end in termination.
Re:Originally posted by: guy
Provided you get IT permission and they make sure that it does not compromise the Network.
Technology wise you can put the DSL on a separate computer that has two NICs. Configure one NIC to gets its Gateway and DNS from the DSL provider and Bridge the second NIC to the Network.
:sun:
I'm afraid that won't be an option. The DSL line will have to remain seperate from the domain. Removing the default gateway I don't think is going to work either as I'm using DHCP for both connections. Any other ideas?
Re:remove the default gateway from the LAN (non "super sekrit dsl that's going to get us fired") connection might fix it.
Re:Provided you get IT permission and they make sure that it does not compromise the Network.
Technology wise you can put the DSL on a separate computer that has two NICs. Configure one NIC to gets its Gateway and DNS from the DSL provider and Bridge the second NIC to the Network.
:sun:
0 Comments.