Archived from groups: comp.dcom.lans.ethernet (More info?)

The arrangement is

Office 1 - approx 12 PC's
Switch 1 - router- internet
|
~ 50 metres
|
Switch 2
Office 2 - approx 30 PC's plus
2 x Windows servers + 1 Novell 3.12 server (IPX)

All Cat5e structured cabling.

Virtually all traffic is from PC to one or other of the servers in
Office 2. There are some networked printers in the system.

Traffic load should be relatively low. One central database on SQL
server on one server, Word Processing and Exchange on the other and a
small DOS application serving 4 users in Office 1 on the Novell
server. Some but not heavy internet access via Switch 1.

Office 1 staff experience regular delays of sometimes up to a couple
of minutes opening files or running an application.

The link between the switches is 100mbit (as is the rest of the
network except the 10mbit cards in the Novell server).

There is a second cable running from Office 1 to Office 2 but that has
not been connected and I'm not sure whether it is good practice to
have a parallel run.

One company has recommended to upgrade the link to a gigabit line but
I find the logic hard to follow since the servers will still have
100mbit cards.

Any helpful views welcomed.



--
AnthonyL

Archived from groups: comp.dcom.lans.ethernet (More info?)

In article <4264ebf8.8141787@news.zen.co.uk>,
AnthonyL <nospam@please.invalid> wrote:
>The arrangement is
>
>Office 1 - approx 12 PC's
> Switch 1 - router- internet
> |
> ~ 50 metres
> |
> Switch 2
>Office 2 - approx 30 PC's plus
> 2 x Windows servers + 1 Novell 3.12 server (IPX)
>
>All Cat5e structured cabling.
>
>Virtually all traffic is from PC to one or other of the servers in
>Office 2. There are some networked printers in the system.
>
>Traffic load should be relatively low. One central database on SQL
>server on one server, Word Processing and Exchange on the other and a
>small DOS application serving 4 users in Office 1 on the Novell
>server. Some but not heavy internet access via Switch 1.
>
>Office 1 staff experience regular delays of sometimes up to a couple
>of minutes opening files or running an application.
>
>The link between the switches is 100mbit (as is the rest of the
>network except the 10mbit cards in the Novell server).
>
>There is a second cable running from Office 1 to Office 2 but that has
>not been connected and I'm not sure whether it is good practice to
>have a parallel run.
>
>One company has recommended to upgrade the link to a gigabit line but
>I find the logic hard to follow since the servers will still have
>100mbit cards.
>
>Any helpful views welcomed.
>
>
>
>--
>AnthonyL


Did the switches cost less than $99 ?

Do they run the latest software ?

Is this a windows ActiveDirectry system ? If so, I think you have the
wrong DNS entry in the PC that see long delays.

You use the word "switch" and I suspect they are really routers. Are
they all on the same subnet ?

I imagine there could be other DNS/WINS problems.

Does office 1 access the NW server ?

I've seen problems when inexpensive equipment intended for
cookie-cutter configurations get used in ways that are not shown in
the manufacturer's glossy literature, as you are.

I've been burned connecting a cheapo switch to a Big Name switch
(Cisco in my case) and the Most Senior network engineer I know has
taught me that doing switch-to-switch connections on the cheap is a
No-No. He insists the the cheap end be a hub. FWIW.

--
a d y k e s @ p a n i x . c o m

Don't blame me. I voted for Gore.

Archived from groups: comp.dcom.lans.ethernet (More info?)

AnthonyL wrote:

> The arrangement is
>
> Office 1 - approx 12 PC's
> Switch 1 - router- internet
> |
> ~ 50 metres
> |
> Switch 2
> Office 2 - approx 30 PC's plus
> 2 x Windows servers + 1 Novell 3.12 server (IPX)
>
> All Cat5e structured cabling.
>
> Virtually all traffic is from PC to one or other of the servers in
> Office 2. There are some networked printers in the system.
>
> Traffic load should be relatively low. One central database on SQL
> server on one server, Word Processing and Exchange on the other and a
> small DOS application serving 4 users in Office 1 on the Novell
> server. Some but not heavy internet access via Switch 1.
>
> Office 1 staff experience regular delays of sometimes up to a couple
> of minutes opening files or running an application.
>
> The link between the switches is 100mbit (as is the rest of the
> network except the 10mbit cards in the Novell server).
>
> There is a second cable running from Office 1 to Office 2 but that has
> not been connected and I'm not sure whether it is good practice to
> have a parallel run.
>
> One company has recommended to upgrade the link to a gigabit line but
> I find the logic hard to follow since the servers will still have
> 100mbit cards.
>
> Any helpful views welcomed.

