aquarius

Hi! This is an old thread now, but I thought I'd offer another solution that might help in the wireless scenario we were discussing. If you turn off "Windows XP Professional Fast Logon Optimization", Windows XP will wait for network to be available, and run login-tasks synchronously instead of asynchronously, but the network thing is interresting. It can be deployed using GPO, but you can test it with the local policy; Run gpedit.msc Find "Computer Configuration\Administrative Templates\System\Logon\Always wait for the network at computer startup and logon" More info: KB305293 Cheers!

FORM FORK DORK DARK BARK PARK PART FART FAST VAST VASE BASE CASE CAST CART DART DARE CARE FARE MARE MALE TALE SALE SOLE SOLD MOLD TOLD GOLD FOLD FOLK FILK MILK MILE MALE MATE MAZE DAZE DOZE DONE NONE NOSE POSE POLE PORE MORE SORE SURE PURE PARE RARE RACE FACE FACT TACT PACT PAST FAST CAST CASE BASE VASE VISE VISA VESA VEST BEST JEST TEST TEAT MEAT NEAT SEAT SEAR FEAR NEAR DEAR BEER BEEP PEEP PEER LEER LEEK LEAK LEAP LEAN BEAN BEAD LEAD LOAD LORD CORD FORD WORD WOOD GOOD GOAD GLAD CLAD CLAP SLAP FLAP FLAT FLAX FLAY FLAB FLAK FLAW FLOW BLOW BLOT PLOT SLOT SLOP SLOB BLOB BLUB CLUB CLUE GLUE GLUG GLUM PLUM PLUG PLUS FLUS FLUX FLEX FLEE FLEE FREE FRET FRAT BRAT BRAN BRAG DRAG FRAG FRAY PRAY PREY TREY GREY GREW BREW CREW CROW BROW GROW GLOW GLOB SLOB SLAB STAB STAY STAR STAP STAG STOG STOP STEP STEW SHEW PHEW CHEW WHEW WHEN THEN Yes, but is it better THAN some other threads?

FORM FORK DORK DARK BARK PARK PART FART FAST VAST VASE BASE CASE CAST CART DART DARE CARE FARE MARE MALE TALE SALE SOLE SOLD MOLD TOLD GOLD FOLD FOLK FILK MILK MILE MALE MATE MAZE DAZE DOZE DONE NONE NOSE POSE POLE PORE MORE SORE SURE PURE PARE RARE RACE FACE FACT TACT PACT PAST FAST CAST CASE BASE VASE VISE VISA VESA VEST BEST JEST TEST TEAT MEAT NEAT SEAT SEAR FEAR NEAR DEAR BEER BEEP PEEP PEER LEER LEEK LEAK LEAP LEAN BEAN BEAD LEAD LOAD LORD CORD FORD WORD WOOD GOOD GOAD GLAD CLAD CLAP SLAP FLAP FLAT FLAX FLAY FLAB FLAK FLAW FLOW BLOW BLOT PLOT SLOT SLOP SLOB BLOB BLUB CLUB CLUE GLUE GLUG GLUM PLUM PLUG PLUS FLUS FLUX FLEX FLEE FLEE FREE FRET FRAT BRAT BRAN BRAG DRAG FRAG FRAY PRAY PREY TREY GREY GREW BREW CREW CROW BROW GROW GLOW GLOB SLOB SLAB STAB STAY STAR STAP STAG STOG STOP STEP STEW SHEW PHEW CHEW WHEW That means it's time to WHET the appetite for more words?

