valter

Yes, enable Always wait for the network at computer startup and logon GPO located in Administrative Templates\System\Logon ... this should prevent users getting "Press CTRL-ALT-DELETE" dialog before workstation communicate with AD ...

Did you authorize your DHCP server? Try using ipconfig commands and see what error you will get ..

Using RIS ... check this out http://bink.nu/Forums/ShowPost.aspx?PostID=1684 be sure to create answer file that will NOT auto partition your hard disk ... then you MUST do it manualy

WininstallLE is cool simple stuff, the ONLY problem is that before and after snapshots must be taken on clean machine ... means only Windows installed ... any extra software will create additional keys in the registry that you WILL later import into another computer ...

GO to MS IE website and download installation wizard ... once done, open Run dialog and type the following "C:\Folder\ie6setup.exe" /c:"ie6wzd.exe /d /s:""#E" make sure you replace word Folder with actual location where ie6setup.exe is located ... this will download full installation for IE6 in the aforementioned folder and then you take it from there ...

.htaccess file works ONLY with Apache and not with IIS

When logged onto workstation, open cmd and type "gpupdate /force" and see what happens if snothing happens with your wallpaper, then type gpresult and look for the following .. 1. If the policy you try to apply is in User Configuration then USER SETTINGS -------------- CN=Test TU. User,CN=Users,DC=IT,DC=TEST,DC=LOCAL Last time Group Policy was applied: 5/17/2005 at 7:31:00 AM Group Policy was applied from: sun.IT.TEST.LOCAL Group Policy slow link threshold: 500 kbps Applied Group Policy Objects ----------------------------- Default Domain Policy 2. If the policy you try to apply is in Computer Configuration then COMPUTER SETTINGS ------------------ CN=IT1,OU=IT Computers,DC=IT,DC=TEST,DC=LOCAL Last time Group Policy was applied: 5/17/2005 at 7:24:45 AM Group Policy was applied from: hermes.IT.TEST.LOCAL Group Policy slow link threshold: 500 kbps Applied Group Policy Objects ----------------------------- DNS Settings Software installation Default Domain Policy The following GPOs were not applied because they were filtered out ------------------------------------------------------------------- Local Group Policy Filtering: Not Applied (Empty) here you can see what policies and when they were applied ...

You have a problem with replication. There can be many reasons for the replication problem, but the most common is multihomed domain controllers (DC with more than 1 NIC) .... install Windows 2000 support tools and use replmon.exe to monitor replication and possibly pinpoint the problem ... if you have a multihomed DC, remove one of the network cards and then try to reinitiate replication ... once you get replication up and running the rest of the story is piece of cake ... as far as migration is concerned, I would rather upgrade existing working w2k domain to 2k3 ... if you decide to upgrade instead of migration, cosult this article http://support.microsoft.com/default.aspx?...kb;en-us;325379

Maybe you want to check this ... http://support.microsoft.com/default.aspx?...kb;en-us;898060

