Windows Network Help Needed
-
Hello everyone, I work at a non-profit org. and we have a small office network with 1 server (Windows Server 2000) and about 20 computers (fast, slow, dell, hp but all running Windows OS - pro and couple of home editions). Our Windows Server 2000 is on a Dell Dimension E510 with Pentium HT 2.8 GHz and 1GB of RAM. It runs as a Domain controller and running Active Directory on it. Our DHCP is our modem - just so that DHCP works even when our server is turned off. We recently switched from use of workgroup to domain after we got the server and couple of problems seem to be rising, which I need some help on. 1. Accessing people's shared folders became slower - sometimes up to a minute. Sometimes it goes really smooth. I think getting a router might solve this problem but we never had this problem before we installed the server on one of our computers 2. In our TCP/IP config we have our modem as "Preferred DNS" and our ISP DNS as "Alternate DNS". I am not sure if this is the way it should be. Seems like our Server is running DNS too. I don't know if I can disable it - though non of our computers are configured to look for DNS in the server (our local E510). 3. When a domain user wants to log on to the their computer it asks if they want to lon on to the the local computer or the domain. I was just wondering what's the difference? Which one should I use? Right now everyone is loggin onto their own local accounts because that's where they have their files and everything because that's the only place that we could log on to before we got the server. How should I go about to solve this problems. Any help, ideas, comments, questions is appreciated. Thank you for your time, Chandman
-
Hello everyone, I work at a non-profit org. and we have a small office network with 1 server (Windows Server 2000) and about 20 computers (fast, slow, dell, hp but all running Windows OS - pro and couple of home editions). Our Windows Server 2000 is on a Dell Dimension E510 with Pentium HT 2.8 GHz and 1GB of RAM. It runs as a Domain controller and running Active Directory on it. Our DHCP is our modem - just so that DHCP works even when our server is turned off. We recently switched from use of workgroup to domain after we got the server and couple of problems seem to be rising, which I need some help on. 1. Accessing people's shared folders became slower - sometimes up to a minute. Sometimes it goes really smooth. I think getting a router might solve this problem but we never had this problem before we installed the server on one of our computers 2. In our TCP/IP config we have our modem as "Preferred DNS" and our ISP DNS as "Alternate DNS". I am not sure if this is the way it should be. Seems like our Server is running DNS too. I don't know if I can disable it - though non of our computers are configured to look for DNS in the server (our local E510). 3. When a domain user wants to log on to the their computer it asks if they want to lon on to the the local computer or the domain. I was just wondering what's the difference? Which one should I use? Right now everyone is loggin onto their own local accounts because that's where they have their files and everything because that's the only place that we could log on to before we got the server. How should I go about to solve this problems. Any help, ideas, comments, questions is appreciated. Thank you for your time, Chandman
Chandman wrote:
pro and couple of home editions
What do you mean by home edition? Is it windows xp home edition?
Chandman wrote:
We recently switched from use of workgroup to domain after we got the server and couple of problems seem to be rising, which I need some help on.
If your networking has a windows xp home edition, you won't be able to join your computer to domain controller. Only windows xp professional edition that could join to domain controller.
Chandman wrote:
1. Accessing people's shared folders became slower - sometimes up to a minute. Sometimes it goes really smooth
In my opinion, this issue relate to name resolution process. Name resolution process is translation from a computer name to an IP address. Our computer name are contact to each other via ip address. There are many step of name resolution process work:
DNS cache, host file, DNS, NetBIOS cache, WINS, NetBios broad cast, lmhost file. You said that accessing to the other resource on your network sometime slow and sometime fast. This relate to name resolution process which fall in NetBios broadcast section which your computer boradcast its signal to find a computer with a specific IP address to connect to. From here, i want to ask you a question, does your network have a DNS server? DNS server is the server that use to store a DNS name with IP address of each computer. If you do not have DNS server, then you should edit the host file on each computer to point to a specific name and IP address. The host file is locate in%systemroot%\system32\drivers\etc\hostfilethis file is open with notepad. Try to read its explaination in the file and add the record in it. If you afraid that it might impact to system, you can copy its original file to another location. Manually do this to all computer or copy and paste it via a diskette to the other computer.Chandman wrote:
I think getting a router might solve this problem but we never had this problem before we installed the server on one of our computers
Why you use a router in your networking environment? Router is a device that connect from LAN to LAN which has a difference network ID or connect from LAN to WAN (usually internet). By default router device never allow broadcast signal access through it. If you have DHCP serve an
-
Hello everyone, I work at a non-profit org. and we have a small office network with 1 server (Windows Server 2000) and about 20 computers (fast, slow, dell, hp but all running Windows OS - pro and couple of home editions). Our Windows Server 2000 is on a Dell Dimension E510 with Pentium HT 2.8 GHz and 1GB of RAM. It runs as a Domain controller and running Active Directory on it. Our DHCP is our modem - just so that DHCP works even when our server is turned off. We recently switched from use of workgroup to domain after we got the server and couple of problems seem to be rising, which I need some help on. 1. Accessing people's shared folders became slower - sometimes up to a minute. Sometimes it goes really smooth. I think getting a router might solve this problem but we never had this problem before we installed the server on one of our computers 2. In our TCP/IP config we have our modem as "Preferred DNS" and our ISP DNS as "Alternate DNS". I am not sure if this is the way it should be. Seems like our Server is running DNS too. I don't know if I can disable it - though non of our computers are configured to look for DNS in the server (our local E510). 3. When a domain user wants to log on to the their computer it asks if they want to lon on to the the local computer or the domain. I was just wondering what's the difference? Which one should I use? Right now everyone is loggin onto their own local accounts because that's where they have their files and everything because that's the only place that we could log on to before we got the server. How should I go about to solve this problems. Any help, ideas, comments, questions is appreciated. Thank you for your time, Chandman
Hi Chandman. First: 1 Server and 20 computers seems absolutely reasonable. Especially with the server specs you posted. On 1: If you are in a single collision domain (network using hubs) you might be experiencing the effect of high load on such a kind of network. If you have seperate collision domains (network using switches), try enabling auto-negotiation for link-speed and -mode (i.e. "MBit/s" and "Duplex-Type"). Also check that everyone is in the same network (IP-network, i.e. everyones addresses are between 192.168.0.1 and 192.168.0.254). I do not think that splitting your network and putting a router in between is gonna help you very much. On 2: Btw, your modem seems to be a router. Otherwise, it would probably not have an IP address at all. If it also has a DHCP-server, see that only one is running (modem/router or server), two might cause some trouble. If you want to use your server for DNS and DHCP, disable DHCP in the router and configure the server to look-up any unknown address via router / ISP-DNS. The clients should then be set to use the server for DNS. On 3: The domain. Otherwise, the user might have to authenticate with the domain each time he tries to access a certain service. Plus, the advantage of being in a domain is that - if you store profiles on the domain server - users can work on any computer they log in to. They still will get a profile and "My Documents" on the machine they are working with, but - of course - the "Documents"-folder will not "follow them" from one computer to the next. But, then, they probably are gonna be working on one machine most of the time, anyway. Cheers, Sebastian -- Contra vim mortem non est medicamen in hortem.
-
Chandman wrote:
pro and couple of home editions
What do you mean by home edition? Is it windows xp home edition?
Chandman wrote:
We recently switched from use of workgroup to domain after we got the server and couple of problems seem to be rising, which I need some help on.
If your networking has a windows xp home edition, you won't be able to join your computer to domain controller. Only windows xp professional edition that could join to domain controller.
Chandman wrote:
1. Accessing people's shared folders became slower - sometimes up to a minute. Sometimes it goes really smooth
In my opinion, this issue relate to name resolution process. Name resolution process is translation from a computer name to an IP address. Our computer name are contact to each other via ip address. There are many step of name resolution process work:
DNS cache, host file, DNS, NetBIOS cache, WINS, NetBios broad cast, lmhost file. You said that accessing to the other resource on your network sometime slow and sometime fast. This relate to name resolution process which fall in NetBios broadcast section which your computer boradcast its signal to find a computer with a specific IP address to connect to. From here, i want to ask you a question, does your network have a DNS server? DNS server is the server that use to store a DNS name with IP address of each computer. If you do not have DNS server, then you should edit the host file on each computer to point to a specific name and IP address. The host file is locate in%systemroot%\system32\drivers\etc\hostfilethis file is open with notepad. Try to read its explaination in the file and add the record in it. If you afraid that it might impact to system, you can copy its original file to another location. Manually do this to all computer or copy and paste it via a diskette to the other computer.Chandman wrote:
I think getting a router might solve this problem but we never had this problem before we installed the server on one of our computers
Why you use a router in your networking environment? Router is a device that connect from LAN to LAN which has a difference network ID or connect from LAN to WAN (usually internet). By default router device never allow broadcast signal access through it. If you have DHCP serve an
Thank you for your response Roath.
Roath Kanel wrote:
Chandman wrote:
pro and couple of home editions
What do you mean by home edition? Is it windows xp home edition?
Yes we have Windows XP Professional and few Home editions aswell. But I found out that if I set the Workgroup same as our domain name, the computer becomes a part of the network.
Roath Kanel wrote:
Chandman wrote:
1. Accessing people's shared folders became slower - sometimes up to a minute. Sometimes it goes really smooth
In my opinion, this issue relate to name resolution process... From here, i want to ask you a question, does your network have a DNS server? DNS server is the server that use to store a DNS name with IP address of each computer...
Yes. Our Windows Server 2000 runs a DNS server. How should I go about configuring it? In our server - in the DNS console, I just noticed that we have our server ip address for the forward lookup zones. But we don't have anything in the reverse lookup zones. Is that an issue? I am also thinking that I should set all computer's preffered DNS to our server - not our modem. But I have to have some way to forward that to our gateway if it's outgoing request outside of our LAN. So I'm not so sure on this eigther. About router: I've seen many people having a [ WAN - modem - router - switch - computers] set up. Though, our current configuration is set up in a way that we don't have a router in between our switch and modem - therefore our modem is acting like a router, hosting DHCP, and acting as a DNS. I feel like having it set up so that when the sub netmask is 255.255.255.0 forward it to our server (DNS) else forward it to our modem or directly to our ISP DNS server. But I'm not sure about how to do it and whether I should do it. Other thing that might be useful to know is that in some room we have 2 person working in there and they share the connection via hub. It's kind of expensive for us to replace all those hubs with small switches just to test, because once again we're non-profit. PS: Our internet works fine though - no one's complaining about the internet speed. Thank you again for all your replies so far. Chandman -- modified at 14:14 Friday 9th June, 2006
-
Hi Chandman. First: 1 Server and 20 computers seems absolutely reasonable. Especially with the server specs you posted. On 1: If you are in a single collision domain (network using hubs) you might be experiencing the effect of high load on such a kind of network. If you have seperate collision domains (network using switches), try enabling auto-negotiation for link-speed and -mode (i.e. "MBit/s" and "Duplex-Type"). Also check that everyone is in the same network (IP-network, i.e. everyones addresses are between 192.168.0.1 and 192.168.0.254). I do not think that splitting your network and putting a router in between is gonna help you very much. On 2: Btw, your modem seems to be a router. Otherwise, it would probably not have an IP address at all. If it also has a DHCP-server, see that only one is running (modem/router or server), two might cause some trouble. If you want to use your server for DNS and DHCP, disable DHCP in the router and configure the server to look-up any unknown address via router / ISP-DNS. The clients should then be set to use the server for DNS. On 3: The domain. Otherwise, the user might have to authenticate with the domain each time he tries to access a certain service. Plus, the advantage of being in a domain is that - if you store profiles on the domain server - users can work on any computer they log in to. They still will get a profile and "My Documents" on the machine they are working with, but - of course - the "Documents"-folder will not "follow them" from one computer to the next. But, then, they probably are gonna be working on one machine most of the time, anyway. Cheers, Sebastian -- Contra vim mortem non est medicamen in hortem.
Sebastian Schneider wrote:
On 1: If you are in a single collision domain (network using hubs) you might be experiencing the effect of high load on such a kind of network. If you have seperate collision domains (network using switches), try enabling auto-negotiation for link-speed and -mode (i.e. "MBit/s" and "Duplex-Type"). Also check that everyone is in the same network (IP-network, i.e. everyones addresses are between 192.168.0.1 and 192.168.0.254). I do not think that splitting your network and putting a router in between is gonna help you very much.
We have a modem first - Main switch - hubs - computers We use hubs because we have 2 person in a office and only one ethernet plug into the wall. The Modem is our router, DHCP, DNS as well. Probably not a good solution, right? Q: How do I connect to our switch? I don't think there's a IP for it. When you say enable auto-negotioation, do you mean there's something that you switch manually on the switch?
Sebastian Schneider wrote:
On 2: Btw, your modem seems to be a router. Otherwise, it would probably not have an IP address at all. If it also has a DHCP-server, see that only one is running (modem/router or server), two might cause some trouble. If you want to use your server for DNS and DHCP, disable DHCP in the router and configure the server to look-up any unknown address via router / ISP-DNS. The clients should then be set to use the server for DNS.
Yes, our Modem is our only DHCP, because I uninstalled the DHCP service from the server. I tried to use our server as DHCP but I thought the internet would not work when the server is shut down. Server is on all the time but I just didn't want the other computers to be dependent on it. Q: What do you think about this situation? PS: Our internet works fine though - no one's complaining about the internet speed. Thanks Sebastian, Chandman -- modified at 14:13 Friday 9th June, 2006
-
Thank you for your response Roath.
Roath Kanel wrote:
Chandman wrote:
pro and couple of home editions
What do you mean by home edition? Is it windows xp home edition?
Yes we have Windows XP Professional and few Home editions aswell. But I found out that if I set the Workgroup same as our domain name, the computer becomes a part of the network.
Roath Kanel wrote:
Chandman wrote:
1. Accessing people's shared folders became slower - sometimes up to a minute. Sometimes it goes really smooth
In my opinion, this issue relate to name resolution process... From here, i want to ask you a question, does your network have a DNS server? DNS server is the server that use to store a DNS name with IP address of each computer...
Yes. Our Windows Server 2000 runs a DNS server. How should I go about configuring it? In our server - in the DNS console, I just noticed that we have our server ip address for the forward lookup zones. But we don't have anything in the reverse lookup zones. Is that an issue? I am also thinking that I should set all computer's preffered DNS to our server - not our modem. But I have to have some way to forward that to our gateway if it's outgoing request outside of our LAN. So I'm not so sure on this eigther. About router: I've seen many people having a [ WAN - modem - router - switch - computers] set up. Though, our current configuration is set up in a way that we don't have a router in between our switch and modem - therefore our modem is acting like a router, hosting DHCP, and acting as a DNS. I feel like having it set up so that when the sub netmask is 255.255.255.0 forward it to our server (DNS) else forward it to our modem or directly to our ISP DNS server. But I'm not sure about how to do it and whether I should do it. Other thing that might be useful to know is that in some room we have 2 person working in there and they share the connection via hub. It's kind of expensive for us to replace all those hubs with small switches just to test, because once again we're non-profit. PS: Our internet works fine though - no one's complaining about the internet speed. Thank you again for all your replies so far. Chandman -- modified at 14:14 Friday 9th June, 2006
Chandman wrote:
Thank you for your response Roath.
My name is Kanel, Please call me Kanl.
Chandman wrote:
Yes we have Windows XP Professional and few Home editions aswell. But I found out that if I set the Workgroup same as our domain name, the computer becomes a part of the network.
If you have windows xp home edition, you won't be able to join your computer to a domain controller. It doesn't mean you put the same name and you contact communicate with each other. Whether you put a difference name, you still communicate with them but you will see a workgroup and a domain in My network place in your computer. Difference between workgroup and client/server is the way that network administrator manage the network resource.
Chandman wrote:
Yes. Our Windows Server 2000 runs a DNS server. How should I go about configuring it? In our server - in the DNS console, I just noticed that we have our server ip address for the forward lookup zones. But we don't have anything in the reverse lookup zones. Is that an issue? I am also thinking that I should set all computer's preffered DNS to our server - not our modem. But I have to have some way to forward that to our gateway if it's outgoing request outside of our LAN. So I'm not so sure on this eigther.
There are many step to promote your standa alone server to become a primary domain controller. You have to configure, static IP address, DNS, configure friendly name, install DNS component and create forward look zone and revers look up zone (there is more technical detail to create these zone), test DNS service whether your configure properly then finally promote your stand alone server by typing DCPROMO command from the run dialog box. I recommend you to read this aritlce[^] to gain more knowledge about managing your network environment.
Chandman wrote:
About router: I've seen many people having a [ WAN - modem - router - switch - computers] set up. Though, our current configuration is set up in a way that we don't have a router in between our switch and modem - therefore our modem is acting like a router,
-
Sebastian Schneider wrote:
On 1: If you are in a single collision domain (network using hubs) you might be experiencing the effect of high load on such a kind of network. If you have seperate collision domains (network using switches), try enabling auto-negotiation for link-speed and -mode (i.e. "MBit/s" and "Duplex-Type"). Also check that everyone is in the same network (IP-network, i.e. everyones addresses are between 192.168.0.1 and 192.168.0.254). I do not think that splitting your network and putting a router in between is gonna help you very much.
We have a modem first - Main switch - hubs - computers We use hubs because we have 2 person in a office and only one ethernet plug into the wall. The Modem is our router, DHCP, DNS as well. Probably not a good solution, right? Q: How do I connect to our switch? I don't think there's a IP for it. When you say enable auto-negotioation, do you mean there's something that you switch manually on the switch?
Sebastian Schneider wrote:
On 2: Btw, your modem seems to be a router. Otherwise, it would probably not have an IP address at all. If it also has a DHCP-server, see that only one is running (modem/router or server), two might cause some trouble. If you want to use your server for DNS and DHCP, disable DHCP in the router and configure the server to look-up any unknown address via router / ISP-DNS. The clients should then be set to use the server for DNS.
Yes, our Modem is our only DHCP, because I uninstalled the DHCP service from the server. I tried to use our server as DHCP but I thought the internet would not work when the server is shut down. Server is on all the time but I just didn't want the other computers to be dependent on it. Q: What do you think about this situation? PS: Our internet works fine though - no one's complaining about the internet speed. Thanks Sebastian, Chandman -- modified at 14:13 Friday 9th June, 2006
Chandman wrote:
We have a modem first - Main switch - hubs - computers We use hubs because we have 2 person in a office and only one ethernet plug into the wall. The Modem is our router, DHCP, DNS as well. Probably not a good solution, right?
It can't say it is good or not because it is limite to your organization resource that invest for an IT equipment.
Chandman wrote:
Q: How do I connect to our switch? I don't think there's a IP for it. When you say enable auto-negotioation, do you mean there's something that you switch manually on the switch?
Connect your modem to your computer. You computer need to have a network card and connect the network from this network card to a switch. And connect the other computer to this switch too.
Chandman wrote:
I tried to use our server as DHCP but I thought the internet would not work when the server is shut down. Server is on all the time but I just didn't want the other computers to be dependent on it. Q: What do you think about this situation?
Try to read about Description of internet connection sharing[^] and Internet connection sharing in windows xp[^]. Or check this result[^] to find addition resource about internet connection sharing information.
-
Chandman wrote:
Thank you for your response Roath.
My name is Kanel, Please call me Kanl.
Chandman wrote:
Yes we have Windows XP Professional and few Home editions aswell. But I found out that if I set the Workgroup same as our domain name, the computer becomes a part of the network.
If you have windows xp home edition, you won't be able to join your computer to a domain controller. It doesn't mean you put the same name and you contact communicate with each other. Whether you put a difference name, you still communicate with them but you will see a workgroup and a domain in My network place in your computer. Difference between workgroup and client/server is the way that network administrator manage the network resource.
Chandman wrote:
Yes. Our Windows Server 2000 runs a DNS server. How should I go about configuring it? In our server - in the DNS console, I just noticed that we have our server ip address for the forward lookup zones. But we don't have anything in the reverse lookup zones. Is that an issue? I am also thinking that I should set all computer's preffered DNS to our server - not our modem. But I have to have some way to forward that to our gateway if it's outgoing request outside of our LAN. So I'm not so sure on this eigther.
There are many step to promote your standa alone server to become a primary domain controller. You have to configure, static IP address, DNS, configure friendly name, install DNS component and create forward look zone and revers look up zone (there is more technical detail to create these zone), test DNS service whether your configure properly then finally promote your stand alone server by typing DCPROMO command from the run dialog box. I recommend you to read this aritlce[^] to gain more knowledge about managing your network environment.
Chandman wrote:
About router: I've seen many people having a [ WAN - modem - router - switch - computers] set up. Though, our current configuration is set up in a way that we don't have a router in between our switch and modem - therefore our modem is acting like a router,
Roath Kanel wrote:
There are many step to promote your standa alone server to become a primary domain controller. You have to configure, static IP address, DNS, configure friendly name, install DNS component and create forward look zone and revers look up zone (there is more technical detail to create these zone), test DNS service whether your configure properly then finally promote your stand alone server by typing DCPROMO command from the run dialog box.
our server is already DC. running DNS. has an static IP address. DHCP is working completely fine from our "DSL" Modem (supposedly our router). I am confident with the set up. I am just more concerned about the speed and I think there's just a little trick I have to do to get the accessing speed of shared files accross the network boosted up. I'll read those articles. Thank you again for all your help. Chandman
-
Roath Kanel wrote:
There are many step to promote your standa alone server to become a primary domain controller. You have to configure, static IP address, DNS, configure friendly name, install DNS component and create forward look zone and revers look up zone (there is more technical detail to create these zone), test DNS service whether your configure properly then finally promote your stand alone server by typing DCPROMO command from the run dialog box.
our server is already DC. running DNS. has an static IP address. DHCP is working completely fine from our "DSL" Modem (supposedly our router). I am confident with the set up. I am just more concerned about the speed and I think there's just a little trick I have to do to get the accessing speed of shared files accross the network boosted up. I'll read those articles. Thank you again for all your help. Chandman
Chandman wrote:
I am just more concerned about the speed and I think there's just a little trick I have to do to get the accessing speed of shared files accross the network boosted up.
Try to do your own benchmark about internet connection speed and contact to ISP about an internet connection speed.
-
Sebastian Schneider wrote:
On 1: If you are in a single collision domain (network using hubs) you might be experiencing the effect of high load on such a kind of network. If you have seperate collision domains (network using switches), try enabling auto-negotiation for link-speed and -mode (i.e. "MBit/s" and "Duplex-Type"). Also check that everyone is in the same network (IP-network, i.e. everyones addresses are between 192.168.0.1 and 192.168.0.254). I do not think that splitting your network and putting a router in between is gonna help you very much.
We have a modem first - Main switch - hubs - computers We use hubs because we have 2 person in a office and only one ethernet plug into the wall. The Modem is our router, DHCP, DNS as well. Probably not a good solution, right? Q: How do I connect to our switch? I don't think there's a IP for it. When you say enable auto-negotioation, do you mean there's something that you switch manually on the switch?
Sebastian Schneider wrote:
On 2: Btw, your modem seems to be a router. Otherwise, it would probably not have an IP address at all. If it also has a DHCP-server, see that only one is running (modem/router or server), two might cause some trouble. If you want to use your server for DNS and DHCP, disable DHCP in the router and configure the server to look-up any unknown address via router / ISP-DNS. The clients should then be set to use the server for DNS.
Yes, our Modem is our only DHCP, because I uninstalled the DHCP service from the server. I tried to use our server as DHCP but I thought the internet would not work when the server is shut down. Server is on all the time but I just didn't want the other computers to be dependent on it. Q: What do you think about this situation? PS: Our internet works fine though - no one's complaining about the internet speed. Thanks Sebastian, Chandman -- modified at 14:13 Friday 9th June, 2006
Well, your DSL(?) modem is a router, DHCP, DNS. That is not too bad. The network layout seems to be ok: Switch, then hubs, with the switch going to the router. That is, for a 20 PC network, totally acceptable. Like Kanel, I know that NPO (non-profit organizations) usually have to turn every cent twice before spending it. Basically, your system seems to be OK. I really suspect that there is some misconfiguration. The XP-Home PCs can be difficult to connect to a domain. I suggest (if that is not already the case) that the server be connected to the switch directly. All other computers should be set (Network Settings) to use 10 Mbit/Full Duplex. This part of the configuration is not standardized, but you find these setting, if you open the status-dialog of the LAN-Connection (double-click it), then click the "Properties" or "Advanced" Button in the lower left, then the "Advanced"-Button right next to the Network Interface Name (should be a disabled text-edit). There will be a listbox with several settings. Usually, one or two of them change the link-speed and duplex mode. The server should be set to 100 MBit/s Full Duplex. Well, thats all I can say on the layout. And, frankly, there SHOULD not be any problems with so few clients. I've been using networks since I had to drill holes in cables (not that I knew anything about the concept back then), and I've never heard of shares taking so long to open, except for misconfiguration-issues. But then, your guys MIGHT constantly be sending something over the network (like transmitting files, streaming music from the web, stuff like that). That can kill any partially switched network, since the other computers on the same hub will generate a lot of collisions. If you can spend a few bucks, try to replace the hubs with 5-to-8-port switches. You still should first try to have the computers auto-configured by the DHCP. If its a modern router, it should transmit DNS and Gateway-Information during the auto configuration. The switch and modem probably wont care. The best thing probably would be to check, if someone uses streaming services or file-sharing software. If someone does, try to prevent those from doing that for a day or so, and monitor the performance. To change your IT-policy is up to you, if you believe that is necessary. This, however, is a guess. My employer, for example, forbids any use of streaming services, instant messangers and non-business VoIP. The network is fully switched (with about 10 hubs in the company for extension purposes) and
-
Roath Kanel wrote:
There are many step to promote your standa alone server to become a primary domain controller. You have to configure, static IP address, DNS, configure friendly name, install DNS component and create forward look zone and revers look up zone (there is more technical detail to create these zone), test DNS service whether your configure properly then finally promote your stand alone server by typing DCPROMO command from the run dialog box.
our server is already DC. running DNS. has an static IP address. DHCP is working completely fine from our "DSL" Modem (supposedly our router). I am confident with the set up. I am just more concerned about the speed and I think there's just a little trick I have to do to get the accessing speed of shared files accross the network boosted up. I'll read those articles. Thank you again for all your help. Chandman