I have a remote office that is very old. We were brainstorming on how to set up 5 workstations in the office, being that there was no cabling available. WE decided it would be much eaiser to do wireless than to pull cable into the walls.
We set up a firewall router and vpn to the main office.
We added a linksys 54G wap with all the extra WA, no broadcast SSId, and resticted mac addresses.
We installed wireless 54g usb adapters on the five workstations and everything connects and works great......
Except, no one can log on to the domain. Simply because, the wireless connection will not come on unless you are logged in, but new users, who don't yet have a profile on the machine, can not login, because the domain is not available, because the network connection will not enable until you login. Catch 22
Is wireless technology just not made to work with domains? The only other option I could find was a wireless bridge, but they run $150 each and it would be cheaper to just run cable, and I'm not confident it would work.
We set up a firewall router and vpn to the main office.
We added a linksys 54G wap with all the extra WA, no broadcast SSId, and resticted mac addresses.
We installed wireless 54g usb adapters on the five workstations and everything connects and works great......
Except, no one can log on to the domain. Simply because, the wireless connection will not come on unless you are logged in, but new users, who don't yet have a profile on the machine, can not login, because the domain is not available, because the network connection will not enable until you login. Catch 22
Is wireless technology just not made to work with domains? The only other option I could find was a wireless bridge, but they run $150 each and it would be cheaper to just run cable, and I'm not confident it would work.