Search results for query: *

If the win2K server is in native mode, than you can't use a NT4 BDC or PDC it simply won't work. But if you have a win NT4 domain, and you upgrade one of the servers to win2K then they can work together as long as the domain isn't switched to native mode. regards asteriks

Hi, I think you should check you binding order. In the property of network you can choose advanced and than advanced settings, try changing the binding order and put the first addaptor on top maybe this can solve your problem. kind regards,, asteriks

Try to make yourself the owner of the directory, and deleting it like this. If this doesn't work, you can try to boot the server into save mode, than you should be able to delete the directory! Another thing you can do is find out which process is using the folder => stop or kill the process...

eriksond, from where do you run you usrmgr? did you start it on de PDC, another DC or from a workstation, were you installed the network clients??? If the problem resides on the PDC, than i think your SAM database is corrupted. greetings Asteriks

you must add a rule in the proxy server that allows clients to use the ftp protocol. How this is done depends on the version of proxy server. In version 2 you ask the properties of the winsocks proxy, and there in one of the tabs you can configure that they are allowed to handle ftp traffic...

We still use kixstart, it remains a graet product and works like it should!

Katriona, Is the server a member of the domain? If he is a member of the domain, maybe you can check your wins configuration. If the server does not has an address configured for a wins server, it wil not find a domain controller and display you that message: "The domain controller for...

search the client for files with the extention pwl, this files contain the users passwd. If you delete these files, all win 98 passwds will be gone. The next time you logon, you don't enter a win98 passwd anymore and afterwards, he will not ask for passwords again.

the standard IIS installation for NT is V3 I think, but in SP3 it is update to IIS V4, so which is the correct version, i don't know, but I suggest using V4 or V5 which is delivered with win2k greetings Wouter

The problem is solved in the mean while!!! Some of the PC were not correctly installed and the winsocks drivers were not the latest. Updating too winsocks v2 solved the problem in most cases. regards Wouter

OK, Now, i'm not completly with you, the problems that you have, is it on the server site, or on the client side. Is it terminal server client that doesn't detect the modem of your laptop or is it the server that doesn't see the modem? wouter

i was thinking maybe, due to the fact of the reconfiguration of the AD, The SID of the user accounts changed and maybe that was the reason why it wasn't working anymore, that's why maybe the localadmin account still has the necessary user rights to do this. Something else, can you check under...

did you use the local admin account or a account that is a member of the domain admin groep? regards Wouter

hi, yes, it should be perfectly possible. As a mather of fact, there are some different possibilities to do this. 1) You can configure RRAS to manage dial in users, so you can dail in and than you can use the home network as if your were directly connected to it. 2) You can use Terminal...

normally, NT keeps profiles stored on the server when the users logon to these server, when you upgrade the server to windows 2000, the profiles will be upgrades as wel. So i think that you don't have to copy all of the profiles to disk. If there is no copy on the server, maybe you can set-up...

hi, Is the modem allready installed and configured correctly on the system and are there no conflicts in the configuration?? Wouter

We have a routed environment, and all switches are configured as dhcp relay agents for their subnet! We have two meta ip dhcp servers that run in fail over mode with 900 scopes defined on it. Now the problem is that the dhcp address assignment works fine for windows 2000, windows NT and...

When i try to start the scsichanger service, i get the following message: "could not start the scsichanger service on \\servername error 1058: the specified service is disabled and cannot be started" You can find this service under devices in the control pannel and it is used to...

It is easy to connect through a telephone line. If your connection drops, the status on the TS will be disconnected. All your applications remain open, and when you reconnect you get the stuff that you were working on again. To make it work you should go to terminal server configuration...

are there any port restrictions implemented? Wouter Leysen