|Hello, I am hoping you will be able to help me with a problem I have.|
I think my network isn't set up properly. The network is working though!
That is, I can access the internet and my file server, but there are some problems
I have windows server 2003 installed and I have created domain accounts and I can log on to the server and I can log onto the workstation with domain accounts. Access the internet and server shares but....
One thing I noticed is a very slow log onto the workstation when logging using domain accounts. Up to ten minutes before the whole thing gets loaded up. Different stages of the log on process, take around 2 minutes each to complete.
Accessing network shares (on the server) are periodically disconnected and happens all the time. But the connection is always restored.
User Accounts, on the local workstation. I have added the domain users and they show in the list.
In advanced and groups, the names show with the SID as well, never seen that before.
From the advanced view of user groups on the local workstation, if I try to add a user, the domain doesn't show, even if I log onto the workstation as domain administrator, the only domain that is visible is the local domain (the workstation itself) and clicking on location shows only the local PC.
I cannot change NTFS security on a folder in the sense that I cannot add domain users to have any access rights, for the same reason as above. When you click on add, and click on locations, only the local PC is shown.
A domain user without admin rights cannot save documents on the local workstation but can log on and save work under their profile
My feeling it is probably a DNS issue and the way the server is set up.
So let me tell you how I set the network up. It is probably my lack of network knowledge that is causing the issue.
My job is an IT analyst, so connecting things to the network is something I do on a daily basis.
I am at home and talked to 'the little lady' about setting up a network at home. She has no problem, so long as, 1 she doesn't have to join the network, and 2 it doesn't stop our kids accessing the internet either.
So at home, we have a wireless ADSL router connected to the internet. The family connect via the wireless and I do have my own PC for home use that also connects via the wireless. I have a desktop, the workstation and a file server connected via cables to the network. The server has a fixed IP (not in the DHCP scope)
The ADSL router is the DHCP server and DNS server. The DC server has DNS local copy only.
All the network info that is on the ADSL router is configured on the DC server.
I would like to make the DC server the DHCP server, but I am not, because of the wireless on the ADSL router. If I turn off the DHCP on the router and make the DC the DHCP server. Will this cause an issue for clients PCs that are not members of the domain from getting an IP address from the server? If a PC is trying to connect to the wireless via the ADSL router, if the router isn't the DHCP server, it will get one from the DC?
On the ADSL router the DNS server addresses mentioned are public IPs. What would happen if I make the DC a fully fledged DNS server? I thought the ADSL router would have to have its own DNS server LAN side, but I am beginning to suspect there isn't one LAN side. The only DNS addresses I have seen are the public ones, and everything works as well, just not too well.
Any help would be very much appreciated.