Slow LAN

[Pat Glenn]

Having recently acquired some older computers I am now setting up a P2P
network.

All machines:
-New installation of appropriate OS's
-No apparent hardware issues
-Using thin-net 10base2
-File and printer sharing enabled
-Logging on with administrator account (same password and user)
-NetBEUI installed
-IPX/SPX installed
-TCPIP installed
(Firewalls are OFF for now)

Machine A:
-Win2K (NT5)
-Modem for internet connection
-requires (ctrl-alt-del) log-on
-IP Addres set to 192.168.0.1/255.255.255.0

Machine B:
-WinXP Home
-requires log-on
-IP Addres set to 192.168.0.25/255.255.255.0

Machine C:
-WinME
-requires log-on
-IP Addres set to 192.168.0.50/255.255.255.0

After fighting for a few evenings, all machines can now see each other and
access each others resources. I'm having a bit of trouble with the ICS, but
that seems to be resolvable (I've had it working off and on a few times -
currently off, but that's another story...)

B > A, B > C, C > A, and C > B are all very fast connections. The NT machine
however, seems to have a hard time resolving the connections. The little
searching flashlight comes on every time you go to the network. It takes
roughy 60 - 90 seconds to resolve the connection every time you go to the
resource. Once you get a lock on things, it goes lightning fast, but until
then you might as well fire up the coffee pot...

Any ideas?

Thanks

 

[Pegasus \(MVP\)]

Having recently acquired some older computers I am now setting up a P2P
network.

All machines:
-New installation of appropriate OS's
-No apparent hardware issues
-Using thin-net 10base2
-File and printer sharing enabled
-Logging on with administrator account (same password and user)
-NetBEUI installed
-IPX/SPX installed
-TCPIP installed
(Firewalls are OFF for now)

Machine A:
-Win2K (NT5)
-Modem for internet connection
-requires (ctrl-alt-del) log-on
-IP Addres set to 192.168.0.1/255.255.255.0

Machine B:
-WinXP Home
-requires log-on
-IP Addres set to 192.168.0.25/255.255.255.0

Machine C:
-WinME
-requires log-on
-IP Addres set to 192.168.0.50/255.255.255.0

After fighting for a few evenings, all machines can now see each other and
access each others resources. I'm having a bit of trouble with the ICS, but
that seems to be resolvable (I've had it working off and on a few times -
currently off, but that's another story...)

B > A, B > C, C > A, and C > B are all very fast connections. The NT machine
however, seems to have a hard time resolving the connections. The little
searching flashlight comes on every time you go to the network. It takes
roughy 60 - 90 seconds to resolve the connection every time you go to the
resource. Once you get a lock on things, it goes lightning fast, but until
then you might as well fire up the coffee pot...

Any ideas?

Thanks

What is the point of having three separate protocols? TCP/IP
will meet all your requirements - the rest will only confuse the
issue. Uninstall NetBEUI and IPX/SPX, then review your DNS
settings.

Is "thin-net 10base2" coax wiring? If yes then you should
replace it with CAT5 cabling. Much easier to debug, much
less chance of interference between machines.

 

[Pat Glenn]

What is the point of having three separate protocols? TCP/IP

will meet all your requirements - the rest will only confuse the
issue. Uninstall NetBEUI and IPX/SPX, then review your DNS
settings.

It would probably make life simpler. I was going from old information. I
understand that it used to be for security that you ran other protocols on
the LAN and left TCPIP for communication. (I think I need to get some
updated books) I might probably still need NetBEUI though. Unless adaptec
has re-written their SCSI driver (unlikely for my old scanner) I require
that protocol for network scanner sharing.

Is "thin-net 10base2" coax wiring? If yes then you should
replace it with CAT5 cabling. Much easier to debug, much
less chance of interference between machines.

Welcome to the 'caveman age' of computing... It's coax with BNC connectors.
No CAT5. Why? No hub - Yet. Perhaps some day...

 

[Pegasus \(MVP\)]

See below.

It would probably make life simpler. I was going from old information. I
understand that it used to be for security that you ran other protocols on
the LAN and left TCPIP for communication. (I think I need to get some
updated books) I might probably still need NetBEUI though. Unless adaptec
has re-written their SCSI driver (unlikely for my old scanner) I require
that protocol for network scanner sharing.

*** I doubt it very much.

Welcome to the 'caveman age' of computing... It's coax with BNC connectors.
No CAT5. Why? No hub - Yet. Perhaps some day...

*** Have you checked the prices of hubs lately? You can probably
*** get 10 MBits/s hubs second-hand for nothing - I've got some
*** gathering dust. Time to upgrade!