I am new to networking and have been asked to figure out how to fix the issues here where I work. I have tried various things but to no avail and am in need of major help.
First I'm not sure of why but they set the network on a 184.108.40.206 scope. Then when they ran out of IP addresses they put in a linksys router and configured it with a 220.127.116.11 IP address. Now that might seem as if it will work but it doesn't. Because the linksys router is handing out the DHCP. Which means that in order for me to remote to any of the devices on the linksys router I have to log into the domain controller.
Second I have to set up duplicate servers on each link in order to issue updates. This is a waste of resources when I know that there is a fix for this.
Here is what I have tried:
I put the linksys router in bridge mode, created a super scope and added a persistant route. The best I could get was out to the internet but could not use any of the companies resources. I have spent hours reaching this and just as many in trial and error. But I still end up restoring the configuration that is currently in place.
If someone has any suggestion please enlighten me.
The Subnet on the Domain controller used to be 255.255.255.0 now it is 255.255.0.0. But the Linksys router will not let me change the subnet on the device to 255.255.0.0. It will only except 255.255.255.0.
The network cards on the domain controller are virtualized and to change this will make the network less stable according to all documents I have read.
That is why I tried to set up the Super Scope on the Domain Controller but there is still something I am missing.
Finally, we want to change to a 10 network but there should be a solution to this as well.
Ok, I'm not sure as to what you mean as host, so I will probably give you either the wrong information or too much information.
We have one server as Domain Controller, Dns, Dhcp and Active Directory. With one fail over server. These are both running Windows 2000 server.
We then have various servers running Windows NT - Windows 2003 server. There are 13 in all.
Next we have 20 switches, one linksys router, 30 network printers, between 200 and 220 computers - depending on if all laptop users are logged on the network - and finally 5 wireless access points. These are used for our PPC, however, currently they are not part of the domain.
Here is some other interesting things that might help narrow down the issue.
When users VPN in they get a 193.100.3.XXX and can get to all functions of the domain. We have our end users using Terminal Server.
When I loggon on to a computer on the 193.100.4.XXX I can get to some network drives that were brought in with the NETLOGON, i.e.
We have our users with there own personal drives on the network the nas server is called personal and we then through their .bat have a shared folder assigned to them. The nas server is on the 193.100.1.XXX network, however because of this I can UNC to any part of the nas server. Yet when I try to UNC/RDP to say on my local pc on the 193.100.1.XXX or for that matter any server/computer I get a pop up box stating that it is unavailable.
The only time I can ping a computer or device on the 193.100.4.XXX is when I am on either the Domain server or the backup Domain server. The same goes for when I am on the 193.100.4.XXX I can only ping the Domain server or backup Domain server.
I hope that somewhere with this information I have answered the question.