The question is where the bottleneck lies.

Cheap things to check.

First, run virus, adware, and spyware scans on _everything_ for which you
have a utility available. If you've got malware of some sort broadcasting
tons of traffic on your LAN then nothing's going to work right until you
fix that.

Ping each computer from each other computer and see if there is unusual
latency in either direction. Download a copy of qcheck
<http://www.ixiacom.com/products/qcheck/>, install it on a Windows box,
read the readme, and download the appropriate endpoints from the link in
the readme, then see what speed you're really getting between machines and
if you're getting the same speed both ways--if you're not then find out
why--most common cause would be a configuration error--either speed or a
duplex mismatch.

Windows server includes a tool called "network monitor". Go into the
Windows Server help and search on that and install it on your servers and
then watch the traffic going to and from them and see if you're seeing
anything coming in or going out that doesn't get a response. The free
version only monitors traffic to and from the server on which it is
installed, which is a significant limitation, but it's still a useful tool.

There's a tool called "Ethereal" <http://www.ethereal.com/> which is a
general-purpose network analyzer similar in purpose to "network
monitor"--ethereal is a free download--install it on one of your machines
that is experiencing the slowdown and watch the traffic and see if it's
sending anything for which it is not getting a response or receiving
anything to which it should be responding and isn't.

With those tools and some time you should be able to identify most network
problems--the trouble is that they're complex tools and it takes time to
learn to use them--there's a book, "Ethereal Packet Sniffing"
<http://www.amazon.com/exec/obidos/tg/detail/-/1932266828/qid=1113915990/sr=8-1/ref=pd_csp_1/104-1548119-3742340?v=glance&s=books&n=507846>
which may help. While you're about it, if you haven't already read them
try "Ethernet the Definitive Guide" by Charles Spurgeon
<http://www.amazon.com/exec/obidos/tg/detail/-/1565926609/qid=1113916220/sr=1-1/ref=sr_1_1/104-1548119-3742340?v=glance&s=books>
and "TCP/IP Illustrated"
<http://www.amazon.com/exec/obidos/tg/detail/-/0201633469/qid=1113916303/sr=1-1/ref=sr_1_1/104-1548119-3742340?v=glance&s=books>.

If you don't already have managed switches (and if you did and knew how to
use them you'd already know whether the link between them was the
problem--they'll tell you statistics on it) you might want to consider
picking up a couple of them off of ebay--Catalyst 2924s go for under $200
and sometimes under $100. I see Procurve 4000s, which for your use are
serious overkill but a bit noisy, for about the same.




--
--John
to email, dial "usenet" and validate
(was jclarke at eye bee em dot net)

Archived from groups: comp.dcom.lans.ethernet (More info?)

In article <d4323v0163g@news1.newsguy.com>,
J. Clarke <jclarke.usenet@snet.net.invalid> wrote:
>AnthonyL wrote:
>
>> The arrangement is
>>
>> Office 1 - approx 12 PC's
>> Switch 1 - router- internet
>> |
>> ~ 50 metres
>> |
>> Switch 2
>> Office 2 - approx 30 PC's plus
>> 2 x Windows servers + 1 Novell 3.12 server (IPX)
>>
>> All Cat5e structured cabling.
>>
>> Virtually all traffic is from PC to one or other of the servers in
>> Office 2. There are some networked printers in the system.
>>
>> Traffic load should be relatively low. One central database on SQL
>> server on one server, Word Processing and Exchange on the other and a
>> small DOS application serving 4 users in Office 1 on the Novell
>> server. Some but not heavy internet access via Switch 1.
>>
>> Office 1 staff experience regular delays of sometimes up to a couple
>> of minutes opening files or running an application.
>>
>> The link between the switches is 100mbit (as is the rest of the
>> network except the 10mbit cards in the Novell server).
>>
>> There is a second cable running from Office 1 to Office 2 but that has
>> not been connected and I'm not sure whether it is good practice to
>> have a parallel run.
>>
>> One company has recommended to upgrade the link to a gigabit line but
>> I find the logic hard to follow since the servers will still have
>> 100mbit cards.
>>
>> Any helpful views welcomed.
>
>The question is where the bottleneck lies.
>
>Cheap things to check.
>
>First, run virus, adware, and spyware scans on _everything_ for which you
>have a utility available. If you've got malware of some sort broadcasting
>tons of traffic on your LAN then nothing's going to work right until you
>fix that.
>
> Ping each computer from each other computer and see if there is unusual
>latency in either direction. Download a copy of qcheck
><http://www.ixiacom.com/products/qcheck/>, install it on a Windows box,
>read the readme, and download the appropriate endpoints from the link in
>the readme, then see what speed you're really getting between machines and
>if you're getting the same speed both ways--if you're not then find out
>why--most common cause would be a configuration error--either speed or a
>duplex mismatch.
>
>Windows server includes a tool called "network monitor". Go into the
>Windows Server help and search on that and install it on your servers and
>then watch the traffic going to and from them and see if you're seeing
>anything coming in or going out that doesn't get a response. The free
>version only monitors traffic to and from the server on which it is
>installed, which is a significant limitation, but it's still a useful tool.
>
>There's a tool called "Ethereal" <http://www.ethereal.com/> which is a
>general-purpose network analyzer similar in purpose to "network
>monitor"--ethereal is a free download--install it on one of your machines
>that is experiencing the slowdown and watch the traffic and see if it's


