Re: Stange program behavious after moving WStation into AD

First question off the top of my head is how does the system detect that files have "landed"?

Unless you have some new security lockdowns being delivered in GPOs via AD, AD would not impact the local functioning of workstations.

I would recommend figuring out how the application is working. Network traces might be useful. Contacting the vendor of the software that is doing all of this copying might be useful as well.

joe

--
Joe Richards Microsoft MVP Windows Server Directory Services
Author of O'Reilly Active Directory Third Edition
www.joeware.net


---O'Reilly Active Directory Third Edition now available---

http://www.joeware.net/win/ad3e.htm



gg@xxxxxxxxxxxxxxx wrote:
Hi, this is a bizarre problem - and you guys are my last hope!

We have a BESPOKE system running on 5 x Windows 2000 (Sp3)
workstations. Without going into too much detail 3 x of the PC's take
files from an external source, copy them to either of the other 2 x
PC's which in turn process the files (kind of a RIPPING process) then
pass the files BACK to the PC that sent the file in the first place (ie
on of the 3 x pcs)

All 5 x PC's were in a Windows NT domain (standard PDC/BDC/Wins etc). A
few days ago we have moved all the PC's into our Active Directory...all
is well EXCEPT...

SInce moving the PC's, we have a problem where the PC's that SEND the
file to be RIPPED now do not seem to detect when the files have been
processed and are sat in the output folder(s) waiting to be picked up -
its like now we are in AD, the PC's just arent aware that the files
have 'landed'

Even stranger....as we cant live with this setup, we moved the PC's
BACK into the old Domain...and the problem still exists! (and yes, its
defainately a result of moving into AD)

Does anyone know anything in particular that...

(a) Happens to a Worstation when being moved into AD, that could affect
its ability to detect when file(s) are copeid to a specific folder
another workstation?

(b) Any settings that could affect the above that WOULDNT be reverted
when putting a previously moved PC backn into an old Domain?

1st thing we looked at was user RIGHTS...but as a test, we have given
all PC's admin rights - only other issue could be null-session rights,
but we havent changed OS just moved to AD??

Its definately not file/folder/share security/permissions, the files
are written OK. Are there are policies that could be inherited that
might affect the file-hook detection?

Would the fact that we are on 2k SP3 be a problem? (not sure if the s/w
can take SP4!)

Any help appreciated, thanks

.

Relevant Pages

  • Re: OT: Update Virus Checker
    ... > The first question is: "Are you safer from virus attacks with OS ... Microsoft (along with Windows users) is in a sense a victim ... > to many of the security problems associated with those products. ...
    (rec.outdoors.fishing.fly)
  • Re: Display All Domain Names on the Network
    ... Hi to answer your first question, I just checked it (using wbemtest and ... Dim objDomain As ManagementObject ... I get the following exception when running the code on a Windows 2000 ... Unhandled Exception: System.Management.ManagementException: Invalid class ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Limitation to combobox items
    ... To answer your first question. ... Working with Windows Forms for Database front ends does seem a little rough ... > I stop trying to make them work and start shopping for a third party suite ... > of controls? ...
    (microsoft.public.dotnet.framework.windowsforms.databinding)
  • Re: IE Options-Programs
    ... >> For the first question, make sure OE is your default e-mail client. ... >> And please see these articles about virus protection in OE 6: ... >> Description of how the Attachment Manager works in Windows XP Service ...
    (microsoft.public.windows.inetexplorer.ie6_outlookexpress)