Solved

Slow VPN Performance

Posted on 2006-11-10
4
1,077 Views
Last Modified: 2013-11-29
I was trying to transfer a few very small (10 KB) word docs over the VPN today, and it kept failing after a few minutes. There was very little network activity. I wonder if it is an MTU issue. I used wireshark to get the following:

No.     Time        Source                Destination           Protocol Info
      1 0.000000    00:ff:b4:9b:b3:e5     Spanning-tree-(for-bridges)_00 STP      Conf. Root = 32768/02:ff:b4:9b:b3:e5  Cost = 0  Port = 0x8000

Frame 1 (52 bytes on wire, 52 bytes captured)
IEEE 802.3 Ethernet
Logical-Link Control
Spanning Tree Protocol

No.     Time        Source                Destination           Protocol Info
      2 0.841445    10.69.69.4            10.69.69.255          NBNS     Name query NB <01><02>__MSBROWSE__<02><01>

Frame 2 (92 bytes on wire, 92 bytes captured)
Ethernet II, Src: AppleCom_9f:1c:06 (00:16:cb:9f:1c:06), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Internet Protocol, Src: 10.69.69.4 (10.69.69.4), Dst: 10.69.69.255 (10.69.69.255)
User Datagram Protocol, Src Port: 52013 (52013), Dst Port: netbios-ns (137)
NetBIOS Name Service

No.     Time        Source                Destination           Protocol Info
      3 2.000320    00:ff:b4:9b:b3:e5     Spanning-tree-(for-bridges)_00 STP      Conf. Root = 32768/02:ff:b4:9b:b3:e5  Cost = 0  Port = 0x8000

Frame 3 (52 bytes on wire, 52 bytes captured)
IEEE 802.3 Ethernet
Logical-Link Control
Spanning Tree Protocol

No.     Time        Source                Destination           Protocol Info
      4 4.000199    00:ff:b4:9b:b3:e5     Spanning-tree-(for-bridges)_00 STP      Conf. Root = 32768/02:ff:b4:9b:b3:e5  Cost = 0  Port = 0x8000

Frame 4 (52 bytes on wire, 52 bytes captured)
IEEE 802.3 Ethernet
Logical-Link Control
Spanning Tree Protocol

No.     Time        Source                Destination           Protocol Info
      5 5.503809    10.69.69.49           10.69.69.51           TCP      [TCP segment of a reassembled PDU]

Frame 5 (1390 bytes on wire, 1390 bytes captured)
Ethernet II, Src: 02:ff:b4:9b:b3:e5 (02:ff:b4:9b:b3:e5), Dst: 00:ff:02:2d:ce:4f (00:ff:02:2d:ce:4f)
Internet Protocol, Src: 10.69.69.49 (10.69.69.49), Dst: 10.69.69.51 (10.69.69.51)
Transmission Control Protocol, Src Port: microsoft-ds (445), Dst Port: 3119 (3119), Seq: 0, Ack: 0, Len: 1336

No.     Time        Source                Destination           Protocol Info
      6 5.683029    10.69.69.51           10.69.69.49           TCP      3119 > microsoft-ds [ACK] Seq=0 Ack=1336 Win=17368 Len=0 SLE=4008 SRE=4160

Frame 6 (66 bytes on wire, 66 bytes captured)
Ethernet II, Src: 00:ff:02:2d:ce:4f (00:ff:02:2d:ce:4f), Dst: 02:ff:b4:9b:b3:e5 (02:ff:b4:9b:b3:e5)
Internet Protocol, Src: 10.69.69.51 (10.69.69.51), Dst: 10.69.69.49 (10.69.69.49)
Transmission Control Protocol, Src Port: 3119 (3119), Dst Port: microsoft-ds (445), Seq: 0, Ack: 1336, Len: 0

No.     Time        Source                Destination           Protocol Info
      7 5.738669    10.69.69.49           10.69.69.51           TCP      [TCP segment of a reassembled PDU]