If the OP has two switches then using a traffic monitor will be
impossible unless the switches have management. If the switches have
management then you'll get counters, which might show something
interesting.

Assuming dumb switches I think the blinkenlights are as useful. If
the lights are not blinking he's got a problem with a timeout, not a
high traffic problem. DNS problems would show up as the former. If
you do have lots of blinking lights then the traffic monitor on a
Windows box may tell you something but because you have a switch it
can only see it's own traffic. ISTR that MS Monitor had software that
could be installed at other points in the network and feed data back
to the server for aggregation and analysis. That would solve the switch
limitation.

You can use perfmon.exe on any Windows box (except 98/me/dos) to
analysis in great detail what it's doing.

If your server (CPU and disk as shown by permon) is idle and the
lights are not blinking then you do';t have a capacity problem,
you've got a network design problem. IMO probably DNS.

You can put ethereal on each and every box (except NW) and analysis
the traffic and protocols.



>If you don't already have managed switches (and if you did and knew how to
>use them you'd already know whether the link between them was the
>problem--they'll tell you statistics on it) you might want to consider
>picking up a couple of them off of ebay--Catalyst 2924s go for under $200
>and sometimes under $100. I see Procurve 4000s, which for your use are
>serious overkill but a bit noisy, for about the same.
>

Agreed. Procurve boxes have a lifetime warranty so you can't go
wrong. As for my issue with cheap/noname switch-to-switch
connections, If you match brands, HP or Cisco you should be OK.


--
a d y k e s @ p a n i x . c o m

Don't blame me. I voted for Gore.

Archived from groups: comp.dcom.lans.ethernet (More info?)

Al Dykes wrote:

> In article <d4323v0163g@news1.newsguy.com>,
> J. Clarke <jclarke.usenet@snet.net.invalid> wrote:
>>AnthonyL wrote:
>>
>>> The arrangement is
>>>
>>> Office 1 - approx 12 PC's
>>> Switch 1 - router- internet
>>> |
>>> ~ 50 metres
>>> |
>>> Switch 2
>>> Office 2 - approx 30 PC's plus
>>> 2 x Windows servers + 1 Novell 3.12 server (IPX)
>>>
>>> All Cat5e structured cabling.
>>>
>>> Virtually all traffic is from PC to one or other of the servers in
>>> Office 2. There are some networked printers in the system.
>>>
>>> Traffic load should be relatively low. One central database on SQL
>>> server on one server, Word Processing and Exchange on the other and a
>>> small DOS application serving 4 users in Office 1 on the Novell
>>> server. Some but not heavy internet access via Switch 1.
>>>
>>> Office 1 staff experience regular delays of sometimes up to a couple
>>> of minutes opening files or running an application.
>>>
>>> The link between the switches is 100mbit (as is the rest of the
>>> network except the 10mbit cards in the Novell server).
>>>
>>> There is a second cable running from Office 1 to Office 2 but that has
>>> not been connected and I'm not sure whether it is good practice to
>>> have a parallel run.
>>>
>>> One company has recommended to upgrade the link to a gigabit line but
>>> I find the logic hard to follow since the servers will still have
>>> 100mbit cards.
>>>
>>> Any helpful views welcomed.
>>
>>The question is where the bottleneck lies.
>>
>>Cheap things to check.
>>
>>First, run virus, adware, and spyware scans on _everything_ for which you
>>have a utility available. If you've got malware of some sort broadcasting
>>tons of traffic on your LAN then nothing's going to work right until you
>>fix that.
>>
>> Ping each computer from each other computer and see if there is unusual
>>latency in either direction. Download a copy of qcheck
>><http://www.ixiacom.com/products/qcheck/>, install it on a Windows box,
>>read the readme, and download the appropriate endpoints from the link in
>>the readme, then see what speed you're really getting between machines and
>>if you're getting the same speed both ways--if you're not then find out
>>why--most common cause would be a configuration error--either speed or a
>>duplex mismatch.
>>
>>Windows server includes a tool called "network monitor". Go into the
>>Windows Server help and search on that and install it on your servers and
>>then watch the traffic going to and from them and see if you're seeing
>>anything coming in or going out that doesn't get a response. The free
>>version only monitors traffic to and from the server on which it is
>>installed, which is a significant limitation, but it's still a useful
>>tool.
>>
>>There's a tool called "Ethereal" <http://www.ethereal.com/> which is a
>>general-purpose network analyzer similar in purpose to "network
>>monitor"--ethereal is a free download--install it on one of your machines
>>that is experiencing the slowdown and watch the traffic and see if it's
>
>
> If the OP has two switches then using a traffic monitor will be
> impossible unless the switches have management.

