|
|
|||||||
| Networking Have a networking problem, connectivity issues, LAN/WAN probs? |
![]() |
|
|
Thread Tools | Search this Thread | Display Modes |
|
|
#1 |
|
Guest
Posts: n/a
|
Here is my problem as best I understand it.
My workstation is connected to a TCP/IP network and I have dial up networking (TCP/IP) set up for my internet connection. (Not through the network) I have been having problems with very slow network performance of some applications, particularly DOS apps. Quite by accident, I discovered that when I have "IP Packet Size" set to Automatic, my network connection runs fine, but internet connection is slow. Conversely, when "IP Packet Size" is set to "Small" (576) my network connection is SSLLOOWW and internet is fine. This can't be impossible to fix, but it is beyond my world of knowledge. Suggestions Please???? Network card is a 3Com 3C905-TX Modem is a Viking 56k External/Serial port ------------------ |
|
|
|
#2 |
|
Registered User
Join Date: Jul 2000
Location: Huntington Beach, CA, USA
Posts: 1,515
|
Where are you setting IP Packet Size?
------------------ Death is lighter than a feather - duty heavier than a mountian.
__________________
Death is lighter than a feather - duty heavier than a mountian. The answer to your question is: 00110100 00110010 |
|
|
|
|
|
#3 |
|
Guest
Posts: n/a
|
I am setting the packet size in either the Networking properties "dial-up Adapter - Advanced Tab"
or to optimize internet connections I use EasyMTU and that changes it in the registry. |
|
|
|
#4 |
|
Guest
Posts: n/a
|
If all you are doing is transfering files on your lan and not plaing network games where you have to use tcp/ip. Then install netbui on both sets and change bindings on tcp where file and print sharingare not bound to tcp/ip on both sets then it will only be bound to netbuiand ipx/spx if installed . netbui is not a routable protocol but it huals bu**. On a small lan try this and you should be able to do what ever you want to your tcp/ip settings for modem. X
|
|
|
|
#5 |
|
Guest
Posts: n/a
|
Yeah, NetBEUI is our friend. Just make sure that you're not dangling port 139 out on the 'Net for hacker-fish to chomp. Steve Gibson at <a href="https://grc.com/x/ne.dll?bh0bkyd2">www.grc.com</a> Will tell you if you're wide open.
------------------ Thank you for calling the support desk! How may I disconnect you today? |
|
|
|
#6 |
|
Guest
Posts: n/a
|
So just to confirm... On a small (5 user) network, Netbui is what I should be using to connect to the server, and only use TCP/IP for the modems?
|
|
|
|
#7 |
|
Guest
Posts: n/a
|
Definitely do NetBEUI and make sure you have "printer and file sharing" unbound from TCP/IP. Also, shut down Ports 137 & 138 as well as 139. Ah, heck, get a firewall and increase the chance of keeping your system intact. Otherwise, hacks will chomp your 'puter and then it'll
------------------ You want the right answer?!? You must be asleep, 'cuz you're dreamin'...
|
|
|
|
#8 |
|
Guest
Posts: n/a
|
So netbui is faster than tcp ip on a network?
|
|
|
|
#9 | |
|
Guest
Posts: n/a
|
Quote:
On a p2p network that dosent need to be routed and as long as you stay under 15 or so sets the number 15 will vary with opion from 10 to 20. Still it will smoke other protocols in this envorment. MS wrote it specifically for this purpous. small p2p file sharing. X |
|
|
|
|
#10 |
|
Registered User
Join Date: Jun 2000
Location: Pinehurst, NC USA
Posts: 1,887
|
NetBEUI is fine for small networks, I know TCp/IP is 40% header 60% data, IPX/SPX is 20% header 80% data but am unsure what NetBEUI is, 10% header 90%data per packet?
------------------ we are number one, all others are number two......or lower
__________________
I'd rather be riding my motorcycle "I gotta have more cowbell, baby" Bruce Dickinson(Christopher Walken) |
|
|
|