Malkosha

When the compnay I worked for split into 2 groups I had to move my users to another domain. I copied the current domain profile to the administrators profile. I then changed domains on the PC, logon as the new user on a new domain, then copied the profile back. This gave me: Mapped drives, printers, desktops etc. I created a new outlook PST and imported the settings from the old one which was on their drive. I then copied favorites. I lost the cookies of course. I had to reconnect the mapped drives, becuase the user had changed, but it was easy considering the drives were already there ... they just didn't have permission to access them. This saved me a ton of time, and I spent about 10min's per PC, depending on how big their PST was (if you don't watch them, they will grow ... one user had a 450meg PST). Another cleaner way is to work with roaming profiles, but that would only be good for you in a future change. Luck!!

I'll take a stab at this one. What you could do, is setup a new local account, on the workstation. Then copy the current user profile over to the new profile. This should preserve most of the settings. Later, when the user is up, copy the profile back. You will have to re-map any drives since the SID has changed, but the drives all already there so no problem. I'm not sure about cookies or fav's but they may also work. Luck

Trying to keep this short, We have a main office with a PDC and BDC, along with 6 locations that have a BDC. We use cisco routers with NAT enabled. All are running NT4. We upgraded the servers at the main office to Win2k. DDNS was a learning experience, but we got there. When we tried to upgrade the remote BDC to Win2K, we couldn't establish the trust needed with the Win2K servers at the main office. We played with DNS and still couldn't get it. We ended up calling MS and they said that the problem is that Win2K can't/won't validate or establish trusts through NAT. In other words, as long as NAT was in place internally, there was no way we could run a Win2K network. Has anyone else run into this problem, or better yet, is there a workaround? I would hate to re-design the entire network in order to upgrade to Win2K. Thank you!

Thanks but, it is static. What seems to be happening is that DNS asigns the RAS address to a DNS address. This confuses the NT4 machines. Oh .. I forget one important point. This only affects machines that are not Win2K or XP. That is, it only affects Nt4 clients and Win95/98 clients. **edited for spelling errors worse than usual **

We upgraded our DC's from NT4 to Win2K. Everything seems to work ... except for one little problem. Our RRAS is on one of the DC's, and when ever someone RAS's in, they get a DHCP address. This address is then picked up by DNS, and the DC is assigned that address. Of course, all connections to the DC are lost. By deleteing the DNS entry and stop/start the RAS service, the problem is fixed ... until the next time someone RAS's in. Anyone have a clue how to fix this?

Thanks clutch. We had a similar idea, but no where near as detailed or complete as yours, and we left a few things out . We will give it a go! Once again, thank you

I need a little help with Migration from NT4 to Win2k. We have a main office which hosts the Primary and Backup Domain controllers. We also have a WAN with 6 offices that contain BDC's. Each office has a router and at the main office there is a PIX firewall between the main office and the outside world. All of these are running NT4. We upgraded the main office's BDC to Win2K server, made it the PDC and used AD and DNS. The original PDC will be upgraded in a day or so, and we will then convert that into its original function as a PDC. We also want to upgrade the WAN locations but have run into a question. We have WINS working great at the moment, and replicate it one way so the NAT translation doesn't hose the PDC WINS database up. The main office is set at 172.30.x.x while the WAN is set at 192.168.x.x. The WAN computers communicate with the main office using 172.17.x.x as the translated address. The PIX is set so no one can ping the PDC from the outside. What can we do to allow DNS to handle name resolution (and replicate it) without getting the servers all confused? We had this problem with WINS, and solved it by only replicating it in a single direction, create Static mappings, then turnning on MIGRATION (To prevent static mappings from being overwritten). Can this be done with DNS? Thank you!!

Do they make PCMCIA video cards? It would seem that a market would exist for one. While my ATI rage mobility works OK, it would be great to be able to upgrade the video card for higher graphics performance.

Try getting rid of the mapped drives ... they should not be needed. Also get rid of the /v (I assume verbose) and replace it with /e which answers yes to all questions) Nothing to lose heh!

Thx!! I'll give it a try .... changing the binding order that is. I have an A20P thinkpad that uses a pass through port replicator, which of course causes me no problems at all. I wonder what Dell is thinking sometimes when they do some of the things they do. For instance, they have the classic "IBM nub" for mouse control but also have the touch pad and 2 sets of mouse buttons just underneath it. At first you would think "hey great! I get options here" but in truth, while you can disable either device (but not the buttons), if you choose the nub then its easy to mistakenly hit one of the "mouse buttons" usually at the wrong time. Thx again!

I just installed a new Dell Laptop for one of the company exec's. It has an onboard NIC and it worked fine. However, when his Port replicator came in, I installed it and it had its own NIC card. This was no problem for Win2K of course and the card was found a recognized. We use DHCP on our domain, which gives the IP, gateway, DNS servers and WINS. This is an NT4 PDC. The first card had no problem (LAN1 under network/properties)getting a WINS address and therefore had no problems connecting to mapped drives. The second card (in the PR, called LAN2) only gets an IP address and can't resolve names ... no mapped drives etc. When I run IPCONFIG, the 2nd card shows no WINS address. When I try to connect to mapped drives using UNC names, I get the device is in use error. While I would love to just disable one of the cards and let it go (probably the internal one) the user needs it for going to different WAN sites and logging on. Any idea how I can solve this issue? I guess I could give that card a static IP but thats not a popular idea around the shop. Any ideas? THX!!

I updated the drivers for my V3 and they installed perfectly. So did the tools. Everything seems to work great. Get the latest drivers from 3dfx and let it rip.

Thanks I will!!

the problems with Voodoo3 cards that the other betas had? The drivers released from 3dfx didn't load before. While this may be a driver problem and/or a 3dfx problem it seems to me that forcing a rewrite on drivers every time a new system comes out is poor quality control and a lack of vision.

I beat ya to it!! I layed down RedHat 7 and its faster, comes with a couple of GUI's that rock the house and they have no intention of forcing people to "activate" a damn thing. Everytime MS puts out a new OS its the same thing ... need newer/powerful hardware, the drivers are not backward compatible and they charge a fortune. RH7 is the best OS I've ever put on, bar none. With KDE and Gnome pre-installed managing your system is a piece of cake. The GUI's are also skinable and it runs with yesterdays harware just fine. I have Q3 up right now and the drivers for my Voodoo3 work outstanding. MS screwed up with this activation thing and it will be interesting how they will handle it over the long haul. If you think you have problems now ...