I see you're not too familiar about networks so U might not even know if it is possible. Anyway, U connect different networks with different IP ranges(subnets) ex. Network 1: 10.0.0.1-10.0.0.255 Network 2: 10.0.1.1-10.0.1.255 Network 3: 10.0.2.1-10.0.2.255 Network 4: In my case ADSL, is where U also set DNS for Internet sharing to work on CLIENT computers. I believe U get the picture. The problem is connecting all these networks together, so they all have Filesharing and Internet sharing. And here comes Winroute, which does precisely that. I've read on multiple sites that an option BRIDGE CONNECTION is in effect for this kind of network but I'm not sure if that is true... So if any1 have any else ideas please let me know. <{POST_SNAPBACK}> I don't think you understod my post, anyway what I was aiming at is that you CAN'T use 2 NICs on the same network with the same IP range, but since you want to cacth on the terminology, let me rephrase it. NO IT'S NOT POSSIBLE TO USE 2 NICS ON THE SAME NETWORK SEGMENT WITHIN THE SAME IP RANGE! (if this look like I'm shouting, yes I am) Hope you got it better this time. Anyway, stupid idea, having 3 PCs on 3 different ip rangs just because you hate switches ... maybe you should just start playing with some other less complicated toys

Hard core problem solving doesn't work these days .... it's lot easier just to restart OS then to look for the cause unless it's repeated problem ... anyway, I doubt that you will find any1 who can give you a hint why this happened

I don't think so, anyway you should be happy that it's possible at all, before gpmc was introduced export and import was not possible at all at least not in that manner

Long story shot, no it's not posible, and I just wonder how did you made it under win2k because there will be an error as soon as you use same network on 2 or more different NICs

@1 Check white paper from here @2 Only if you use 2 different networks and if your server is not DC. If your server is DC, disable the unused NIC because it can just create problems. MS doesn't support multihomed DCs

Have you tried to manually replicate AD information? If not, install Windows support tools and use replmon.exe to monitor replication and if possible verify that network hangs during domain information exchange

If you run a Active Directory, then you MUST run a DNS, because AD can not work without DNS server ... collision means that two or more nodes sends packages at the same time ...

When you install IIS, there you can pick if you want TSweb client or not, and regarding port, if you have change it to lets say 1234 then you should configure your forwarding to forward RDP request to port 1234

Just a stupid question, have you install terminal services web client at all?

I didn't see that you run Active Directory on your server, so you can make a little test, get another network card, just a simple PCI NIC and install it in the PowerEdge, disable the onboard one and see if the same thing happens with that one if it doesn't then call DELL support so they can replace your server board if it does, try either updating the NIC driver (from DELL's website), or/and reinstall TCP/IP

Just because VBS can do more stuff than batch file can ... just for a start to map user home folder os much more complicated using batch file (writing it by hand and not third party program) ... and again, that's my personal reccomendation

Sure it does

Did you try ERD Commander?

No due to the security issues ...

I would strongly reccomend not to use batch files as logon scripts, but use vbs ... anyway, the port that you map on the workstation using logon script doesn't matter, as long as there is no local printer installed and connected to lpt1, and yes you can map usb printer that is connected on the server, to lpt1 port on the workstation ... here is an example of printer connection using vbs Dim net Set net = CreateObject("WScript.Network") net.AddWindowsPrinterConnection "\\Server\HPLJ4", "HPLJ4" word Server replace with your actual server name, HPLJ4 is the name of the port on the server this is how you set default printer using vbs Set net = CreateObject("WScript.Network") net.SetDefaultPrinter "\\Server\HPLJ4" if you wonder how to map drives using vbs here is an example Dim WshNetwork Set WshNetwork = WScript.CreateObject("WScript.Network") WshNetwork.MapNetworkDrive "Q:", "\\Server\SharedFolder" and to map user home folders use this Note:you must remove home mappings from user properties in Active Directory users and Computers if any is there![b/] ' VBScript. ' Mapping user home folder on the server Dim oNet, sUser Set oNet = CreateObject("Wscript.Network") sUser =oNet.UserName oNet.MapNetworkDrive "P:", "\\Server\" & sUser The map user home folder should actually be the first lines of the code in the script so it looks like this ' VBScript. ' Mapping user home folder on the server Dim oNet, sUser Set oNet = CreateObject("Wscript.Network") sUser =oNet.UserName oNet.MapNetworkDrive "P:", "\\Server\" & sUser Dim WshNetwork Set WshNetwork = WScript.CreateObject("WScript.Network") WshNetwork.MapNetworkDrive "Q:", "\\Server\SharedFolder" Dim net Set net = CreateObject("WScript.Network") net.AddWindowsPrinterConnection "\\Server\HPLJ4", "HPLJ4" Set net = CreateObject("WScript.Network") net.SetDefaultPrinter "\\Server\HPLJ4" Remember to save the script as vbs file (*.vbs)

Can't tell you why, but it looks like a problem on your Win2k3 domain ... anyway, the painless process you might wanna take would be to upgrade your Win2k domain to Win2k3 and skip process of migration that is real pain in the neck ... anyway, if you decide to upgrade your domain instead, let me know so I can find some links that would help you out