Recent content by zoldy

I have now spent the day reading countless articles claiming that if you create an OU and define a group policy and place the terminal server object inside the OU... everyone logging onto that server will have the policy applied.. article number 278295 But it simply does not work... The very...

yes thank you... i thought of that .... the only issue with that is it applies to everyone... I will keep searching.... I tried apply the policy to the built in group TERMINAL SERVER USERS... but that does not seem to work.. thanks again for the info

sorry re-read your response ... and now i understand... so I guess the question is how do I apply a user policy only when logged onto the terminal server? thanks

that's correct... but they don't... I can't figure out why... do I need to refresh or something like that?

As per a microsoft article here is what I am tring to do... apply a policy to a user only if they are logging into the terminal server.... Intructed to create a new OU... move the server object into this OU... Creat a group policy on this OU... The only way the policy seems to apply is...

managing the permissions using this method would be difficult... future changes would require alot of management... yes this would work but I was looking for alternatives

Back in the novell days you used to be able to set a user as a security eqaul to another user.. this was handy in certain situations. Anyone know of something similar in windows 2000. Here is what I am trying to do... it is a bit complicated but here are the basics.. user1 .. normal...

the table I am linking to is a DB2 ... I have had similar issues with these.... Alternately can I force Upper case on import in to my user table? The data on one side is db2 the data on the other side is imported...

I am doing a join in access and it is not matching these two fields.... 9p23-BA4B 9P23-BA4B If I change the p to uppercase it works... can I change the join to not be case sensative? thanks in advance

Ok I found that I have antivirus for smtp gateway product from symantec that is causing the issue. However when I allow relaying on that software.... it allows from any ip .... not sure why ...... seem to have opposite problem now... I have support contract for the symantec product so I am...

The other thing that might help resolve what is wrong is that if the destination address is one of my users ... it works fine. it must be checking the destination address for some reason..

We are using outlook ... however as I stated we also have an aplication that uses smtp to send mail directly from the app. This app does not support authentication on the outbound mail... and yes I did add the address in the allow list and yes it still deny's relaying

Here is what I want to do maybe it is not even possible... I want to allow my local lan users on my domain... to send smtp mail through my exchange server and the mail client does not support user name and password on outbound mail.... I thought by allowing relaying on my local IP's subnet...

I get 550 relaying denied... any other ideas?

hmmm... that's exactly what I did as well....