ICTCity

if you don't redirect profiles on a server or a network share... yes. Well, I don't think you will have troubles, the error simply indicates that a computer cannot be verified with its SID. Unless people are able to login with their account, you can ignore this problem. If I'm not wrong, SID are used to avoid the entire authentication process. Anyway, if this fails, Windows will try to use user's credentials. I'm not sure... Anyway, this problem is because your DC has created another DB with differents SIDs.

I mean, try with one pc... just to see if this resolve your problem.

Oh well, try to un-join that pc from domain. Delete the COMPUTER's entry from AD, then re-add the pc and your problem should be solved.

Hi, Before going further, open task manager > RESOURCE MONITOR. You have 5 TABS. First of all on OVERVIEW you have 4 bars and on the right there's a small blue square which indicates the percentile of usage. Take a look if there's something high (when I say high, I mean >= 50%). This EXCEPT the network. For network you have to determine first your network's speed. Let's say you have a 5M connection, if you see the 5% on the blue square, it means your bandwidth is full! (5% of 100), if you have a 1gb NIC, you will have 0,5% and so on. If you think there's something unusual, go to the relative tab and check WHICH process is using your resource. Let me know if you need help!

You should tell me what is COMPUTER X, was it a server? Of course it is running somewhere and it was a TRUSTED DELEGATED. Now the point is: can you find something in domains and trusts? If the computer X was a part of DC, you have to remove the partnership. Anyway, also this problem is not a problem (???), because the COMPUTER X will not be able to take infos about AD structure. But anyway, it will work properly. If you want to establish a trusted domain parternership, you can do this by adding a trusted in DOMAIN AND TRUSTS.

That's ok for sysvol. Just ignore this error. Regarding the last one (DHCP), I could tell you to remove and readd the DHCP role, but if everything is working fine, you don't have to do so. I think you're ok right now :)

Hi there, First of all let's clarify some topics: LOAD BALANCING is the art of CHECK WHICH OBJECT (server) HAS MORE RESOURCES AVAILABLE. Microsoft cannot do this, not in the way you want. Don't confuse LB (load balancing) with ROUND ROBIN (RR), RR just send request RANDOMLY to a pool of server. This means that if one of those servers fails, the broker (the component who has to "forward" the traffic) doesn't know anything about this. Just after a while (this is not easy, the THEORY says: once the heartbeat (usually a ping) is broken after 5 attempts, the node is automatically taken offline from the pool), but BEFORE this happens, requests made to this server are lost. Now, before going further, let me know what you want to do: 1) failover clustering (microsoft cluster, two or more servers with identical hardware which are replicated eachother) this scenario is also know as FAULT TOLERANT. 2) CDR (continuos data replication) for exchange, basically you install two times Exchange server (2007 and above) and you don't need clustering from MS. 3) MySql LB/RR You COULD create a failover cluster with round robin. Remember the network part, have 100 servers in a cluster with just one router is meaningless. Let me know!

Actually you shouldn't have big problems, sorry, no problems at all. Anyway, let's try to make sure everything is working fine: Check permissions on SYSVOL share (this is mandatory for GP). Regarding DHCP, try this: ipconfig /registerdns net restart netlogon Retry but as said, you may not have problems... time service is running, this is the most important thing.

I'm not really a good programmer... but I can remember that when I need to connect to a SQL server I prefer to use integrated auth. I used this whitepaper: http://www.asp.net/learn/whitepapers/aspnet-and-iis6 take a look at the end "Supporting integrated authentication with SQL Server" Regarding your firewall, you surely have done something wrong with rules. Let's start from Mdaemon. Yours rules may be correct, but you have to allow EXEs too. From the KB of Mdaemon, you should permit these EXEs: MDaemon.exe WorldClient.exe WebAdmin.exe MDSpamD.exe AVUpdate.exe The same thing must be made for SQL server's executable.

Try to open the dump file with this: http://www.nirsoft.net/utils/blue_screen_view.html Hope this help...

But the time service is running or not? start > run > services.msc > time > right click > properties and check WHO start this service.

WELCOME BACK! You should check something: 1) SYSLOG share (permissions) 2) Check DHCP & TIME services for start account. You may have to change the user account (network, system) if they start with a domain account, check passwords. The warnings you have, may all be related to time service (which is failing to start). But it seems to be a permission's problem. let me know.

You have to open the rights ports on your FW: Because of the many different scenario you can have, I suggest you to read this article from MS, which explains not only HOW to configure (allow) a program with Win FW, but also the ports used by SQL. http://technet.microsoft.com/en-us/library/cc646023.aspx Regarding your other problem, I suggest you to try to add a simple ODBC connection and see if you can retrieve any info. Can you post the string you use to connect from your app? thanks.

Hi and welcome. Regarding your request, depends on how much time you want to spend and which is your starting level. You could buy Microsoft's books regarding WS2k8, but they aren't so easy. On amazon you can find this book I bought time ago: http://www.amazon.com/Mastering-Microsoft-Windows-Server-2008/dp/0470532866/ref=sr_1_1?ie=UTF8&qid=1305404978&sr=8-1 Of course you should have some basics, if not, start with this one: http://www.amazon.com/Windows-Server-2008-Reference-Dummies/dp/0470180447/ref=sr_1_1?s=books&ie=UTF8&qid=1305405075&sr=1-1 Which covers also Active Directory really in a easy way. Enjoy your stay!

hi there, Just to be sure your problem is the firewall, temporarly disable it and check both applications. If this resolve your problem, re-enable your FW and post again so we can investigate on your problem. If this doesn't help you in any way, post again for the same reason as before :) cheers

Hi and welcome. Enjoy your stay!

Uh wait. I thought that all printers where network's printers... plugged to a Win Srv. In this scenario (with USB printer) you can just redirect the printer via "LOCAL RESOURCES" (the flag I told you to disable before) and I think there's no way to save settings...

Hi, I can't see the attachment / error.

Your user will have two identical printers. 1 -> terminal server with its own properties 2 -> directly mapped to the NB / WS with its own properties When he changes something on the local printer, this doesn't affect the TS's printer and viceversa.

Open the options for the .RDP file, LOCAL RESOURCES and UNCHECK printers. In this way, users will never have redirected printers.

Once a user is logged on via TS, open the control panel > printers > add network printer and map connecting trough the print server.

Hi there, First: Can you access that program from the server itself? Second: All the clients are on the same network? Third: Have you any firewall enabled? The error is quite clear... CANNOT OPEN CONNECTION. The most probable cause, could be a firewall.

I know it happens at a precise moment, but 0x5 can be compared to "generic error occurred" which means everything and nothing at the same time. Sorry I have no more ideas

You want to install Windows, enable Hyper-V and then add the AD role on the same server which is running hyper-v, right? If so, Microsoft says: "Although this scenario can be possible by manually change some parameter, you will experience performance's issues. This scenario is not officially supported by MS." In other words, if you want to do this, make sure to understand: 1) it's not a good idea 2) Domain controllers should be domain controllers and STOP 3) You can find guides on the network, but what you can do when you have a problem?

Try to add the MANAGE PRINTER permission to the users. If you deploy printers with GPO, I don't know the resolution. I had the same problem and finally I had to manually (or via script) map the printer from the control panel. But in my case everything worked with a script :)