Active Directory replication runs through port 389. By an unhappy concidence, so does Exchange 5.5's LDAP connector. You may have to change the port number Exchange uses.
Check out: http://support.microsoft.com/default.aspx?scid=kb;en-us;312501
HTH
Chris
Mark,
Thanks, but this isn't quite what I need. I'm not sure if I'm explaining this right.
In our user folders, we might have User1, User2, etc. Let's say in User1, I have a folder stuff. In that folder is a folder morestuff.
When DFS failed & rebuilt, it renamed the folder \User1\stuff...
OK, we have 2 W2K DCs at work connected via VPN over cable modem. These servers are also DFS (Distributed File System) servers.
Unfortunately, the VPN connection tends to drop and refuses to reconnect (I'm thinking it's a router problem, but that's another story), and at one point, the loss of...
What are the upload speeds on the 2 Internet connections you're running the VPNs on? Remember, Upstream Speed - VPN tunnel overhead = total bandwidth for file/app use. Download speeds make NO difference here.
Oracle stuff is also usually OBNOXIOUSLY huge. One of our staff needed to use an...
Sounds like it's hanging up trying to start the UPS daemon. The logon prompt should appear automatically after all daemons have been loaded. Try using Ctrl-C to skip the UPS start when it hangs and see if you get the MOTD & logon prompt.
Replacing the client's grc.dat file with the new copy in the VPHOME share on the AV server should also fix the "old server listed on the client AV upgrade" problem.
Did you recently upgrade or change your Exchange server? We went through this after our new Exchange server was in place. Some of the Outlook clients were pointing to the old server's Contacts folder.
In Control Panel -> Mail -> Outlook Address Book, go to properties and delete all references...
Try this - In Active Directory Users & Computers, make sure that each mail-enabled user has the proper address listed under "Email Address" in the user's Properties. Otherwise, Exchange likes to tag the return address as user@yourADdomain.
Hope this helps
Unfortunately, NT & 2000 do not have the capability of hiding files & folders via permissions, like you can in Novell. But proper permissions settings will prevent access by unauthorized users. NTFS permissions aren't as weak as 9x share-level permissions.
If you use a $ after the share name, it will be hidden from the Network Neighborhood browser. You then map a drive letter to this hidden share. e.g. \\SERVER1\USER1$
Remember also that any folders on the server (as long as you're using NTFS as your file system) have permission settings, just...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.