FORM FORK DORK DARK BARK PARK PART FART FAST VAST VASE BASE CASE CAST CART DART DARE CARE FARE MARE MALE TALE SALE SOLE SOLD MOLD TOLD GOLD FOLD FOLK FILK MILK MILE MALE MATE MAZE DAZE DOZE DONE NONE NOSE POSE POLE PORE MORE SORE SURE PURE PARE RARE RACE FACE FACT TACT PACT PAST FAST CAST CASE BASE VASE VISE VISA VESA VEST BEST JEST TEST TEAT MEAT NEAT SEAT SEAR FEAR NEAR DEAR BEER BEEP PEEP PEER LEER LEEK LEAK LEAP LEAN BEAN BEAD LEAD LOAD LORD CORD FORD WORD WOOD GOOD GOAD GLAD CLAD CLAP SLAP FLAP FLAT FLAX FLAY FLAB FLAK FLAW FLOW BLOW BLOT PLOT SLOT SLOP SLOB BLOB BLUB CLUB CLUE GLUE GLUG GLUM PLUM PLUG PLUS FLUS FLUX FLEX FLEE FLEE FREE FRET FRAT BRAT BRAN BRAG DRAG FRAG FRAY PRAY PREY TREY GREY GREW BREW CREW CROW BROW GROW GLOW GLOB SLOB SLAB STAB STAY STAR STAP STAG STOG STOP There's still many "trival" words to come up with, so STEP up to the challenge! (Hope noone is entering the same word while I write this, though I have no problem sharing credit with a Doe

FORM FORK DORK DARK BARK PARK PART FART FAST VAST VASE BASE CASE CAST CART DART DARE CARE FARE MARE MALE TALE SALE SOLE SOLD MOLD TOLD GOLD FOLD FOLK FILK MILK MILE MALE MATE MAZE DAZE DOZE DONE NONE NOSE POSE POLE PORE MORE SORE SURE PURE PARE RARE RACE FACE FACT TACT PACT PAST FAST CAST CASE BASE VASE VISE VISA VESA VEST BEST JEST TEST TEAT MEAT NEAT SEAT SEAR FEAR NEAR DEAR BEER BEEP PEEP PEER LEER LEEK LEAK LEAP LEAN BEAN BEAD LEAD LOAD LORD CORD FORD WORD WOOD GOOD GOAD GLAD CLAD CLAP SLAP FLAP FLAT FLAX FLAY FLAB FLAK FLAW FLOW BLOW BLOT PLOT SLOT SLOP SLOB BLOB BLUB CLUB CLUE GLUE GLUG GLUM PLUM PLUG PLUS FLUS FLUX FLEX FLEE FLEE FREE FRET FRAT BRAT BRAN BRAG DRAG FRAG FRAY PRAY PREY TREY GREY GREW BREW CREW CROW Gotta sweat to your BROW

I'm longing for the GREY Havens...

FORM FORK DORK DARK BARK PARK PART FART FAST VAST VASE BASE CASE CAST CART DART DARE CARE FARE MARE MALE TALE SALE SOLE SOLD MOLD TOLD GOLD FOLD FOLK FILK MILK MILE MALE MATE MAZE DAZE DOZE DONE NONE NOSE POSE POLE PORE MORE SORE SURE PURE PARE RARE RACE FACE FACT TACT PACT PAST FAST CAST CASE BASE VASE VISE VISA VESA VEST BEST JEST TEST TEAT MEAT NEAT SEAT SEAR FEAR NEAR DEAR BEER BEEP PEEP PEER LEER LEEK LEAK LEAP LEAN BEAN BEAD LEAD LOAD LORD CORD FORD WORD WOOD GOOD GOAD GLAD CLAD CLAP SLAP FLAP FLAT FLAX FLAY FLAB FLAK FLAW FLOW BLOW BLOT PLOT SLOT SLOP SLOB BLOB BLUB CLUB CLUE GLUE GLUG GLUM PLUM PLUG PLUS FLUS FLUX FLEX Allmost ready to FLEE...

@ethanmcf: I know you have told us before, but I'm just thinking: is it only the router which is far away from the offices? Is it possible to wire the clients to the serverroom, and use a wireless bridge from there to the router? Do they only use cell phones or are there telephone lines that can be used? If the net is not several decades old, it might be be Cat5 which is OK for 100MB ethernet. A CAT5 cable often has 4 pairs, of which the PC needs 2 (100MB max) and 2 left that you can use for a telephone and a spare. (In norway and europe I think, at least with RJ45 sockets, usually have all 4 pairs are connected at the socket even for 1 telephone outlet, to facilitate future expansions.) Then you'd have wired access to the servers and DC, and only the router would be connected via the bridge. Either that or use nmX.Memnoch's tip. Users might find it irritating though, if they have to re-login if they where too fast and stuff like that.

You must "Allow Windows to handle the wireless connection" instead of the vendor driver, This way the network starts in time to let you log in with it... Some WLAN cards may not let you do this, and Windows XP or later is required on the client. Anyway, that is not a problem with the DC.