If he's trying to monitor traffic on the entire network this is true.
However if he has a specific machine that is having problems then
monitoring traffic to and from that specific machine, which can be done by
putting the monitoring software on that machine, can sometimes tell a great
deal about its specific problem.

> If the switches have
> management then you'll get counters, which might show something
> interesting.
>
> Assuming dumb switches I think the blinkenlights are as useful.

They can tell you that "something is wrong"> If
> the lights are not blinking he's got a problem with a timeout, not a
> high traffic problem. DNS problems would show up as the former. If
> you do have lots of blinking lights then the traffic monitor on a
> Windows box may tell you something but because you have a switch it
> can only see it's own traffic. ISTR that MS Monitor had software that
> could be installed at other points in the network and feed data back
> to the server for aggregation and analysis. That would solve the switch
> limitation.
>
> You can use perfmon.exe on any Windows box (except 98/me/dos) to
> analysis in great detail what it's doing.

If the problem is internal to the machine. If it's sitting waiting for a
response that never comes perfmon may tell you that it's waiting but it
won't necessarily tell you what it's waiting _for_.

> If your server (CPU and disk as shown by permon) is idle and the
> lights are not blinking then you do';t have a capacity problem,
> you've got a network design problem. IMO probably DNS.

Possibly. Or possibly something specific to Windows.

> You can put ethereal on each and every box (except NW) and analysis
> the traffic and protocols.
>
>
>
>>If you don't already have managed switches (and if you did and knew how to
>>use them you'd already know whether the link between them was the
>>problem--they'll tell you statistics on it) you might want to consider
>>picking up a couple of them off of ebay--Catalyst 2924s go for under $200
>>and sometimes under $100. I see Procurve 4000s, which for your use are
>>serious overkill but a bit noisy, for about the same.
>>
>
> Agreed. Procurve boxes have a lifetime warranty so you can't go
> wrong. As for my issue with cheap/noname switch-to-switch
> connections, If you match brands, HP or Cisco you should be OK.

--
--John
to email, dial "usenet" and validate
(was jclarke at eye bee em dot net)

Archived from groups: comp.dcom.lans.ethernet (More info?)

On Tue, 19 Apr 2005 08:19:29 -0400, "J. Clarke"
<jclarke.usenet@snet.net.invalid> wrote:

