wakebordboy Posted January 18, 2002 Share Posted January 18, 2002 hey guys whats up this is a problem I have run into while redoing a network I used 1.7GHz and 1.9GHz AMD XP processors and Soyo dragon Mobo's and run a domain under windows 2000 server with about 15 computers connected to it sharing 1 DSL 1.5 Mbps upload/download and a 3com hub and netopia router it seem to take forever for xp to talk to the server I also see this with 98 but not so much 98 (running xp pro) and backing up files to the server (xfering files to the server) and it seems slow as hell I was wondering guys since u might want to take a stab at this what is your opinion on this? just shoot some ideas out that I might not have thought of and as well the server speed is like 800MHz and no matter how far away the computers are it is just as slow (also running NAV 7.61 Corp on server with managed setup) thanks for the feedback :D Link to comment Share on other sites More sharing options...
ElGato Posted January 18, 2002 Share Posted January 18, 2002 Is NAV scanning network drives on startup? Link to comment Share on other sites More sharing options...
BrianR Posted January 18, 2002 Share Posted January 18, 2002 ... is more than likely the problem. Only a guess, without more information. HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionExplorerRemoteComputerNameSpace{2227A280-3AEA-1069-A2DE-08002B30309D} Delete the other key Data: Task Scheduler You should a definite increase in the speed of your connection. Link to comment Share on other sites More sharing options...
Aaron P Posted January 18, 2002 Share Posted January 18, 2002 DNS is setup correctly? What about your switches, try setting to 100/Full Duplex (or Half Duplex) depending on your config. Link to comment Share on other sites More sharing options...
Vlad Posted January 18, 2002 Share Posted January 18, 2002 God that's a hell of a run on sentence. Sounds like it could be a DNS or a security/authorization issue. Link to comment Share on other sites More sharing options...
Jon Posted January 18, 2002 Share Posted January 18, 2002 BrianR, any chance of a bit more info re:that key? What is is disabling, reasons to not delete etc..? :) Link to comment Share on other sites More sharing options...
JustinLerner Posted January 18, 2002 Share Posted January 18, 2002 Recommendations? Maybe, since you added a PC name to the Domain, your domain may be expecting another PC with the same name. It would be better to add the XP pc to domain from the XP PC. Try deleting the PC name from the Domain. Change the XP PC to a workgroup then reboot and join the XP PC to the domain, from the XP PC. Or, your network settings are incorrect, especially the XP PC. Are all other network settings OK? What about the TCP/IP netmask? DNS address, the network address of each PC on the network should be the same as the Server network address for authentication. Do you have a DNS server? XP/2000 clients of 2000 domain controllers expect to see Active Directory and that the Server/Domain controller is actually a domain name (like xxx.com). I don't know if you can actually use 2000 Server as a domain controller without DNS used on the local network, but if you can I'm certain the performance would increase with a local DNS server. (WINS is not needed.) Really, I think the problem is that the XP PC is not properly defined in the domain. If it is, you should be able to access the XP resources from the 2000 Domain controller in the Domain Manager. BTW. You should never DELETE a service from a SERVER or DOMAIN CONTROLLER (like the TASK Scheduler), especially via a REGISTRY edit. You can always disable or change how/if it runs in SERVICES. (AUTO, Manual, Disabled.) It would also be a mistake to disable the Schedule service if you have a production system used to run nightly reports, etc. Or if you have programmers working with the system. They can schedule BATCH commands to run late at night with the AT command . . . Who suggested that option? Link to comment Share on other sites More sharing options...
Chris123NT Posted January 18, 2002 Share Posted January 18, 2002 u guys are all wrong...I have 3 win 2000 servers and had the same problem a while back. Heres what u have to do. 1. Go into the DNS properties on the server and configure a reverse DNS lookup zone. 2. Make sure DHCP is enabled on the server and under scope options apply the ones that fit your network 3. this one is a must but the other 2 must be done as well MAKE SURE WINS IS ENABLED AND BROADCASTING OVER THE NETWORK. When i had the problem and i did these 3 things everything went great. My win xp comp now logs to the domain in 1.5 seconds! Let me know how this goes for you. if you do it right it WILL WORK :). Good luck Link to comment Share on other sites More sharing options...
wakebordboy Posted January 18, 2002 Author Share Posted January 18, 2002 Thanx Guys im going to try that last one let you know how it goes in an hour or so thanx and if theres anything u can thing of to make this network faster as far as config and settings go thanx guys let you know how it goes :D PS: Chris123NT Can you walk me through this from the start menu im kinda new at 2000 server Link to comment Share on other sites More sharing options...
Vlad Posted January 18, 2002 Share Posted January 18, 2002 . Go into the DNS properties on the server and configure a reverse DNS lookup zone. Yeah that obviously has nothing to do with dns, which 3 of us mentioned as a possible problem before you. But we're all wrong. Link to comment Share on other sites More sharing options...
Craig f Posted January 18, 2002 Share Posted January 18, 2002 I think I heard somewhere, that windows 2000/xp makes a DNS call to the server before using netbios.. it also helps if all ur cards are the same speed... then the switch doesn't have to do it. I have seen some switches cause that kind of delay before.. just a thought Link to comment Share on other sites More sharing options...
Chris123NT Posted January 19, 2002 Share Posted January 19, 2002 this involves reverse DNS. I will see if i can find detailed instructions on how to do this for ya and as for u vlad lighten up a bit. Link to comment Share on other sites More sharing options...
wakebordboy Posted January 19, 2002 Author Share Posted January 19, 2002 thanx bro it would really help cause server is new to me a complete detailed thing on the would rock thanx :-) i ow ya :D Link to comment Share on other sites More sharing options...
Craig f Posted January 19, 2002 Share Posted January 19, 2002 lookup Q174419 at support.microsoft.com http://search.support.microsoft.com/search...=&maxResults=25 Link to comment Share on other sites More sharing options...
wakebordboy Posted January 19, 2002 Author Share Posted January 19, 2002 cool thanx guys anything else that could speed up the network before i try anything? :D Link to comment Share on other sites More sharing options...
Geronimo Posted January 23, 2002 Share Posted January 23, 2002 you could turn off netbios. that would speed up the network, but you lose the computer browser service with that. Which means you need to know the UNC or map drives to the network resources you want to access. Also if you are using a DHCP server, make sure you set your domain name in the scope. It helps on looks. I dont know if you are going to use the DNS service, but if so set it up as a forwarder to your ISP's DNS servers. Then set your clients you use that as the primary DNS server in your DHCP scope. Link to comment Share on other sites More sharing options...
JustinLerner Posted January 23, 2002 Share Posted January 23, 2002 The guy who said WINS is necessary is half right. Although your intranet is small and doesn't require WINS, WINS will give greater benefits in a LARGE or even MEDIUM sized intranets or intranets predominantly with mixed versions of Windows (like your intranet). If your network has only Windows 2000/XP clients and client IP hosts that can use pure DNS to access network resources, then it should be OK, simple and the best increase of network speed to disable NetBIOS on each IP host. If you have other IP hosts, based on some Mac OS'es, Solaris, Linux, FreeBSD, these also work well without NetBIOS. However, if your intranet still has any Win9x or Win3.x IP hosts that need access to the network shares/resources, you should not disable NetBIOS on your server or sharing IP hosts, because the older version of Windows won't be able to get to get to network resources/shares without NetBIOS capability (neither can Win 2000/XP hosts get to Win 9x/3.x hosts/shares if NetBIOS is disabled). For speed on XP/2000 client hosts, you can still disable NetBIOS while leaving NetBIOS enabled on the 2000 domain controller/servers for older Windows versions. This will work well for speed, but still 2000/XP hosts cannot get to older Windows shares (on Win9x/3.x PC's or vice,versa.) This may be a security benefit! The fact is, since you also have a small DOMAIN (in # of client hosts), both WINS and DHCP is not needed (but DNS and Active Directory is still required for 2000 Server domain controllers), however you can still use DHCP if you so desire. Those older versions of Windows need correct DNS settings and subnetting without WINS and DHCP. Once again, in a mixed Windows environment of Win9x/3.x PC's, WINS may help improve network performance. Not using WINS relieves some of the load on your Server if it's not very optimised (since it's usually better for different servers to perform the different tasks of WINS/DHCP and DNS/Active Directory). If DHCP is not used, then you need to manually set each IP address (static). If you disable NetBIOS on certain hosts, WINS will also not work on those hosts and Windows browsing (by PC name or UNC) from or to those hosts will not work. The only option to connect to shared resources where NetBIOS is disable (only on XP/2000 clients) is to specify the IP (xxx.xxx.xxx.xxx) address of the sharing host, then you can see the appropriate shares on the respective host. If you need to set up VPN's (PPTP, or IPSEC L2TP) or VLAN's (hardware switches), you should use DHCP to make the connection assignments by the RRAS and the domain authentication/encryption easier. (DNS still required, but WINS may improve the intranet network speed in mixed Windows environments.) If you use WINS, you should also use DHCP. If you decide to use WINS and DHCP, you can also enable the Use NetBIOS Settings from DHCP Server option in your 2000/XP clients. If you don't use WINS and DHCP, you cannot use that option. BTW, browsing is often turned off on IP hosts or client computers in large networks, because the internal techsupport maintains the network shares and maps and to prevent the drag by hundreds to thousands of users "browsing" the corporate wan/man/lan. Link to comment Share on other sites More sharing options...
ahodes1 Posted January 26, 2002 Share Posted January 26, 2002 Originally posted by Chris123NT u guys are all wrong...I have 3 win 2000 servers and had the same problem a while back. Heres what u have to do. 1. Go into the DNS properties on the server and configure a reverse DNS lookup zone. 2. Make sure DHCP is enabled on the server and under scope options apply the ones that fit your network 3. this one is a must but the other 2 must be done as well MAKE SURE WINS IS ENABLED AND BROADCASTING OVER THE NETWORK. When i had the problem and i did these 3 things everything went great. My win xp comp now logs to the domain in 1.5 seconds! Let me know how this goes for you. if you do it right it WILL WORK :). Good luck WINS is the most important part... took my XP machine 2-3 minutes to log on until I set up WINS on the server Link to comment Share on other sites More sharing options...
Geronimo Posted January 26, 2002 Share Posted January 26, 2002 If you set up the XP and 2K clients right you could disable WINS and be fine. However, you need to have a 2K DC running, if not you have to have WINS running. I think it is just easier setting up WINS though. Link to comment Share on other sites More sharing options...
ahodes1 Posted January 26, 2002 Share Posted January 26, 2002 Originally posted by Geronimo If you set up the XP and 2K clients right you could disable WINS and be fine. However, you need to have a 2K DC running, if not you have to have WINS running. I think it is just easier setting up WINS though. Yeah you don't need WINS but strangely it dramatically speeds up domain logons in XP :ponder: Link to comment Share on other sites More sharing options...
Recommended Posts