DUX COMPUTER DIGEST

 

Site Search

Site Info

Home » Forums » Forum Archives » Networking and Internet Sharing » Topic # 1678

Not so close encounters of the TCP/IP kind!
Mazinger Z Feb-07-02 08:17 PM
HELP!
What is the best way to bind your protocols so that you can browse a home network fast?
I have a small home network and when I try to see stuff I have on other computers (in the network) the process is super slow...the little sand clock icon keeps going and going and maybe half a minute later, or sometimes a minute later I finally connect to the other computer.
I have TCP/IP and NetBuie. In the Binding order I have TCP/IP on top of Netbuei. The strange thing is that I read that I don't need NetBuei but when I remove it then it doesn't find any computers on the network, "Network not accessible" so I have to reinstall Netbuei in order to access the network, is this normal?

Thanks!!!
PS: I have 10/100 Nics! and on the network status it says that the running speed is 100.0 Mbps.


1. RE: Not so close encounters of the TCP/IP kind!
DT71 Feb-08-02 02:03 AM
In response to message 0
> The strange thing is
>that I read that I
>don't need NetBuei but when
>I remove it then it
>doesn't find any computers on
>the network, "Network not accessible"
>so I have to reinstall
>Netbuei in order to access
>the network, is this normal?

Your network is only using netbuei. TCP/IP is not configured correctly and thats why when u uninstall netbuei, you loose it. Since you can see stuff when buei is running, you know your hardware is communicating so you can concentrate
on TCP/IP settings. Then I would remove netbuei because having the two protocols can reduce speed.
I think the reason your speed is so slow when you try to connect to the other pc may be because the nic is searching for a valid ip address and cant obtain it then finally it gives up and you can see the other pc then by buei only.


2. RE: Not so close encounters of the TCP/IP kind!
Mazinger Z Feb-08-02 10:33 AM
In response to message 1
OK!
Now how do I set TCP/IP correctly?
I've followed every step and it doesn't work!
I set the other W2K to get IP address automatically and as the instructions say, nothing else should be done, but it doesn't work!
help!

3. RE: Not so close encounters of the TCP/IP kind!
lbyard Feb-08-02 06:20 PM
In response to message 2
Where are they going to get them? Do you have a DHCP server running? Larry

4. RE: Not so close encounters of the TCP/IP kind!
Mazinger Z Feb-11-02 07:41 AM
In response to message 3
problem solved!!!
TCP/IP is configured prperly and Netbuei is unistalled!!!
System is running great!

Thanks Larry!


5. RE: Not so close encounters of the TCP/IP kind!
lbyard Feb-11-02 05:42 PM
In response to message 4
Well, share the knowledge with other readers. What exactly did you do? Larry

6. RE: Not so close encounters of the TCP/IP kind!
Mazinger Z Feb-11-02 07:11 PM
In response to message 5
OK...
The problem was that I had not configured TCP/IP correctly. So,it was just using Netbuei just like you said. What did I do? I assigned each computer static IP address in the range of 192.168.0.X (I assigned 192.168.0.1 to the machine using AnalogX Proxy serve) Then I pinged all computers and got replies with no problems. I then removed the other protocols I had installed..Netbuei and IPX/SPX. I clicked My Network places again and the speed was amazing. No more delays in getting into another machine.
ICS is working great too...thanks to AnalogX. It's the solution that was recommended to me above somewhere in this chain of responses. After having major headaches over ICS not working on a W2Kpro/W98 environment, I decided to download that program (AnalogX Proxy) from AnalogX.com. it downloads in a flash and the setup is real easy. I recommend anyone having the same problem with ICS to give this alterative solution a try...it works.
PS: And for AOL users...Once you have installed AnalogX Proxy. You have to configure AOL to connect via Proxy...do the manual configuration and your Proxy server should be the IP address of the computer where you have Analogx Proxy running, then AOL wants you to indicate the port number, that port number should be 1080 and not 6588 like the AnalogX instructions indicate. AOL did not connect for me using 6588 but it did once I changed that to port number 1080. That configuartion is only for AOL users trying to run to connect using ICS. AnalogX Proxy is amazing!!!

Thanks again!


| Home | Guides | How to | Reviews | Online Store | FAQ | Forums | Forum Archives |
| Links | News | Newsletter | About Dux | Advertising | Contact Info | Privacy |