Hi Ivan,
Mac addresses only have local significance. So for your scenario, host X
sends a packet with it's own MAC address as the source and the router TR
interface as the destination MAC address. The router then rebuilds the
packet and sends it out the ethernet interface with the Ethernet
Hmmmwho is your telco? For the old Concert network (now BT Ignite) I
know they use ANSI LMI with a keep-alive interval of 10 secs. Make sure your
settings match your telco's.
What I always advise to do is to use a sniffer to see what's actually going
on on the line. This way you can quickly
Hey Mark,
First thing to do is use filters. Personally I use NAI's Sniffer Pro, which
quickly allows you to select a session based on IP addresses and/or
protocol. Ethereal should have this functionality as well.
First create a filter based on the server's IP address, and look for any
Use a sniffer in combination with this log. This will help you identify
which traffic opens the DDR link and which not.
If there are any other ways, let me know.
Rgds,
Crestion
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7i=44815t=44798
Hey George,
Before you start taking any actions, first use a Sniffer to see what is
causing the delay. It's no use implementing anything unless you know it's
going to be effective.
Hth,
Crestion
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7i=44604t=44355
Hi Rich,
First thing to do is to trace the signal. I.e. what are the physical limits
of the RF. Special wireless tools (like the Sniffer Wireless) are available
to help you with this, but the software delivered with your Aironet can tell
you a lot as well.
If the signal stays within the
Hi Murali,
This definitely is a strange problem. I would advise to put sniffers on both
ends of the connection (so one between the NT Server and Router A and one
between router C and the Win98 client), try to logon and than watch the
packet flow for any anomalies. Especially keep an eye on the
Hi Pierre,
A bit-time is the time it takes to send a bit.
For 10Mb Ethernet a bit-time is a 100 nanoseconds (10 Megabit per second, so
1 bit per 100 nanoseconds), for Fast Ethernet it is 10 nanoseconds and so on.
So if a workstation on a Fast Ethernet network were to wait 5 bit-times, it
Steven,
Way off Hmmmthe only thing I indeed forgot to mention is the
directional antenna-danger, but to say I'm way off...that's a strong
statement.
First of all let me clarify myself. My final comment, Again, which solution
to go for depends on your security needs and how much you're
Btwthere's a great article on Wireless security on
http://www.networkcomputing.com/1303/1303ws2.html
This article also shows the importance of finding the right balance between
risk assessment, cost and convenience.
Message Posted at:
to do
too much of packet processing..
i would like to know if i am going in the right direction.
Crestion --thanks for the mail.. i shall do that and let me see what it has
to say ?
can Etherpeek monitor serial links across on router ?
thanks,
Murali
-Original Message-
From: C restion
For 16Mb Token Ring that would lead to 1 bit per 62.5 nanoseconds. I.e. one
bit-time is 62.5 nanoseconds.
Rgds,
Remmert
From: Pierre-Alex Guanel
To: C restion ,
Subject: RE: bit time [7:44144]
Date: Tue, 14 May 2002 09:47:44 -0500
Thank you Remmert. Can I assume that with a 16 Mb Token
12 matches
Mail list logo
