VMware Communities: TCP sequence number too high, a transport-level error has occured

Up to Discussions in Virtual Machine & Guest OS

This Question is Possibly Answered

1 "correct" answer available (10 pts) 2 "helpful" answers available (6 pts)

3 Replies Last post: Jul 3, 2009 5:29 AM by Texiwill

TCP sequence number too high, a transport-level error has occured when sending the request to the server

Jul 1, 2009 11:19 PM

jrsweden 2 posts since
Apr 25, 2009

I have a network related problem, communication issue between two VM in a ESX 3.5 environment. My firewall is telling us that "tcp sequence number too high" and drop packets.

Background: One W2003 Standard IIS VM with .Net applikation communicating with one W2003 Enterprise SQLServer 2005. VM sitting on each VLAN. VM communicating through firewall and switches.

Suddenly firewall reports "tcp sequence number too high" and communication is lost. Event viewer in W2003 IIS reports "A transport-level error has occured when sending the request to the server".

Is there any known issues about tcp handling in virtual switches, nic's or other network related environment? Is there any white-papers regarding configuration scenarios?

Thanks
Jörgen Rönning, Gotit Sweden
jorgen.ronning@gotit.se

Tags: 3.5, nic, vswitch, tcp, tcp, ip, firewall, network, sequence

Reply Re: TCP sequence number too high, a transport-level error has occured when sending the request to the server Jul 2, 2009 9:08 AM

Texiwill 10,056 posts since
Jan 13, 2004 Moderator

Hello,

Moved to the Virtual Machine and Guest OS forum.

There was a similar issue when using vmxnet with multiple vCPUs on RHEL. Are you using multiple vCPUs and the vmxnet driver? If so then try using the e1000 or pcnet32 network drivers.

Best regards,
Edward L. Haletky VMware Communities User Moderator, VMware vExpert 2009, Virtualization Practice Analyst
Now Available: 'VMware vSphere(TM) and Virtual Infrastructure Security: Securing the Virtual Environment'
Also available 'VMWare ESX Server in the Enterprise'
SearchVMware Pro|Blue Gears|Top Virtualization Security Links|Virtualization Security Round Table Podcast

Reply Re: TCP sequence number too high, a transport-level error has occured when sending the request to the server Jul 3, 2009 1:18 AM

in response to: Texiwill

jrsweden 2 posts since
Apr 25, 2009

Thankyou for your reply.

VM IIS W2003 are using 2 vCPU and a Flexible NIC. VMware TOOLS is running. In control panel/add remove hardware we can read VMware Accelerated AMD PCNet Adapter.
VM SQL 2005 are using 4 vCPU and a Enhanced vmxnet NIC. VMware TOOLS is running. In control panel/add remove hardware we can read VMware PCI Ethernet Adapter #3.
ESX 3.5 patch 4 installation uses the "console".

The flexible driver can work as a vmxnet NIC (http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1001805). With VMware TOOLS it should be a vmxnet NIC driver.

Are we using multiple vCPUs? YES.
Are we using RHEL? YES.
Are we using vmxnet driver? YES.

How can we change the behavior of the flexible driver to use any other network driver than vmxnet?
If this is right - then we have several VM using wrong network driver.

Thanks
Jörgen Rönning, Gotit Sweden
jorgen.ronning@gotit.se

Reply Re: TCP sequence number too high, a transport-level error has occured when sending the request to the server Jul 3, 2009 5:29 AM

in response to: jrsweden

Texiwill 10,056 posts since
Jan 13, 2004 Moderator

Hello,

This is the driver provided by VMware, it is the vmxnet driver. Just remove it and go back to the default pcnet32 driver. Flexible implies that you can either use the vmxnet or pcnet32. Until you install VMware Tools, pcnet32 is in use. Just change the driver for the vNIC.

Are we using multiple vCPUs? YES.
Are we using RHEL? YES

Where? BOTH VMs are Windows.... This is not an ESX Management Appliance issue.
.

Are we using vmxnet driver? YES.

Another option is to go to one vCPU and see if that corrects the problem.

In either case I would open a case with VMware Support to get better assistance, they will ask you to go back to pcnet32 or use the e1000 driver as well. e1000 takes more to change out on VI 3.x than it does in vSphere but it is one solution as well. e1000 like pcnet32 is a native windows driver.

Best regards,
Edward L. Haletky VMware Communities User Moderator, VMware vExpert 2009, Virtualization Practice Analyst
Now Available: 'VMware vSphere(TM) and Virtual Infrastructure Security: Securing the Virtual Environment'
Also available 'VMWare ESX Server in the Enterprise'
SearchVMware Pro|Blue Gears|Top Virtualization Security Links|Virtualization Security Round Table Podcast

Actions

View as PDF

Up to Discussions in Virtual Machine & Guest OS