Search results for query: *

There is no SP1 for Wk3. Also the rpc restart is from blaster virus. When you shearch for the virus you didn't find it because it does't affect a .net machine but it can shutdown it remote.

Are you using an nt account to loggin to PWA. If not this is your problem

Maybe you have firewall enable at .net server connections

This warm cant infect .Net server but through other machines can send an RPC shutdown This patch cause problems with SQL,ASP,IIS and some others connections

You can use sql 2k with sp3 installed It works fine

i have tested as a microsoft vendor and it works fine

Yes it's just problem with your drivers,, i think that if you check it at a win2k server you will get the same error

Hmm check your hardware at Microsoft size, maybe something incompatible with .Net

Don't try any drivers for win 2k isn't compatible. Try winxp drivers. Server 2003 is the XP server

Set dns at the tcp/ip properties of the client

No much differences there, just enable ras server and configured as VPN srv

When you promote net server to DC, by default doesn't allow pre win2k clients at the network.. Show if you didn't change the default option during dcpromo go to active directory users and computers admin tool and at build in acounts locate the pre win2000 clients Add to this as a member the...

Yes you must run it They are swithes of adprep command which is located at the i386 folder of the net server cd

From group policies you must deactivate desktop changes

Yes 2k envioroment isn't supported.. Only xp with SP1 I thing that microsoft is going to support onl xp platforms at the future.. The new office will only work at XP, Net server and w2k!!!

Something wrong with your config,, win2k client works fine with .net server

You can and 3718 isn't the final version

It does work this is for sure, check out your config of TS

Whel you can be a mumber of an other AD domain if you configure your AD domain as a child domain to an existing AD