Frame 7 (1390 bytes on wire, 1390 bytes captured)
Ethernet II, Src: 02:ff:b4:9b:b3:e5 (02:ff:b4:9b:b3:e5), Dst: 00:ff:02:2d:ce:4f (00:ff:02:2d:ce:4f)
Internet Protocol, Src: 10.69.69.49 (10.69.69.49), Dst: 10.69.69.51 (10.69.69.51)
Transmission Control Protocol, Src Port: microsoft-ds (445), Dst Port: 3119 (3119), Seq: 1336, Ack: 0, Len: 1336

No.     Time        Source                Destination           Protocol Info
      8 5.884234    10.69.69.51           10.69.69.49           TCP      3119 > microsoft-ds [ACK] Seq=0 Ack=2672 Win=17368 Len=0 SLE=4008 SRE=4160

Frame 8 (66 bytes on wire, 66 bytes captured)
Ethernet II, Src: 00:ff:02:2d:ce:4f (00:ff:02:2d:ce:4f), Dst: 02:ff:b4:9b:b3:e5 (02:ff:b4:9b:b3:e5)
Internet Protocol, Src: 10.69.69.51 (10.69.69.51), Dst: 10.69.69.49 (10.69.69.49)
Transmission Control Protocol, Src Port: 3119 (3119), Dst Port: microsoft-ds (445), Seq: 0, Ack: 2672, Len: 0

No.     Time        Source                Destination           Protocol Info
      9 5.926810    10.69.69.49           10.69.69.51           TCP      [TCP Previous segment lost] [TCP segment of a reassembled PDU]

Frame 9 (206 bytes on wire, 206 bytes captured)
Ethernet II, Src: 02:ff:b4:9b:b3:e5 (02:ff:b4:9b:b3:e5), Dst: 00:ff:02:2d:ce:4f (00:ff:02:2d:ce:4f)
Internet Protocol, Src: 10.69.69.49 (10.69.69.49), Dst: 10.69.69.51 (10.69.69.51)
Transmission Control Protocol, Src Port: microsoft-ds (445), Dst Port: 3119 (3119), Seq: 4008, Ack: 0, Len: 152

