Wireless > Ethernet?

[bobber205]

The guys above us at my school are having us put all of our ethernet desktops over to wireless.

The wireless network over the last year or so hasnt' been reliable at all (I once calculated a 93% uptime or so). But we've been promised it will be.

I was told the reason is because "manageable" ethernet switches are much more expensive than the same thing for wireless networks.
Is this true?

Also, in Windows: to log into the secure wireless network, you need to be onto the domain. But you can't connect to that network unless you're on the domain. So in the login screen, you have no network connection b/c the system requires your username and password combo to connect.

So it's a catch-22. Is there even a way to have windows connect a wireless device while on the login screen?

Thanks for the help!

 

[EagleKeeper]

You can attempt to connect to a secure domain from a wireless connection via a login screen.

That is how the WiFi works at non-free airports and hotels

Windows (your laptop) is operational - however, you do not have internet access until you are authenticated

 

[bobber205]

Would you mind posting a link that explains this maybe with pictures?

 

[bobber205]

I guess I should clarify. By login screen, I mean the screen that you see when *Windows* boots up.

 

[Czar]

Sounds like a bad idea.

If managed switches are so expensive then just skip those and get cheaper ones that are not managed.

 

[bobber205]

We have cheapers ones already that aren't managed. They don't seem to think that's enough.

 

[EagleKeeper]

Are you attempting to control access to Windows or the Network.

The Network is not needed to get the OS up and nor should it be.

Access to the Network is via the wireless and initially using a Web Browser to authenticate.

I use it at Airports, Hotels, etc.

Some will be setup for authentication required every time you connect, others once during a set time period.

 

[bobber205]

The users need to be able to log onto the domain X.

two reasons that can't currently happen.
1) Wireless is not connected to a network when the machine is not logged onto a user.
2) It needs the credentials stored in the user's profile to be able to log onto the network at all.

This is not just access to the internet, but the domain as well.

We're currently stuck with machines that cannot log in because they have no connection to the domain because they need a connection to the domain in order to log in.

It's a catch 22.