Skip to main content

Posts

Showing posts from February, 2015

DOT11-4-MAXRETRIES

DOT11-4-MAXRETRIES: Packet to client XXXX.XXXX.XXXX reached max retries, removing the client. What you describe can be: 1. Bad RF coverage, so no matter what code version, it will remain happening. Get a "sh dot11 asssoc all" to see the signal level 2. Radio issue (bug), which may need troubleshooting. Easiest is to load latest code, and test from there. 3. Interference that is causing client to miss frames and/or AP not to hear correctly the ACK You can change the retry feature, do this: 1. go to enable mode 2. go to config (conf t) 3. in do0 4. packet ret 64 drop AP-02#sh run int do0 Building configuration... Current configuration : 456 bytes ! interface Dot11Radio0  no ip address  no ip route-cache  !  encryption mode wep mandatory  !VAIBHAVWIRELESSAP01  ! 0  packet retries 64 drop-packet Also add this command if required (config-if)# channel least-congested"

TCP 3-Way Handshake (SYN,SYN-ACK,ACK)

The TCP three-way handshake in Transmission Control Protocol (also called the TCP-handshake; three message handshake and/or SYN-SYN-ACK) is the method used by TCP set up a TCP/IP connection over an Internet Protocol based network . TCP's three way handshaking technique is often referred to as "SYN-SYN-ACK" (or more accurately SYN, SYN-ACK , ACK) because there are three messages transmitted by TCP to negotiate and start a TCP session between two computers . The TCP handshaking mechanism is designed so that two computers attempting to communicate can negotiate the parameters of the network TCP socket connection before transmitting data such as SSH and HTTP web browser requests. This 3-way handshake process is also designed so that both ends can initiate and negotiate separate TCP socket connections at the same time. Being able to n

Native VLAN Mismatches.

Error#1 Lets assume that one of the workstations on the network (PC 5) cannot connect to the internal web server WEB/TFTP, lets use the figure below as an example of a switched network, the first place you start will be at the Switch 2 to check if VLANs are properly configured. Looking at the diagram, switch port fa0/3 on Switch 2 is configured as a trunk port.  Oct 27 12:16:29.352 EET: %CDP-4-NATIVE_VLAN_MISMATCH: Native VLAN mismatch discovered on GigabitEthernet2/6 (2), with sw-el0 GigabitEthernet0/8 (1).   When you connect to switch S2, if there is an error on the switch port, it will appear on your console window, in this case there is and it looks like this:         S2#         #CDP-4-NATIVE VLAN_MISMATCH: Native VLAN mismatch discovered on          FastEthernet0/3  (100), with S1  FastEthernet0/3  (99). Using the show interfaces fa0/3 switchport command will display connectivity detail on the port. e.g         S2# show interfaces fa0/3 switchport         Name:  fa0/3