No.     Time        Source                Destination           Protocol Info
     10 5.926844    10.69.69.51           10.69.69.49           TCP      [TCP Dup ACK 8#1] 3119 > microsoft-ds [ACK] Seq=0 Ack=2672 Win=17368 Len=0 SLE=4008 SRE=4160

Frame 10 (66 bytes on wire, 66 bytes captured)
Ethernet II, Src: 00:ff:02:2d:ce:4f (00:ff:02:2d:ce:4f), Dst: 02:ff:b4:9b:b3:e5 (02:ff:b4:9b:b3:e5)
Internet Protocol, Src: 10.69.69.51 (10.69.69.51), Dst: 10.69.69.49 (10.69.69.49)
Transmission Control Protocol, Src Port: 3119 (3119), Dst Port: microsoft-ds (445), Seq: 0, Ack: 2672, Len: 0

No.     Time        Source                Destination           Protocol Info
     11 5.999866    00:ff:b4:9b:b3:e5     Spanning-tree-(for-bridges)_00 STP      Conf. Root = 32768/02:ff:b4:9b:b3:e5  Cost = 0  Port = 0x8000

Frame 11 (52 bytes on wire, 52 bytes captured)
IEEE 802.3 Ethernet
Logical-Link Control
Spanning Tree Protocol

No.     Time        Source                Destination           Protocol Info
     12 7.999410    00:ff:b4:9b:b3:e5     Spanning-tree-(for-bridges)_00 STP      Conf. Root = 32768/02:ff:b4:9b:b3:e5  Cost = 0  Port = 0x8000

Frame 12 (52 bytes on wire, 52 bytes captured)
IEEE 802.3 Ethernet
Logical-Link Control
Spanning Tree Protocol

No.     Time        Source                Destination           Protocol Info
     13 9.999523    00:ff:b4:9b:b3:e5     Spanning-tree-(for-bridges)_00 STP      Conf. Root = 32768/02:ff:b4:9b:b3:e5  Cost = 0  Port = 0x8000

Frame 13 (52 bytes on wire, 52 bytes captured)
IEEE 802.3 Ethernet
Logical-Link Control
Spanning Tree Protocol

No.     Time        Source                Destination           Protocol Info
     14 11.999763   00:ff:b4:9b:b3:e5     Spanning-tree-(for-bridges)_00 STP      Conf. Root = 32768/02:ff:b4:9b:b3:e5  Cost = 0  Port = 0x8000

Frame 14 (52 bytes on wire, 52 bytes captured)
IEEE 802.3 Ethernet
Logical-Link Control
Spanning Tree Protocol

No.     Time        Source                Destination           Protocol Info
     15 13.999322   00:ff:b4:9b:b3:e5     Spanning-tree-(for-bridges)_00 STP      Conf. Root = 32768/02:ff:b4:9b:b3:e5  Cost = 0  Port = 0x8000

Frame 15 (52 bytes on wire, 52 bytes captured)
IEEE 802.3 Ethernet
Logical-Link Control
Spanning Tree Protocol

No.     Time        Source                Destination           Protocol Info
     16 15.999500   00:ff:b4:9b:b3:e5     Spanning-tree-(for-bridges)_00 STP      Conf. Root = 32768/02:ff:b4:9b:b3:e5  Cost = 0  Port = 0x8000

Frame 16 (52 bytes on wire, 52 bytes captured)
IEEE 802.3 Ethernet
Logical-Link Control
Spanning Tree Protocol

No.     Time        Source                Destination           Protocol Info
     17 17.998949   00:ff:b4:9b:b3:e5     Spanning-tree-(for-bridges)_00 STP      Conf. Root = 32768/02:ff:b4:9b:b3:e5  Cost = 0  Port = 0x8000

Frame 17 (52 bytes on wire, 52 bytes captured)
IEEE 802.3 Ethernet
Logical-Link Control
Spanning Tree Protocol

No.     Time        Source                Destination           Protocol Info
     18 19.999737   00:ff:b4:9b:b3:e5     Spanning-tree-(for-bridges)_00 STP      Conf. Root = 32768/02:ff:b4:9b:b3:e5  Cost = 0  Port = 0x8000

Frame 18 (52 bytes on wire, 52 bytes captured)
IEEE 802.3 Ethernet
Logical-Link Control
Spanning Tree Protocol

No.     Time        Source                Destination           Protocol Info
     19 21.999241   00:ff:b4:9b:b3:e5     Spanning-tree-(for-bridges)_00 STP      Conf. Root = 32768/02:ff:b4:9b:b3:e5  Cost = 0  Port = 0x8000

Frame 19 (52 bytes on wire, 52 bytes captured)
IEEE 802.3 Ethernet
Logical-Link Control
Spanning Tree Protocol

No.     Time        Source                Destination           Protocol Info
     20 23.999534   00:ff:b4:9b:b3:e5     Spanning-tree-(for-bridges)_00 STP      Conf. Root = 32768/02:ff:b4:9b:b3:e5  Cost = 0  Port = 0x8000

Frame 20 (52 bytes on wire, 52 bytes captured)
IEEE 802.3 Ethernet
Logical-Link Control
Spanning Tree Protocol
0
Comment
Question by:sypder
  • 3
4 Comments
 
LVL 5

Accepted Solution

by:
drawlin earned 500 total points
ID: 17920025
We probably need more information about the network setup.  Type of VPN devices, Internet connection on both ends(T1, DSL, cable) and is this a new problem, in that it worked just fine in the past but today it is crawling.  Looking at your packet cap, 75% of the entries was Spanning Tree, which indicates your switch is spending 75% of it's time looking for the best route to send data.  However, it could be that you had just plugged a device into your switch when you started your capture and it was learning.  I would give it a couple minutes after plugging anything into the switch, then start the capture, then start the VPN and transfer a couple files, then stop your capture.  If STP is still accounting for 75%  of your traffic, you could have a layer 2 problem.
0
 
LVL 3

Author Comment

by:sypder
ID: 17922525
We are using Windows computers running OpenVPN. The server end is the premium DSL, the client end varies, but currently is DSL. The problem is not new, but intermittent. A good example is the Windows Remote Desktop. This usually worked fine over the VPN, but a few days ago stopped. I now have to access the remote desktop directly (i.e., global IP rather than local IP). No new computers were added to the network when I took that snap shot. In general, I do see a lot of spanning trees. I will try transferring some files and then doing a capture.

I will perform more tests and post more information. Thank you.
0
 
LVL 3

Author Comment

by:sypder
ID: 17935490
I think he whole spanning tree problem is gone. My problem now seems to (perhaps) be Dreamweaver related. When I open up a very small CSS file. It send over 800 packets. Most are like:

Frame 732 (216 bytes on wire, 216 bytes captured)
Ethernet II, Src: 00:ff:02:2d:ce:4f (00:ff:02:2d:ce:4f), Dst: 02:ff:b4:9b:b3:e5 (02:ff:b4:9b:b3:e5)
Internet Protocol, Src: 10.69.69.54 (10.69.69.54), Dst: 10.69.69.49 (10.69.69.49)
Transmission Control Protocol, Src Port: 4147 (4147), Dst Port: microsoft-ds (445), Seq: 41638, Ack: 85706, Len: 162
NetBIOS Session Service
SMB (Server Message Block Protocol)

No.     Time        Source                Destination           Protocol Info
    733 27.899895   10.69.69.49           10.69.69.54           SMB      NT Create AndX Response, FID: 0x800e

Frame 733 (193 bytes on wire, 193 bytes captured)
Ethernet II, Src: 02:ff:b4:9b:b3:e5 (02:ff:b4:9b:b3:e5), Dst: 00:ff:02:2d:ce:4f (00:ff:02:2d:ce:4f)
Internet Protocol, Src: 10.69.69.49 (10.69.69.49), Dst: 10.69.69.54 (10.69.69.54)
Transmission Control Protocol, Src Port: microsoft-ds (445), Dst Port: 4147 (4147), Seq: 85706, Ack: 41800, Len: 139
NetBIOS Session Service
SMB (Server Message Block Protocol)

No.     Time        Source                Destination           Protocol Info
    734 27.900311   10.69.69.54           10.69.69.49           SMB      Close Request, FID: 0x800e

Frame 734 (99 bytes on wire, 99 bytes captured)
Ethernet II, Src: 00:ff:02:2d:ce:4f (00:ff:02:2d:ce:4f), Dst: 02:ff:b4:9b:b3:e5 (02:ff:b4:9b:b3:e5)
Internet Protocol, Src: 10.69.69.54 (10.69.69.54), Dst: 10.69.69.49 (10.69.69.49)
Transmission Control Protocol, Src Port: 4147 (4147), Dst Port: microsoft-ds (445), Seq: 41800, Ack: 85845, Len: 45
NetBIOS Session Service
SMB (Server Message Block Protocol)

No.     Time        Source                Destination           Protocol Info
    735 27.939701   10.69.69.49           10.69.69.54           SMB      Close Response

Frame 735 (93 bytes on wire, 93 bytes captured)
Ethernet II, Src: 02:ff:b4:9b:b3:e5 (02:ff:b4:9b:b3:e5), Dst: 00:ff:02:2d:ce:4f (00:ff:02:2d:ce:4f)
Internet Protocol, Src: 10.69.69.49 (10.69.69.49), Dst: 10.69.69.54 (10.69.69.54)
Transmission Control Protocol, Src Port: microsoft-ds (445), Dst Port: 4147 (4147), Seq: 85845, Ack: 41845, Len: 39
NetBIOS Session Service
SMB (Server Message Block Protocol)

No.     Time        Source                Destination           Protocol Info
    736 27.939991   10.69.69.54           10.69.69.49           SMB      Trans2 Request, QUERY_PATH_INFO, Query File Basic Info, Path: \Sites\TNB\includes\css\Backend.css

Frame 736 (204 bytes on wire, 204 bytes captured)
Ethernet II, Src: 00:ff:02:2d:ce:4f (00:ff:02:2d:ce:4f), Dst: 02:ff:b4:9b:b3:e5 (02:ff:b4:9b:b3:e5)
Internet Protocol, Src: 10.69.69.54 (10.69.69.54), Dst: 10.69.69.49 (10.69.69.49)
Transmission Control Protocol, Src Port: 4147 (4147), Dst Port: microsoft-ds (445), Seq: 41845, Ack: 85884, Len: 150
NetBIOS Session Service
SMB (Server Message Block Protocol)

No.     Time        Source                Destination           Protocol Info
    737 27.983132   10.69.69.49           10.69.69.54           SMB      Trans2 Response, QUERY_PATH_INFO

Frame 737 (158 bytes on wire, 158 bytes captured)
Ethernet II, Src: 02:ff:b4:9b:b3:e5 (02:ff:b4:9b:b3:e5), Dst: 00:ff:02:2d:ce:4f (00:ff:02:2d:ce:4f)
Internet Protocol, Src: 10.69.69.49 (10.69.69.49), Dst: 10.69.69.54 (10.69.69.54)
Transmission Control Protocol, Src Port: microsoft-ds (445), Dst Port: 4147 (4147), Seq: 85884, Ack: 41995, Len: 104
NetBIOS Session Service
SMB (Server Message Block Protocol)

No.     Time        Source                Destination           Protocol Info
    738 27.998747   00:ff:b4:9b:b3:e5     Spanning-tree-(for-bridges)_00 STP      Conf. Root = 32768/02:ff:b4:9b:b3:e5  Cost = 0  Port = 0x8000

Frame 738 (52 bytes on wire, 52 bytes captured)
IEEE 802.3 Ethernet
Logical-Link Control
Spanning Tree Protocol

No.     Time        Source                Destination           Protocol Info
    739 28.003549   10.69.69.54           10.69.69.49           SMB      Trans2 Request, FIND_FIRST2, Pattern: \Sites\TNB\includes\css\Backend.css

Frame 739 (210 bytes on wire, 210 bytes captured)
Ethernet II, Src: 00:ff:02:2d:ce:4f (00:ff:02:2d:ce:4f), Dst: 02:ff:b4:9b:b3:e5 (02:ff:b4:9b:b3:e5)
Internet Protocol, Src: 10.69.69.54 (10.69.69.54), Dst: 10.69.69.49 (10.69.69.49)
Transmission Control Protocol, Src Port: 4147 (4147), Dst Port: microsoft-ds (445), Seq: 41995, Ack: 85988, Len: 156
NetBIOS Session Service
SMB (Server Message Block Protocol)

No.     Time        Source                Destination           Protocol Info
    740 28.048113   10.69.69.49           10.69.69.54           SMB      Trans2 Response, FIND_FIRST2, Files: Backend.css

Frame 740 (246 bytes on wire, 246 bytes captured)
Ethernet II, Src: 02:ff:b4:9b:b3:e5 (02:ff:b4:9b:b3:e5), Dst: 00:ff:02:2d:ce:4f (00:ff:02:2d:ce:4f)
Internet Protocol, Src: 10.69.69.49 (10.69.69.49), Dst: 10.69.69.54 (10.69.69.54)
Transmission Control Protocol, Src Port: microsoft-ds (445), Dst Port: 4147 (4147), Seq: 85988, Ack: 42151, Len: 192
NetBIOS Session Service
SMB (Server Message Block Protocol)

No.     Time        Source                Destination           Protocol Info
    741 28.054702   10.69.69.54           10.69.69.49           SMB      NT Create AndX Request, Path: \Sites\TNB

Frame 741 (164 bytes on wire, 164 bytes captured)
Ethernet II, Src: 00:ff:02:2d:ce:4f (00:ff:02:2d:ce:4f), Dst: 02:ff:b4:9b:b3:e5 (02:ff:b4:9b:b3:e5)
Internet Protocol, Src: 10.69.69.54 (10.69.69.54), Dst: 10.69.69.49 (10.69.69.49)
Transmission Control Protocol, Src Port: 4147 (4147), Dst Port: microsoft-ds (445), Seq: 42151, Ack: 86180, Len: 110
NetBIOS Session Service
SMB (Server Message Block Protocol)

No.     Time        Source                Destination           Protocol Info
    742 28.097034   10.69.69.49           10.69.69.54           SMB      NT Create AndX Response, FID: 0xc00a

Frame 742 (193 bytes on wire, 193 bytes captured)
Ethernet II, Src: 02:ff:b4:9b:b3:e5 (02:ff:b4:9b:b3:e5), Dst: 00:ff:02:2d:ce:4f (00:ff:02:2d:ce:4f)
Internet Protocol, Src: 10.69.69.49 (10.69.69.49), Dst: 10.69.69.54 (10.69.69.54)
Transmission Control Protocol, Src Port: microsoft-ds (445), Dst Port: 4147 (4147), Seq: 86180, Ack: 42261, Len: 139
NetBIOS Session Service
SMB (Server Message Block Protocol)

No.     Time        Source                Destination           Protocol Info
    743 28.097247   10.69.69.54           10.69.69.49           SMB      Close Request, FID: 0xc00a

Frame 743 (99 bytes on wire, 99 bytes captured)
Ethernet II, Src: 00:ff:02:2d:ce:4f (00:ff:02:2d:ce:4f), Dst: 02:ff:b4:9b:b3:e5 (02:ff:b4:9b:b3:e5)
Internet Protocol, Src: 10.69.69.54 (10.69.69.54), Dst: 10.69.69.49 (10.69.69.49)
Transmission Control Protocol, Src Port: 4147 (4147), Dst Port: microsoft-ds (445), Seq: 42261, Ack: 86319, Len: 45
NetBIOS Session Service
SMB (Server Message Block Protocol)

No.     Time        Source                Destination           Protocol Info
    744 28.137779   10.69.69.49           10.69.69.54           SMB      Close Response

Frame 744 (93 bytes on wire, 93 bytes captured)
Ethernet II, Src: 02:ff:b4:9b:b3:e5 (02:ff:b4:9b:b3:e5), Dst: 00:ff:02:2d:ce:4f (00:ff:02:2d:ce:4f)
Internet Protocol, Src: 10.69.69.49 (10.69.69.49), Dst: 10.69.69.54 (10.69.69.54)
Transmission Control Protocol, Src Port: microsoft-ds (445), Dst Port: 4147 (4147), Seq: 86319, Ack: 42306, Len: 39
NetBIOS Session Service
SMB (Server Message Block Protocol)

Chris
0
 
LVL 3

Author Comment

by:sypder
ID: 17961821
I found out that Dreamweaver is just not very good on a VPN. I am switching over to PHPeclipse.

Thanks.
0

Featured Post

Control application downtime with dependency maps

Visualize the interdependencies between application components better with Applications Manager's automated application discovery and dependency mapping feature. Resolve performance issues faster by quickly isolating problematic components.

Join & Write a Comment

Suggested Solutions

Title # Comments Views Activity
Cisco Layer 2 Switches 6 50
need help finding NIC driver for Dell optiplex 380 2 27
Nic to NIC 5 44
Linux as a middle box 7 18
#Citrix #Citrix Netscaler #HTTP Compression #Load Balance
Configuring network clients can be a chore, especially if there are a large number of them or a lot of itinerant users.  DHCP dynamically manages this process, much to the relief of users and administrators alike!
Here's a very brief overview of the methods PRTG Network Monitor (https://www.paessler.com/prtg) offers for monitoring bandwidth, to help you decide which methods you´d like to investigate in more detail.  The methods are covered in more detail in o…
This video gives you a great overview about bandwidth monitoring with SNMP and WMI with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're looking for how to monitor bandwidth using netflow or packet s…

708 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

13 Experts available now in Live!

Get 1:1 Help Now