>AnthonyL wrote:
>
>> The arrangement is
>>
>> Office 1 - approx 12 PC's
>> Switch 1 - router- internet
>> |
>> ~ 50 metres
>> |
>> Switch 2
>> Office 2 - approx 30 PC's plus
>> 2 x Windows servers + 1 Novell 3.12 server (IPX)
>>
>> All Cat5e structured cabling.
>>
>> Virtually all traffic is from PC to one or other of the servers in
>> Office 2. There are some networked printers in the system.
>>
>> Traffic load should be relatively low. One central database on SQL
>> server on one server, Word Processing and Exchange on the other and a
>> small DOS application serving 4 users in Office 1 on the Novell
>> server. Some but not heavy internet access via Switch 1.
>>
>> Office 1 staff experience regular delays of sometimes up to a couple
>> of minutes opening files or running an application.
>>
>> The link between the switches is 100mbit (as is the rest of the
>> network except the 10mbit cards in the Novell server).
>>
>> There is a second cable running from Office 1 to Office 2 but that has
>> not been connected and I'm not sure whether it is good practice to
>> have a parallel run.
>>
>> One company has recommended to upgrade the link to a gigabit line but
>> I find the logic hard to follow since the servers will still have
>> 100mbit cards.
>>
>> Any helpful views welcomed.
>
>The question is where the bottleneck lies.
>
>Cheap things to check.
>
>First, run virus, adware, and spyware scans on _everything_ for which you
>have a utility available. If you've got malware of some sort broadcasting
>tons of traffic on your LAN then nothing's going to work right until you
>fix that.
Pretty confident that machines are clean but some double checking may
not go amiss.
>
> Ping each computer from each other computer and see if there is unusual
>latency in either direction. Download a copy of qcheck
><http://www.ixiacom.com/products/qcheck/>, install it on a Windows box,
>read the readme, and download the appropriate endpoints from the link in
>the readme, then see what speed you're really getting between machines and
>if you're getting the same speed both ways--if you're not then find out
>why--most common cause would be a configuration error--either speed or a
>duplex mismatch.
This looks very interesting. I'll give it a go.
>
>Windows server includes a tool called "network monitor". Go into the
>Windows Server help and search on that and install it on your servers and
>then watch the traffic going to and from them and see if you're seeing
>anything coming in or going out that doesn't get a response. The free
>version only monitors traffic to and from the server on which it is
>installed, which is a significant limitation, but it's still a useful tool.
Well only two servers so not too much of a problem.
>
>There's a tool called "Ethereal" <http://www.ethereal.com/> which is a
>general-purpose network analyzer similar in purpose to "network
>monitor"--ethereal is a free download--install it on one of your machines
>that is experiencing the slowdown and watch the traffic and see if it's
>sending anything for which it is not getting a response or receiving
>anything to which it should be responding and isn't.
>
>With those tools and some time you should be able to identify most network
>problems--the trouble is that they're complex tools and it takes time to
>learn to use them--there's a book, "Ethereal Packet Sniffing"
><http://www.amazon.com/exec/obidos/tg/detail/-/1932266828/qid=1113915990/sr=8-1/ref=pd_csp_1/104-1548119-3742340?v=glance&s=books&n=507846>
>which may help. While you're about it, if you haven't already read them
>try "Ethernet the Definitive Guide" by Charles Spurgeon
><http://www.amazon.com/exec/obidos/tg/detail/-/1565926609/qid=1113916220/sr=1-1/ref=sr_1_1/104-1548119-3742340?v=glance&s=books>
>and "TCP/IP Illustrated"
><http://www.amazon.com/exec/obidos/tg/detail/-/0201633469/qid=1113916303/sr=1-1/ref=sr_1_1/104-1548119-3742340?v=glance&s=books>.

Many thanks - I will leave this till later. I recall it being a bigger
subject than I wanted to get into on another issue last year.
>
>If you don't already have managed switches (and if you did and knew how to
>use them you'd already know whether the link between them was the
>problem--they'll tell you statistics on it) you might want to consider
>picking up a couple of them off of ebay--Catalyst 2924s go for under $200
>and sometimes under $100. I see Procurve 4000s, which for your use are
>serious overkill but a bit noisy, for about the same.
>
It didn't at the time seem a complex enough network to require managed
switches. I have a spare 2900 XL that I could hook up.


--
AnthonyL

Archived from groups: comp.dcom.lans.ethernet (More info?)

On 19 Apr 2005 08:03:30 -0400, adykes@panix.com (Al Dykes) wrote:

>In article <4264ebf8.8141787@news.zen.co.uk>,
>AnthonyL <nospam@please.invalid> wrote:
>>The arrangement is
>>
>>Office 1 - approx 12 PC's
>> Switch 1 - router- internet
24 PORT 10/100MBPS Unmanaged switches
PLANET SWITCH FNSW2400S

>> |
>> ~ 50 metres
>> |
>> Switch 2

2 x 24 PORT 10/100MBPS Unmanaged switches
Allied Telesyn AT-FS724I-30

