Overview: 1. We have one lan used for internal and back to main company HQ. (We can access the internet with this but it is very - very slow)
we decided to to install a wireless ADSL router with internet access
- so we could our own independent faster internet access !!!!
installed wirless cards on PC's (which also have PCI NICs)
Problem; we can access fast internet access now ... but we need to aslo use IE to access company web and specialist site(which is only accessable through Wired LAN).
How can we a use a.IE to access 2 differnet lans(internet) ? b. Mozilla -no good - one of our key general sites does not support it ! other suggestions ?
both lans are on differnet IP' s LAN 1 10.x.x.x Lan2 192.X.X
also one program draws data from old lan (LAN1 10.x.x.x)
I don't see how bridging networks a wired and a wireless one is going to allow a single machine using IE to know when to access one network as opposed to another network.
A bridge is between the two networks so that wired and wireless machine can act as one physical network.
formatting link
In either case of LAN 1 10.x.x.x or Lan2 192.X.X even with a bridge, a computer in your case can only be connected to one physical LAN with an IP. It can't be connected to two LAN(s) simultaneously with two IP(s) in this case. You cannot come across a network with software such as IE and use that machine as if it's part of the other network. It's impossible.
However, it is possible through the bridging of the two networks and machines on both sides of the bridging can see each other, that you could use a single machine on the other side in a RDS or Terminal situation with multiple connections with multiple uses on both LAN(s) using that one machine to access the Internet using IE on that machine.
Maybe with Terminal Services or RDS. I hear RDS can have multiple RDS sessions as well if set-up properly.
Well get the main router that connects you to your wan to advertise the adsl router as the router of last resort.
ie stuf it knows about routes via the corporate lan other wise it goes to the internet.
any packets to internal systems got to the main wan anything else goes to
Are you ABSOLUTELY sure your not going to get disemboweled by the headoffice network/security guys you realy should do this unless you know what you are doing.
Another post in this thread by Duane gives more info, and a link to a place for more info
A bridge is between the two networks so that wired and wireless machine can act as one physical network.
formatting link
Read his post and see that wiki for how to do it....
One addition, if you know the ip address (4 hex numbers seperated by periods), in many cases you can go directly there from the browser by typing it instead of the www thing.. The www address is actually resolved to 4 hex digits anyway.. (IE mine are all similar, but I can use 192.168.1.4 is my local network storage, 192.168.7.77 is a dialup modem on the network,
192.168.2.100 is my Bluetooth AP etc)...
I wonder, if you bridge, if you could just use the same browser but instead of the www address that has to be resolved, if you could just type in the
This isnt an IE problem - it is IP based. luckily Windows NT and derivatives do handle IP routing and /or multi interface config.
So - assuming that you dont have security / firewalls / restrictions on each PC that get in the way...
what you have to do is get the PC to make sensible decisions about which interface to use for which destination subnets.
if you run "netstat -r" at a command line prompt you will see the local PC routing table. here is part of one for my w2k PC with only 1 LAN connected - XP should show the same kind of display. =========================================================================== Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.25 1 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1 192.168.0.0 255.255.255.0 192.168.0.25 192.168.0.25 1 192.168.0.25 255.255.255.255 127.0.0.1 127.0.0.1 1 192.168.0.255 255.255.255.255 192.168.0.25 192.168.0.25 1 224.0.0.0 224.0.0.0 192.168.0.25 192.168.0.25 1 255.255.255.255 255.255.255.255 192.168.0.25 192.168.0.25 1 Default Gateway: 192.168.0.1 ===========================================================================
192.168.0.0 255.255.255.0 192.168.0.25 192.168.0.25 1 is the entry for the subnet connected to the Ethernet - you should have entries in for both the local LAN interfaces. the default gateway tells you which "way" the PC will send packets to addresses not covered by the routing table.
if this doesnt work, then it probably means your local and corporate networks have multiple subnets and you are going to have to add static routes to override the default gateway setting for some destinations.
exactly what to set is going to depend on the subnets used - and may well change if "corporate" alter the network design.
so you will end up with a complex set of config on each PC (and some PCs may not allow you to set this up - eg older versions of Windoze).
i suspect the overall network is more complicated, and this will be tedious to fully set up, and more difficult to test and maintain.
So - you can do this, but it is going to cause some ongoing hassle.
i suggest you "fix" this properly, forget about the separate wireless network and get a local Internet feed integrated with the router that feeds the corporate WAN.
After all - faster Internet is the reason you said you were doing this, and hooking it into the common internal network fixes it for visitors with laptops and so on, as well as local based PC users.
Also - you corporate network guys will then be able to sort out your firewall, maintain the kit, get the internet feed fixed when it breaks, and respond to any intrusion attempts.
The only place the 10.x.x.x IP will lead to, which is a LAN IP on the other network, is to the machine that has the LAN IP. The machine will be a WEB or FTP server, since this is a browser being used. They do have RDS via a browser over the Internet, which I use to RDS to my machine at work.
Or you can use Terminal Services via a LAN or WAN connection so that mutiple users LAN or WAN can run applications from a Terminal Server as if they were there at th machine running them, which RDS can do as well LAN or WAN, but with not as many connections as a Server O/S, if it's a XP Pro workstation that only allows 10 concurrent connections.
I would set up a proxy machine. Have one machine that connects to the DSL/internet line and to the 10.x.x.x line. Set up a proxy server on that machine to use the DSL connection as the connection to the internet. The have everybody point their browser proxy to the 10.x.x.x address of the proxy machine and set up exceptions so the browser doesn't use the proxy for internal (10.x.x.x) addresses. This way it can see both worlds. there are many free proxy server apps out there that could do this for you.
Cabling-Design.com Forums website is not affiliated with any of the manufacturers or service providers discussed here.
All logos and trade names are the property of their respective owners.