Hi,
I'm fiddeling around now for some time to get a PC connected to a win2003 domain via a Wireless connection (Linksys AP).
The client's can be windows 2000 or windows xp pro.
As a standalone machine the PC's can connect and surf the internet. No problem in general.
But if the user needs/wants to login to the domain. Than some problems pop up.
sometime's folder redirect 'can not find the server' during startup of the PC. But in general is does recover from this if I click on the 'little pc shaped icon on the taskbar' and sync the folders (all the time internet access is possible). More often the connection to the server failes and the connection is lost. But than also internet access is lost and not automatically recovered.
What's so difficult about assigning a user working on a wireless workstation to a domain using folder redirect.??
Is a 'more complex' solution i.e. vpn a more stable solution?
p.s. everything related to slowlink is set to 0 in the GPO.
I'm fiddeling around now for some time to get a PC connected to a win2003 domain via a Wireless connection (Linksys AP).
The client's can be windows 2000 or windows xp pro.
As a standalone machine the PC's can connect and surf the internet. No problem in general.
But if the user needs/wants to login to the domain. Than some problems pop up.
sometime's folder redirect 'can not find the server' during startup of the PC. But in general is does recover from this if I click on the 'little pc shaped icon on the taskbar' and sync the folders (all the time internet access is possible). More often the connection to the server failes and the connection is lost. But than also internet access is lost and not automatically recovered.
What's so difficult about assigning a user working on a wireless workstation to a domain using folder redirect.??
Is a 'more complex' solution i.e. vpn a more stable solution?
p.s. everything related to slowlink is set to 0 in the GPO.