>>Office 2 - approx 30 PC's plus
>> 2 x Windows servers + 1 Novell 3.12 server (IPX)
>>
>>All Cat5e structured cabling.
>>
>
>
>Did the switches cost less than $99 ?

24 PORT 10/100MBPS Unmanaged switches
PLANET SWITCH FNSW2400S
Allied Telesyn AT-FS724I-30

>
>Do they run the latest software ?

AFAIK there are no updates available

>
>Is this a windows ActiveDirectry system ?
Yes
>If so, I think you have the
>wrong DNS entry in the PC that see long delays.
Entries appear correct
>
>You use the word "switch" and I suspect they are really routers. Are
>they all on the same subnet ?
I think they are called switches. All on same subnet.
>
>I imagine there could be other DNS/WINS problems.
>
>Does office 1 access the NW server ?
Yes and in fact only office 1 accesses the NW server. No problems
with this.
>
>I've seen problems when inexpensive equipment intended for
>cookie-cutter configurations get used in ways that are not shown in
>the manufacturer's glossy literature, as you are.
I don't understand I'm afraid what I am doing so wrong. Are you
saying switch to switch is the wrong way to bridge the offices?
>
>I've been burned connecting a cheapo switch to a Big Name switch
>(Cisco in my case) and the Most Senior network engineer I know has
>taught me that doing switch-to-switch connections on the cheap is a
>No-No. He insists the the cheap end be a hub. FWIW.

So I should replace the Planet switch with a hub?

--
AnthonyL

Archived from groups: comp.dcom.lans.ethernet (More info?)

In article <42663bed.10009162@news.zen.co.uk>,
AnthonyL <nospam@please.invalid> wrote:
>On Tue, 19 Apr 2005 08:19:29 -0400, "J. Clarke"
><jclarke.usenet@snet.net.invalid> wrote:
>
>>AnthonyL wrote:
>>
>>> The arrangement is
>>>
>>> Office 1 - approx 12 PC's
>>> Switch 1 - router- internet
>>> |
>>> ~ 50 metres
>>> |
>>> Switch 2
>>> Office 2 - approx 30 PC's plus
>>> 2 x Windows servers + 1 Novell 3.12 server (IPX)
>>>
>>> All Cat5e structured cabling.
>>>
>>> Virtually all traffic is from PC to one or other of the servers in
>>> Office 2. There are some networked printers in the system.
>>>
>>> Traffic load should be relatively low. One central database on SQL
>>> server on one server, Word Processing and Exchange on the other and a
>>> small DOS application serving 4 users in Office 1 on the Novell
>>> server. Some but not heavy internet access via Switch 1.
>>>
>>> Office 1 staff experience regular delays of sometimes up to a couple
>>> of minutes opening files or running an application.
>>>
>>> The link between the switches is 100mbit (as is the rest of the
>>> network except the 10mbit cards in the Novell server).
>>>
>>> There is a second cable running from Office 1 to Office 2 but that has
>>> not been connected and I'm not sure whether it is good practice to
>>> have a parallel run.
>>>
>>> One company has recommended to upgrade the link to a gigabit line but
>>> I find the logic hard to follow since the servers will still have
>>> 100mbit cards.
>>>
>>> Any helpful views welcomed.
>>
>>The question is where the bottleneck lies.
>>
>>Cheap things to check.
>>
>>First, run virus, adware, and spyware scans on _everything_ for which you
>>have a utility available. If you've got malware of some sort broadcasting
>>tons of traffic on your LAN then nothing's going to work right until you
>>fix that.
>Pretty confident that machines are clean but some double checking may
>not go amiss.
>>
>> Ping each computer from each other computer and see if there is unusual
>>latency in either direction. Download a copy of qcheck
>><http://www.ixiacom.com/products/qcheck/>, install it on a Windows box,
>>read the readme, and download the appropriate endpoints from the link in
>>the readme, then see what speed you're really getting between machines and
>>if you're getting the same speed both ways--if you're not then find out
>>why--most common cause would be a configuration error--either speed or a
>>duplex mismatch.
>This looks very interesting. I'll give it a go.
>>
>>Windows server includes a tool called "network monitor". Go into the
>>Windows Server help and search on that and install it on your servers and
>>then watch the traffic going to and from them and see if you're seeing
>>anything coming in or going out that doesn't get a response. The free
>>version only monitors traffic to and from the server on which it is
>>installed, which is a significant limitation, but it's still a useful tool.
>Well only two servers so not too much of a problem.
>>
>>There's a tool called "Ethereal" <http://www.ethereal.com/> which is a
>>general-purpose network analyzer similar in purpose to "network
>>monitor"--ethereal is a free download--install it on one of your machines
>>that is experiencing the slowdown and watch the traffic and see if it's
>>sending anything for which it is not getting a response or receiving
>>anything to which it should be responding and isn't.
>>
>>With those tools and some time you should be able to identify most network
>>problems--the trouble is that they're complex tools and it takes time to
>>learn to use them--there's a book, "Ethereal Packet Sniffing"
>><http://www.amazon.com/exec/obidos/tg/detail/-/1932266828/qid=1113915990/sr=8-1/ref=pd_csp_1/104-1548119-3742340?v=glance&s=books&n=507846>
>>which may help. While you're about it, if you haven't already read them
>>try "Ethernet the Definitive Guide" by Charles Spurgeon
>><http://www.amazon.com/exec/obidos/tg/detail/-/1565926609/qid=1113916220/sr=1-1/ref=sr_1_1/104-1548119-3742340?v=glance&s=books>
>>and "TCP/IP Illustrated"
>><http://www.amazon.com/exec/obidos/tg/detail/-/0201633469/qid=1113916303/sr=1-1/ref=sr_1_1/104-1548119-3742340?v=glance&s=books>.
>
>Many thanks - I will leave this till later. I recall it being a bigger
>subject than I wanted to get into on another issue last year.
>>
>>If you don't already have managed switches (and if you did and knew how to
>>use them you'd already know whether the link between them was the
>>problem--they'll tell you statistics on it) you might want to consider
>>picking up a couple of them off of ebay--Catalyst 2924s go for under $200
>>and sometimes under $100. I see Procurve 4000s, which for your use are
>>serious overkill but a bit noisy, for about the same.
>>
>It didn't at the time seem a complex enough network to require managed
>switches. I have a spare 2900 XL that I could hook up.
>
>
>--
>AnthonyL


