Discussion Locked

Network Neigborhood

0 helpful
4 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am running a Win NT 4.0 server with 3 workstations. I frequently run an internet sharing program for the workstations. The internet sharing is still fast but the icons in Network Neighborhood take forever to show up and once they do it takes as long to bring up the drive on the workstation. My NIC cards are Netgear FA310TX 10/100 with an Intel 8 Port 10/100 Auto sensing port hub. I have setup the network so many times due to issues when clicking on a workstation in network neighborhood myhair is turning green. After the original setup which includes a format and complete reinstalation of all operating systems and nic cards with all the latest drivers the network works fine. Very fast access speeds and fast file transfers and also fast internet sharing. Eventually when I click on a workstation in Network neighborhood it just sits there trying to find the workstation. It does finally find the workstation but it is very slow. What gives. Why does it work initially and then slow to a crawl. I have pinged the workstations and this is the result. (1) Workstation = Ping Statistics for 192.168.0.3. Round trip times in milli-seconds: Minimum=oms, Maximum = 1ms, Average = oms. (2) Workstation = Ping Statistics for 192.168.0.2 Round trip times in milli-seconds: Minimum=1ms, Maximum=1ms, Average=1ms. I would certainly appreciate any help in stabilyzing my system so that I may use my network as it is suppose to work. I try rebooting the server and workstations but to no avail. Still very slow. I have run virus programs including F-Prot and Mcafee and their are no viruses. Again this rebuild is only a few days old. By the way the server IP address is 192.168.0.1 with the subnet being 255.255.255.0. All the subnets are the same as above. I am Totally stumped. I have tried different Netgear and 3com NIC cards in every combination.

Please help.

Thanks

Mike R. Davis

4 replies

by ball5ball5

I'm going to try to help you with this. I had this exact problem some time ago, and I am trying to remember how I solved it. First of all, you need to look at what you are using for your Internet Connection Sharing (ICS). You don't actually need a 3rd party software solution for this. ICS can be accomplished in an NT environ simply by "gatewaying" all the other boxes to the connected box, unless it's DSL or Cable Modem. In that case, get a little freebie called RASPPPOE. gem of a program.
Next, you have to look at how you are connecting all these boxes- DHCP only, or do you have all the other protocols (WINS,DNS,NWLINK,NETBEUI,Apple, IPX/SPX etc) running also? The only things you need are TCP/IP & DHCP. All networks see TCP/IP.Everything else will slow it down considerably. Next- check to see what Services are running. RAS? Do you need that in your environ? If not, disable it, as well as all the rest of the unecessary
Services. Someone that follows me will undoubtedly check me onthis, so look for further postings to this, but this ought to give you somewhere to start looking. Good Luck.

-jim

by admin

Personally I would disable DHCP and run static ip's. For some really odd reason I have seen DHCP be really slow at times, especially once the install is not so "fresh" in win. I really don't know why, but statics seem to take care of it when it happens. Also, I agree on the gateway. I would solve this with hardware if possible. There are several good gateways out there for small networks. Second to this I would build one from an old box lying around, if you have or can get one given to you and put a nic and modem (or dsl router or ?) in it you could take this function off the server and firewall your server, at least somewhat. Actually there are a lot of variables I am unsure about here too..... Do you have a dial-up ppp? I am assuming you do and it's dynamic. Do you have 2 instances of DHCP running... one with NT server and one with your ICS program?
Basically, I don't know enough about your particular setup, but I would try static ip's with a hardware gateway, and bet it will work better, as well as isolate your 192.168.xxx.xxx boxes from your internet address, especially if you're static.
Hope this helps, if not, no worries :)

by draconis

This is a common problem with networks in nt4. I have 95,98 and nt workstations with nt4 server and proxy2. I also experienced the same darn problem but did overcome it to some extent. You didn't menion the protocols you are using. Also whether any other servers like 'wins' or 'dns' are present or not? As ball5ball5 said get rid of any protocols other than tcp/ip. Now this is important, get hold of a wins server or use LMHosts file for name resolution. If you are using wins and dhcp don't forget to mention the wins server ip addrs. Even if you let go dhcp and use statics, make sure the primary wins server addrs is there. Alternatively you can go ahead with a central LMHosts file where the domain and the server is clearly mentioned using #PRE #DOMAIN(you know...). This should speed up the access speed between workstations. Generally the slow speed is due to lack of proper name resolution means. However if you have already done what's given above, check out the wins or LMHosts file 'cozcertainly the nodes are not able to resolve the names. (I believe that there are no errors in the general setup of the network.)
Hope this helps you...

by gordon

A lot of interesting responses. A lot of good ideas.
We do quite a few small business networks and make every effort to keep a simple network simple. (troublefree)
The Internet connections and the speed of network neighborhood are two separate issues.
Solve network neighborhood first.
The fastest and easiest protocol is netbeui. Use it only,(remove all other protocols) for a starter. To see other computers and their drives quickly you must share and then map the drives. Once this is done and working fast and reliable, add Tcpip. Leave both protocols operating. For a network with 3 workstations I would set static IP's. (192.168.1.10 thru 14) Purchase a single port Linksys router (or equivalent) set it for a static ip of 192.168.1.1.Adjust the other settings to match the requirement of your isp. Be sure to set DNS in the router. Plug it in to one of your ports on the Intel hub. It should work!

A couple of bits of info. Be sure to download the latest firmare patch to the router.

Somebody will comment on the use of netbeui. Netbeui creates a lot of traffic, right. But not so much as to cause any problems on a four node network. This setup works great. I have installed it many times for many customers.

Feel free to contact me at
gordon@theautomatedoffice.com

Good Luck
Gordon

This discussion is closed to new replies.