Allso, if you have other 2k3/2k servers in the domain (defined as domain servers), I think they will cooperate as Backup Domain Controllers should the DC fail. Still, I would treat the Domain Controller as a critical component, a dedicated server, and no multiboot or other stuff that complicate things. Make good backups!! Keep it as simple as possible, it will become complex enough soon! Don't install any kind of application or code that does not pertain to it's role as a Domain Controller!!! (goes for any kind of server) Regards, )chicken fish(

Sure, use the other router! Just eliminate the wireless for the test. It must be set up with DHCP and the necessary stuff of course. If it still fails with the test router you can begin searching for causes other than WiFi. Basic networking first. (Remember that ping might be blocked by client firewalls) Time to log out for me, good luck!

Hello! The DC is just another device in that respect, just set it up with automatic IP, gateway, DNS as you would any laptop. You don't need to associate the DC with the router. I really think you should move the DC and a test computer to the router room (or within the reach of 10m cables to test it! When adding a client to the domain, and logging on to a client with a domain user works using wired LAN, then move it to the wireless net. Keep it simple!

Hello! Warning: No step-by-step here, just a few comments! From what I read in your post, the server is not online the whole time, and wireless might have glitches or whatever, so I would use the DHCP capabilities of the router instead of the DC. Generally, give wired connection to the DC and as many computers as possible. Make sure encryption is in place. WPA, not WEP. (Configure the router. recent routers have a lot of capabilities in this area!) I recommend giving the server(s) static IP address. The router is the default gateway, firewall (if it can do it, enable it!), DHCP-server. The DC is the server with the user accounts database and stuff like that. You join your servers to the domain, and give permissions to domain users. DC has nothing to do with internet access! The DHCP parameters should give the clients the proper settings. Adding clients to the domain: Wireless or wired connection should not matter. (to be onest, I havent tried a wireless DC myself, and by the number of replies you are getting... not many others either :-) On the client, right click My Computer/Properties/Computer Name/Change and join the domain. Use a Domain Administrator account defined on the Domain Controller to authorize the add. If this doesn't work, I strongly feel you have other issues than the wireless scenario. You can easily eliminate the wireless as a cause by connecting the computers (DC + a test client) with a normal switch and ethernet cables to test the domain. Of course, if it doesn't work while wired, it will not when wireless either! If you give more details, you might get better help! Good luck!

Hello! If you can print it, then you can make PDF PDFCreator (A SourceForge project, free) Then File/Print/select PDFCreator (Or maybe you have another PDF-printer allready) Of course this will not save any of the invisible message headers (server stamps, Sent/received etc.) For backup I would still use the database. Note: If the mail has attachments, using PDFCreator you can add these to the same PDF: 1. Print the mail, click "Waiting" instead of "Save" in the PDFCreator dialog, to tell it to wait for more jobs. 2. Print attachments. These will be placed in the PDFCreator queue, waiting for further actions. 3. When all attachments are in the queue, select all and then click the "Combine" button. (At this moment, the PDFCreator window might be minimized to the system tray) 4. Click the red printerbutton to resume the operation, and click Save in the PDFCreator dialog. The result will be one PDF with the mail and attachments. Cheers!

Hi! I promised to check out the keyboard state in a multiuser environment, i.e. with several sessions running. Only tested shift key state. Remote PC was Windows 2000 SP4 Tested for VK_SHIFT (Any shift key, left or right) VK_LSHIFT (Left shift key) VK_RSHIFT (Right shift key) Citrix on NT4 and Remote Desktop on Windows Server 2003: Remote users VK_SHIFT, VK_LSHIFT and VK_RSHIFT works, and no "leak" from the console or other remote sessions. Netmeeting Remote Desktop: (W2K/XP) (Which is not very multiuser, it just takes over console and disables local input) Remote user shift is detected (VK_SHIFT), but it does not detect the difference between the Right or Left shift keys in this scenario, i.e. a test for VK_LSHIFT or VK_RSHIFT would not work. TightVNC: (W2K Server) Same as Netmeeting. You can enable local input in VNC, in which case both remote and local user is detected, as should be expected. Cheers!