«

I am understandably pretty pi***ed off, I’m sorry if I offend anyone.
Microsoft knows about this issue has released two massive service packs for
XP and still no solution. Anyway enough of my complaining.

I am supposed to deploy 50 desktops to run completely on wireless and these
computer policies don’t process.

Does anyone have a true solution, such as an app that is either sold
separately or is included with a NIC that would work around this problem?
I would prefer low profile PCI, but if I have to go USB that’s just the way
it is.
I would also prefer dual band but 802.11a only will also do.

Please help before I kill someone.

Thanks,

Kenny

Sorry now that I've calmed down a little they are recieving the cannot obtain
domain controller name messages. I am also trying to get software to install
among other things.

put away the gun... what is your problem? from what you have stated below
you don't like something microsoft does or doesn't do, but you don't say
what it is. all i can see as a possible problem is that 'these computer
policies don't process'. what policies? what processing? what kind of a
network, domain, workgroup?? what os, xp home or pro? and why does the type
of nic affect the 'processing of policies'?


"Kenny782" <> wrote in message
news:F5E88A0D-CE85-400D-9EE1-...
>I am understandably pretty pi***ed off, I'm sorry if I offend anyone.
> Microsoft knows about this issue has released two massive service packs
> for
> XP and still no solution. Anyway enough of my complaining.
>
> I am supposed to deploy 50 desktops to run completely on wireless and
> these
> computer policies don't process.
>
> Does anyone have a true solution, such as an app that is either sold
> separately or is included with a NIC that would work around this problem?
> I would prefer low profile PCI, but if I have to go USB that's just the
> way
> it is.
> I would also prefer dual band but 802.11a only will also do.
>
> Please help before I kill someone.
>
> Thanks,
>
> Kenny
>

I'm sorry however after working on this for several days straight.... Anyway
here you go

Here someone elses post that explains it a little better:

>>I have a Wireless infrastructure and have setup group policies to install
>>applications. The Hard Wired side works fine but the Wireless tells me
>>that it cannot contact the domain controller to install the Policy. Is
>>there some slow link detection that I need to set up in my GPO to solve
>>this problem? And if there is where and how should it be done? Any ideas
>>would be a great help.
>
> Yes there was one well known issue with applying policies over WLAN.
> (I don't know the current state of this post SP2)
> The problem was that there is only a short time window when a machine can
> pull the
> policy from domain - something about 2 seconds. This is often not enough
> for WLAN.
> The link speed by itself is not a problem (though if it is below certain
> limit, the 2 sec.
> timeout can hit even a wired network)

Just for the record, I'm nto one of these Microsoft haters. I actually like
Microsoft and there products, especially Windows XP. Hell, I manage a
microsoft network for a living.

However I recently went through some group policy hell due to some other XP
bugs on my 2003 domain which I worked with Microsoft after a month long
support case. So I'm just not in the best of moods with XP, and I know you
don't want to here baout this I just don't want to give anyone the wrong
impression.

Kenny

"Kenny782" <> wrote in message
news:8ADA67A2-CC52-463B-AE54-...
> Just for the record, I'm nto one of these Microsoft haters. I actually
> like
> Microsoft and there products, especially Windows XP. Hell, I manage a
> microsoft network for a living.
>
> However I recently went through some group policy hell due to some other
> XP
> bugs on my 2003 domain which I worked with Microsoft after a month long
> support case. So I'm just not in the best of moods with XP, and I know you
> don't want to here baout this I just don't want to give anyone the wrong
> impression.
>
> Kenny

Back to your original problem. Have you investigated breaking the number of
desktops into numbers of anywhere up to 10 per workgroup and smart bridging
(with a physical rather than software smart bridge) them? That would reduce
chatter to the server if each workgroup works within it's own area until
need arises to go outside of it and thus make it more likely that a response
would come back.