melissasue
Members-
Content count
14 -
Joined
-
Last visited
Never
Everything posted by melissasue
-
Hi, I'm hoping someone can shed some light on a little problem that I am experiencing. I have just installed XP Pro and have found the domain being SUPREME, no worries there. I have been able to map a network drive to the server logging on as Administrator to the local machine. This is where my problem comes in. I have a user name on the Server called monitor which my NT 4.0 Workstations can access no worries. When I try to log onto the server through the XP Pro machine using the user name monitor, a message comes up saying that it can't find the local profile, it can't create a roaming profile but it will create a temp profile, settings cannot be saved once logged off the server. I have then gone back into the local machine as administrator, created a user by the name of monitor but there is still no success there. All my computers have a static IP address, I have set an IP Address for this computer, plus enabled the DNS server and put that IP Address in too. Does anyone have any suggestions that could be the problem here. I would be very grateful for suggestions/advice etc. Have a lovely evening. Melissa Sue
-
Hi, I'm hoping someone can shed some light on a little problem that I am experiencing. I have just installed XP Pro and have found the domain being SUPREME, no worries there. I have been able to map a network drive to the server logging on as Administrator to the local machine. This is where my problem comes in. I have a user name on the Server called monitor which my NT 4.0 Workstations can access no worries. When I try to log onto the server through the XP Pro machine using the user name monitor, a message comes up saying that it can't find the local profile, it can't create a roaming profile but it will create a temp profile, settings cannot be saved once logged off the server. I have then gone back into the local machine as administrator, created a user by the name of monitor but there is still no success there. All my computers have a static IP address, I have set an IP Address for this computer, plus enabled the DNS server and put that IP Address in too. Does anyone have any suggestions that could be the problem here. I would be very grateful for suggestions/advice etc. Have a lovely evening. Melissa Sue
-
Hi, Im wondering if anyone could tell me how I can synchronise NT Workstations 4.0 to NT Server 4.0 when workstations start up. Our organisation records live audio from court proceedings so having all workstations displaying the same time as the server is quite important. I look forward to hearing from anyone. Regards Melissa Sue
-
Synchronise NT Workstations time to NT Server 4.0 on start up
melissasue replied to melissasue's topic in Software
Thanks for that. But how do I go about getting a copy of this resource kit? It is exactly what we need. -
Hi, Im wondering if anyone could tell me how I can synchronise NT Workstations 4.0 to NT Server 4.0 when workstations start up. Our organisation records live audio from court proceedings so having all workstations displaying the same time as the server is quite important. I look forward to hearing from anyone. Regards Melissa Sue
-
Hi, Im wondering if someone could help me. I work for an organisation that records live audio to be transcribed. The audio is captured using a programme called FTR and then transferred through to the server from the local machines. What I need to do is get 8 win 98 and 7 NT Workstations to have the same time synchronisation as the server. I have found a file called Time.bat and I am testing on my computer and have put it into my start up folder, it seems to be working okay but unfortunately I have to actually close the box once the script or .bat has run (excuse the language, Im not that good at this sort of stuff). I have actually copied what is in the file which is below: net time \\server /set /yes What I am asking for if anyone knows out there what information I can put into this .bat file to actually automatically close the box down once the script has run. Again, I would be very grateful for all information. Thanks very much. Regards Melissa Sue
-
Originally posted by Wilhelmus: Quote: Hi. Quote: ... What I am asking for if anyone knows out there what information I can put into this .bat file to actually automatically close the box down once the script has run. ... Modify your batch file to this. Quote: net time \\server /set /yes exit The "exit" exits the command-line process when the batch file terminates. My gawd, is that it? Thank you very much for that. I will give it a go and I will let you know. Once again, thanks Im very grateful.
-
Hi, Im wondering if someone could help me. I work for an organisation that records live audio to be transcribed. The audio is captured using a programme called FTR and then transferred through to the server from the local machines. What I need to do is get 8 win 98 and 7 NT Workstations to have the same time synchronisation as the server. I have found a file called Time.bat and I am testing on my computer and have put it into my start up folder, it seems to be working okay but unfortunately I have to actually close the box once the script or .bat has run (excuse the language, Im not that good at this sort of stuff). I have actually copied what is in the file which is below: net time \\server /set /yes What I am asking for if anyone knows out there what information I can put into this .bat file to actually automatically close the box down once the script has run. Again, I would be very grateful for all information. Thanks very much. Regards Melissa Sue
-
Hi, I am hoping that someone would be able to help me. My query will most probably not make much sense as I am not that knowledgable with networking and with NT Servers. I work for a transcription company where we transcribe live audio from the courts. A couple of weeks ago our NT Server fell over, it was over five years old. A new motherboard, cpu and power supply was installed, data was copied off the hard drive, NT reinstalled and then the data copied back on to the hard drive. Once the server has had its extreme make over I hook it back up to the network and can be found on the network. Now this domain has 7 machines that log on to the server, each machine is Windows NT. Each machine logs in as monitor onto the domain, but the following error message comes up: "A domain controller for your domain could not be contacted. You have been logged on using cached account info. Changes to your pofile since you last logged on may not be available". My question is, what does this mean? I have gone through help and can find nothing about this, or I could be looking in the wrong areas and how do I fix this little problem? If anyone could help me, I would be so grateful. Thanks and regards Melissa Sue
-
Thanks everyone for your help and advice....it worked. I'm extremely happy. Regards Melissa Sue
-
Sorry guys, Im getting a bit confused with how to reply to threads etc, pls bear with me. Thanks mnas, this is exactly what has happened. To reconfigure the clients to the new domain, even though it is named the same, do i have to disconnect the network drives that I have mapped, then go into properties take the clients off the workstation, place them in a gamon workgroup, restart the machine. Once I have logged back go back into properties then reconnect the client to the magistrate domain, do I then create an account on the domain once I have typed in the domain name? And if I do, I need to actually create the clients name on the server first, yeah? Thanks to everyone for your help, I have learnt quite a lot this morning. Regards
-
This is exactly what has happened. Except the domain is called MAGISTRATE. Let's say we have a domain with an NT4 PDC called PDC1 hosting a domain called MYDOMAIN and a few clients named CLIENT1, CLIENT2, etc... Then one day the PDC fails and we have no backup of the account database. So a reinstallation of the OS follows and we set the server up as a PDC for a domain called MYDOMAIN. Now this is important: Although the domain we created is named exactly the same as the old one it is NOT the same domain. There is a lot of information behind that name. A lot of unique identifiers are generated when the domain is created. The Netbios name MYDOMAIN is used kind of like an alias for something much more complex. So, our client machines still think they are connected to a domain called MYDOMAIN. But, they generate messages saying that they are unable to contact a PDC for the domain MYDOMAIN. Why is that? There IS a domain called MYDOMAIN! I set it up myself! I know it! Now, as stated above. It is NOT the same domain anymore. The new PDC doesn't know anything about the old one. What we need to do is reconfigure the clients to belong to the new domain. This is done by removing them from the old domain and put them in a workgroup. And then connect them to the new domain. When a workstation (client) connects to a domain controller the DC creates a computer account for the workstation. This makes it possible for the client to ask the DC for information needed to process a login. To do the above do I need to also create accounts on the server first, then go into local machines switch them to a workgroup, restart the computer, then go back and connect them to the magistrate domain and then create an account to the server from the local machine. I would be very grateful for your advise. As before, correct me if I'm wrong.
-
Hi, I am hoping that someone would be able to help me. My query will most probably not make much sense as I am not that knowledgable with networking and with NT Servers. I work for a transcription company where we transcribe live audio from the courts. A couple of weeks ago our NT Server fell over, it was over five years old. A new motherboard, cpu and power supply was installed, data was copied off the hard drive, NT reinstalled and then the data copied back on to the hard drive. Once the server has had its extreme make over I hook it back up to the network and can be found on the network. Now this domain has 7 machines that log on to the server, each machine is Windows NT. Each machine logs in as monitor onto the domain, but the following error message comes up: "A domain controller for your domain could not be contacted. You have been logged on using cached account info. Changes to your pofile since you last logged on may not be available". My question is, what does this mean? I have gone through help and can find nothing about this, or I could be looking in the wrong areas and how do I fix this little problem? If anyone could help me, I would be so grateful. Thanks and regards Melissa Sue
-
Thanks for replying so quickly. Yes, the NIC is onboard. Regards Melissa Sue