Al. Peter has finished for the day, I will pass this to him tomorrow for his comments and come back to you but I have answered some of the below. >That makes no sense. agree >If the app runs on the workstation and fails AND is a permissions issue, >then it stands to reason that it would show up in the security logs of the >DC since that is where the failure occurred. You may have to turn on that >audit logging if not already enabled, but permissions have to go to the DC >for success/failure. Will check this for tomorrow >As for the other troubleshooting, did you only google for an answer and >determine that it doesn't work? I find that hard to believe. And since >2003 is more restrictive in it's security stance, permissions aren't the >likely cause if it works against 2003 vs. 2000. That's not to say it >couldn't be, but it's more likely something else that's different in your >environment. Technet, m/s etc etc >I've written many apps that run against 2000 and 2003 domain controllers >and >they work fine. The *only* time I would consider putting something on the >Exchange server directly is if the application required it due to >application binaries. CDOEXM would be one such example. However, I would >personally just install the needed supporting binaries vs. doing that. Cannot comment will hand to peter >Can you post the failing snippet of code and the AD interaction section? >Else send it off-line? >That might be more helpful in this case. Will pass to peter Steve -----Original Message----- From: steve alcock [mailto:steve.alcock@xxxxxxxxxxxxxx] Sent: Tuesday, November 30, 2004 12:00 PM To: [ExchangeList] Subject: [exchangelist] RE: LDAP problem http://www.MSExchange.org/ >Give some more information. What is the app and what language is it? Visual basic to read e-phone call logs ( these are call records in and out of the company ) >Why do you think that running it on the Exchange server would cause it to >work? Running pete's program on the win2000 server he can read in the current users in the active directory, but running the same program on a workstation it is very hap hazard if it cannot connect to the active directory error message the data base is not available. >Permissions issues (Exchange servers have different permissions of >course, but that's no excuse for that type of programming, right?) that's what we thought >What exact symptoms are you seeing and what has been done to troubleshoot >to date? For example, if a permissions issue, you could see that in the >logs. We have trawled the net for fun hence the running on the server as someone suggested but they ( or anyone else to date can give us the solution ). Nothing is reported in the log Just for the record running the same program on a workstation connected to a win 2003 server and it works fine ? Hence a permissions / security issue in win 2000 server we think Got us stumped steve -----Original Message----- From: steve alcock [mailto:steve.alcock@xxxxxxxxxxxxxx] Sent: Tuesday, November 30, 2004 11:29 AM To: [ExchangeList] Subject: [exchangelist] LDAP problem http://www.MSExchange.org/ Hi all, Windows server 2000 & exchange server............. One of our staff is writing a program to read VoIP call files and to marry them up with network users via Ldap to read the active directory users but it is very hit and miss as to connecting to the service, reading the web many people have this problem but no one gives a complete answer the only real clue is if we run the app on the exchange server it is ok but a workstation is hap hazard, it seems something has to be set on the server to allow the workstations the same access as if running it on the server but I cannot find anything in security policies etc anyone shed a light on what needs altering on the server please?????? Steve Calderglen Computers Calder House Spring Lane Colne Lancs BB8 9BD www.calderglen.net <http://www.calderglen.net/> phone : +44 (0) 1282 871717 -----Original Message----- From: Rick Boza [mailto:rickb@xxxxxxxxxxx] Sent: 29 November 2004 16:09 To: [ExchangeList] Subject: [exchangelist] RE: Instant Messaging http://www.MSExchange.org/ So to make sure we understand, you already have an E2K org in place (on an Win2K3 server) and wanted to add the IM functionality to it? You're not really playing around with this in your production org, are you? Anyhow, this tech rides on the Exchange 2000 technology - if I recall correctly, you can't have the IM functionality up and running without Exchange 2000 present as well. The schema needs to be extended (which you presumably did since you're seeing the IM capabilities in ADUC) but it needs to be fully configured from within ESM before you can enable it for users. Note I'm working from (admittedly slipping) memory here - I worked with this for a couple clients in years past but not recently. Maybe go thru step by step what you did so we can be sure we understand - and I really really suggest playing around with it on a couple test boxes before you go any further and wind up breaking something you didn't want to. Rick On 11/29/04 10:58 AM, "Mark Fugatt" <markfu@xxxxxxxxxxxxx> wrote: http://www.MSExchange.org/ I would recommend you go with Live Communication Server, personally I don't think Exchange 2000 IM on a Windows 2003 server is a supported installation. Mark Fugatt Dedicated Supportability Engineer (Exchange) Microsoft Services Organisation Desk: +44 (0)118 909 5630 Mobile: +44 (0)7966 858108 http://www.microsoft.com/support Dedicated to proactively supporting Microsoft's enterprise Customers This email may contain confidential information. If you are not named on the addressee list, please take no action in relation to this email, do not open any attachment, and please contact the sender (details above) immediately. Information in this email is provided in good faith. If you are a customer of Microsoft, please refer to the terms and conditions which cover the provision of support and consulting services to you/your organization. If you are not corresponding in the course of, or in connection with a Microsoft contract or program with its own terms and conditions, please note that no liability is accepted by Microsoft for the contents of this mail. ________________________________ From: Edwin [mailto:msexchange@xxxxxxxxxx] <mailto:msexchange@xxxxxxxxxx%5d> Sent: 29 November 2004 15:39 To: [ExchangeList] Subject: [exchangelist] Instant Messaging http://www.MSExchange.org/ We would like to make use of the MSN Instant messaging service within our domain. Our DC's are both Win2K3 standard Edition and our Exchange Server is Win2K Advanced. I installed the Instant Messaging software from the Exchange 2000 CD onto a Win2K3 Standard machine that is a member server. I understand that Exchange 2000 is not compatible with Win2K3 however I am not using the mail services and thought I would give it a try before re-installing the server I intend to use. Basically, on the Win2K3 machine I installed the software and System Manager. When I go to the "Exchange Features" tab, of the user I intend to use, I click on "Enable" and I am asked for a IM Home Server. The problem is that the "Browse" button is disabled. Is this because of Win2K vs. Win2K3 with Exchange 2000 (possibly)? Or is there a step that I am missing? P.S. Why not use Exchange 2003? For licensing reasons. P.P.S. Why do you want to use IM? Because we are currently using an antiquated version of ICQ Corporate Edition on an old NT4 domain that I want to get rid of and this will be the final step. ------------------------------------------------------ List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ ------------------------------------------------------ Other Internet Software Marketing Sites: World of Windows Networking: http://www.windowsnetworking.com Leading Network Software Directory: http://www.serverfiles.com No.1 ISA Server Resource Site: http://www.isaserver.org Windows Security Resource Site: http://www.windowsecurity.com/ Network Security Library: http://www.secinf.net/ Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com ------------------------------------------------------ You are currently subscribed to this MSEXchange.org Discussion List as: markfu@xxxxxxxxxxxxx To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=exchangelist Report abuse to listadmin@xxxxxxxxxxxxxx ------------------------------------------------------ List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ ------------------------------------------------------ Other Internet Software Marketing Sites: World of Windows Networking: http://www.windowsnetworking.com Leading Network Software Directory: http://www.serverfiles.com No.1 ISA Server Resource Site: http://www.isaserver.org Windows Security Resource Site: http://www.windowsecurity.com/ Network Security Library: http://www.secinf.net/ Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com ------------------------------------------------------ You are currently subscribed to this MSEXchange.org Discussion List as: rickb@xxxxxxxxxxx To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=exchangelist Report abuse to listadmin@xxxxxxxxxxxxxx ------------------------------------------------------ List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ ------------------------------------------------------ Other Internet Software Marketing Sites: World of Windows Networking: http://www.windowsnetworking.com Leading Network Software Directory: http://www.serverfiles.com No.1 ISA Server Resource Site: http://www.isaserver.org Windows Security Resource Site: http://www.windowsecurity.com/ Network Security Library: http://www.secinf.net/ Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com ------------------------------------------------------ You are currently subscribed to this MSEXchange.org Discussion List as: steve.alcock@xxxxxxxxxxxxxx To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=exchangelist Report abuse to listadmin@xxxxxxxxxxxxxx ------------------------------------------------------ List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ ------------------------------------------------------ Other Internet Software Marketing Sites: World of Windows Networking: http://www.windowsnetworking.com Leading Network Software Directory: http://www.serverfiles.com No.1 ISA Server Resource Site: http://www.isaserver.org Windows Security Resource Site: http://www.windowsecurity.com/ Network Security Library: http://www.secinf.net/ Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com ------------------------------------------------------ You are currently subscribed to this MSEXchange.org Discussion List as: al.mulnick@xxxxxxxxxx To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=exchangelist Report abuse to listadmin@xxxxxxxxxxxxxx ------------------------------------------------------ List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ ------------------------------------------------------ Other Internet Software Marketing Sites: World of Windows Networking: http://www.windowsnetworking.com Leading Network Software Directory: http://www.serverfiles.com No.1 ISA Server Resource Site: http://www.isaserver.org Windows Security Resource Site: http://www.windowsecurity.com/ Network Security Library: http://www.secinf.net/ Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com ------------------------------------------------------ You are currently subscribed to this MSEXchange.org Discussion List as: steve.alcock@xxxxxxxxxxxxxx To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=exchangelist Report abuse to listadmin@xxxxxxxxxxxxxx ------------------------------------------------------ List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ ------------------------------------------------------ Other Internet Software Marketing Sites: World of Windows Networking: http://www.windowsnetworking.com Leading Network Software Directory: http://www.serverfiles.com No.1 ISA Server Resource Site: http://www.isaserver.org Windows Security Resource Site: http://www.windowsecurity.com/ Network Security Library: http://www.secinf.net/ Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com ------------------------------------------------------ You are currently subscribed to this MSEXchange.org Discussion List as: al.mulnick@xxxxxxxxxx To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=exchangelist Report abuse to listadmin@xxxxxxxxxxxxxx ------------------------------------------------------ List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ ------------------------------------------------------ Other Internet Software Marketing Sites: World of Windows Networking: http://www.windowsnetworking.com Leading Network Software Directory: http://www.serverfiles.com No.1 ISA Server Resource Site: http://www.isaserver.org Windows Security Resource Site: http://www.windowsecurity.com/ Network Security Library: http://www.secinf.net/ Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com ------------------------------------------------------ You are currently subscribed to this MSEXchange.org Discussion List as: steve.alcock@xxxxxxxxxxxxxx To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=exchangelist Report abuse to listadmin@xxxxxxxxxxxxxx