Jump to content

catwalker63

Member
  • Posts

    31
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Posts posted by catwalker63

  1. I don't know of any reason for putting DNS in a DMZ but I would make sure there are no other services running on your DNS servers if they are published on the Internet. For the same reason, you should not store files on these servers either. If you have your domain registered on the Internet, you have no choice but to publish the IP addresses of at least two DNS servers for your domain and this gives the bad guys a place to start when attacking your network. If there are no other services to exploit and there is data to steal on your DNS servers, attackers have to work harder to find hosts on your network that will give them what they want.

    Putting your Web and FTP servers in a DMZ, however, is an excellent idea, since outside users are actually accessing content on these servers.

  2. What books have you got/are you getting to study with?

    May I suggest the following:

    Minasi Resource Kit from Sybex (Mastering Windows Server 2003, Mastering Active Directory, Mastering Windows XP Pro, and Mastering Windows XP Registry)

    O'Reilly Active Directory Second Edition by Allen & Lowe-Norris

    I also recommend you get the Microsoft Server 2003 Resource Kit. The XP resource kit you can read online at:

    XP Resource Kit

    Another useful link for all things Microsoft:

    Resource Kit Web Resources

    Also, check out CertTutor at:

    CertTutor Home

    Forums, free practice exams and kind support!

    Good luck! :)

  3. For me it was wfw 3.11 to 95. :) Have you ever installed 95 with floppies? :rolleyes:

    Have you checked the Dell/Compaq websites for drivers for Pro for your machines? Or an upgrade path? You may luck out. At the very least you may be able to back it down to a Win2k Pro -- preferable to the Home edition because of the networking capabilities.

  4. Your NTFS permissions need to allow each user at least Modify permission for non-mandatory roaming profiles. Set the permissions on the same folder as the share and make sure to allow inheritance to propagate from parent to child. If you are using the %username% variable it will set up the folders for each profile for you with the appropriate permissions, or at least it should.

    Do you have the Resource Kits for 2003 and XP? The XP one is available online at Microsoft's website. So are the one's for 2000 and most of what is there should also apply to 2003 to some extent.

  5. I don't think it's DNS if you can ping the name of the server and map drives.

    And it's not protocol binding order if you are only using TCP/IP.

    You've shared the Profile folder on the server with full control permissions on the share and NTFS so it's not permissions. And it's saying it can't find the path anyway so that doesn't indicate a problem with permissions.

    Have you checked the path carefully, letter by letter, and the folder name and server name, letter by letter, to make sure you haven't mistyped?

    I once had a terrible time with the path to my win95 install share because someone had named the folder 0sr2 (the number zero instead of the letter O).

×
×
  • Create New...