Replacing the noname switch with a hub is easy if you have one on
hand, and they are _really_ cheap on ebay. I can't see a 10/100 hub
being a serious bottleneck for the small site. It gives you a place
to plug a PC running etherreal. This is a long shot.

Do you have Activedirectory on your windows servers?

ActiveDirectory makes very specific requirement for DNS services and
the symptoms if you don't comply include long time delays. The easy
way for a small site to comply is to make one of your windows servers
your DNS server and point all the other machines at it.

I keep coming back to DNS/WINS problems. If you are not AD then who
are you using for DNS ? Putting a name/ipaddress entry for all your
servers in /etc/hosts on all your machines is one low-rent way to
fixthings for a small network. If that improves things then you need
to set up a real dns server and put things right.

Is the symptom in office1 reproducable on a specific PC ? If it is
then carry the PC to office2, plug it in and see if the problem
remains. If it/s on all machines or random, that tells you something
but I don;t know offhave what it is.

If you unplug your ISP connection do the symptoms change ?

Please make your responses more readable.



--
a d y k e s @ p a n i x . c o m

Don't blame me. I voted for Gore.

Archived from groups: comp.dcom.lans.ethernet (More info?)

AnthonyL wrote:

> On Tue, 19 Apr 2005 08:19:29 -0400, "J. Clarke"
> <jclarke.usenet@snet.net.invalid> wrote:
>
>>AnthonyL wrote:
>>
>>> The arrangement is
>>>
>>> Office 1 - approx 12 PC's
>>> Switch 1 - router- internet
>>> |
>>> ~ 50 metres
>>> |
>>> Switch 2
>>> Office 2 - approx 30 PC's plus
>>> 2 x Windows servers + 1 Novell 3.12 server (IPX)
>>>
>>> All Cat5e structured cabling.
>>>
>>> Virtually all traffic is from PC to one or other of the servers in
>>> Office 2. There are some networked printers in the system.
>>>
>>> Traffic load should be relatively low. One central database on SQL
>>> server on one server, Word Processing and Exchange on the other and a
>>> small DOS application serving 4 users in Office 1 on the Novell
>>> server. Some but not heavy internet access via Switch 1.
>>>
>>> Office 1 staff experience regular delays of sometimes up to a couple
>>> of minutes opening files or running an application.
>>>
>>> The link between the switches is 100mbit (as is the rest of the
>>> network except the 10mbit cards in the Novell server).
>>>
>>> There is a second cable running from Office 1 to Office 2 but that has
>>> not been connected and I'm not sure whether it is good practice to
>>> have a parallel run.
>>>
>>> One company has recommended to upgrade the link to a gigabit line but
>>> I find the logic hard to follow since the servers will still have
>>> 100mbit cards.
>>>
>>> Any helpful views welcomed.
>>
>>The question is where the bottleneck lies.
>>
>>Cheap things to check.
>>
>>First, run virus, adware, and spyware scans on _everything_ for which you
>>have a utility available. If you've got malware of some sort broadcasting
>>tons of traffic on your LAN then nothing's going to work right until you
>>fix that.
> Pretty confident that machines are clean but some double checking may
> not go amiss.
>>
>> Ping each computer from each other computer and see if there is unusual
>>latency in either direction. Download a copy of qcheck
>><http://www.ixiacom.com/products/qcheck/>, install it on a Windows box,
>>read the readme, and download the appropriate endpoints from the link in
>>the readme, then see what speed you're really getting between machines and
>>if you're getting the same speed both ways--if you're not then find out
>>why--most common cause would be a configuration error--either speed or a
>>duplex mismatch.
> This looks very interesting. I'll give it a go.
>>
>>Windows server includes a tool called "network monitor". Go into the
>>Windows Server help and search on that and install it on your servers and
>>then watch the traffic going to and from them and see if you're seeing
>>anything coming in or going out that doesn't get a response. The free
>>version only monitors traffic to and from the server on which it is
>>installed, which is a significant limitation, but it's still a useful
>>tool.
> Well only two servers so not too much of a problem.
>>
>>There's a tool called "Ethereal" <http://www.ethereal.com/> which is a
>>general-purpose network analyzer similar in purpose to "network
>>monitor"--ethereal is a free download--install it on one of your machines
>>that is experiencing the slowdown and watch the traffic and see if it's
>>sending anything for which it is not getting a response or receiving
>>anything to which it should be responding and isn't.
>>
>>With those tools and some time you should be able to identify most network
>>problems--the trouble is that they're complex tools and it takes time to
>>learn to use them--there's a book, "Ethereal Packet Sniffing"
>><http://www.amazon.com/exec/obidos/tg/detail/-/1932266828/qid=1113915990/sr=8-1/ref=pd_csp_1/104-1548119-3742340?v=glance&s=books&n=507846>
>>which may help. While you're about it, if you haven't already read them
>>try "Ethernet the Definitive Guide" by Charles Spurgeon
>><http://www.amazon.com/exec/obidos/tg/detail/-/1565926609/qid=1113916220/sr=1-1/ref=sr_1_1/104-1548119-3742340?v=glance&s=books>
>>and "TCP/IP Illustrated"
>><http://www.amazon.com/exec/obidos/tg/detail/-/0201633469/qid=1113916303/sr=1-1/ref=sr_1_1/104-1548119-3742340?v=glance&s=books>.
>
> Many thanks - I will leave this till later. I recall it being a bigger
> subject than I wanted to get into on another issue last year.
>>
>>If you don't already have managed switches (and if you did and knew how to
>>use them you'd already know whether the link between them was the
>>problem--they'll tell you statistics on it) you might want to consider
>>picking up a couple of them off of ebay--Catalyst 2924s go for under $200
>>and sometimes under $100. I see Procurve 4000s, which for your use are
>>serious overkill but a bit noisy, for about the same.
>>
> It didn't at the time seem a complex enough network to require managed
> switches. I have a spare 2900 XL that I could hook up.

I think you'll find it very helpful, both because it can collect statistics
on port traffic and because it will let you set up a monitoring port that
lets you see all network traffic that goes through that switch.

--
--John
to email, dial "usenet" and validate
(was jclarke at eye bee em dot net)

Archived from groups: comp.dcom.lans.ethernet (More info?)

AnthonyL <nospam@please.invalid> wrote:
> Office 1 staff experience regular delays of sometimes up to
> a couple of minutes opening files or running an application.

Ouch! This sounds like a config (DNS/WINS) problem.
I hope you're not running NETBIOS.

One longshot -- you mentioned "structured cabling". Are you
sure it's good? Proper Cat5e jacks and factory patchcords?
All field/home-crimped plugs are suspect. Splitting a pair
is too easy. High data errors in one direction usually result.

-- Robert in Houston