First — somewhat newbie alert!
Here’s the issue: I just starting working at a school that has a Windows 2003 R2 Server. Simple filesharing used to work from this server. Then, I tried to install Active Directory, which I had previously managed at another school but not actually ever installed. Well, of course, that was not so smart, and the clients could not find the domain controller. Also, clients were still not looking to the W2K3 Server as the DNS server; they were looking at the ISP’s DNS.
After lots of reading, I decided I ought to just uninstall AD and DNS and focus on other day-to-day issues since school started today. I uninstalled AD and DNS using the Manage Your Server wizard. I did NOT go into the command line and dump the AD meta data.
Now, here’s the problem: I am trying to use simple filesharing from the server so we can start to archive instructional documents. The afternoon directly after uninstalling the AD and DNS, I had no problem connecting as a client to the shared folders. Then, I came in the next morning, and suddenly filesharing was no longer functioning. Odd. Since then, no clients have been able to connect to the shared folders on the server using either “My Network Places” or the map a directory function. I have checked the following settings:
1. Windows Firewall — under “Filesharing” TCP ports 139 and 445 are open; UDP ports 137 and 138 are open; under “UNUP”, TCP ports 2869 and UDP 1900 are open
2. I can successfully ping the server from a client.
3. In File Server Management, the drive that holds the shared folders is successfully shared.
4. The permissions on the shared directories are set to “everyone” for change and read.
5. I changed the name of the machine back to non-URL looking thing — all caps instead of this.this.this.
6. I also created a generic user on the server and tried to map a directory and log on as this user. That didn’t work either.
7. When I try to “Add A Network Place” from a client, I receive the message “The folder you entered does appear to be valid. Please choose another.” Also, you cannot see the server or any of the folders in the “Browse” list.
8. The server and all of the clients have been configured to the same Workgroup.
I am guessing all of this I-don’t-want-share business is the result of some DNS issue left over from the failed AD install, especially because filesharing was working before the AD install and I believe even during it. Any ideas you have either about how to get the AD running while maintaining the ISP DNS OR about how to just simple filesharing running would be EXTREMELY appreciated.
Thank you so much!
Lauren
