Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

We are experiencing a problem after moving some software from one server to another. the client has remained on the same machine.

Old Server: Windows 2003 server Physical machine

New Server: Windows Server 2008 R2 Virtual (Under HyperV)

On the old server the client connected ok but on the new server the client gets the following socket errors 10054 and 10060.

if the client runs on the same VLAN we get comms ok. this lead us to think it was the firewall that was blocking the communications but we could open a session in telnet to the port on the server and the rules in the firewall are set to apply to both servers.

To get to the bottom of this we did a comparison of the wireshrak traces on both the old and new server using the same client and here they are.

Old Server Working!

1   0.000000    10.103.1.15 172.10.8.139    TCP 52415 > 914c/g [SYN] Seq=0 Win=8192 Len=0 MSS=1300 WS=8 SACK_PERM=1
2   0.000339    172.10.8.139    10.103.1.15 TCP 914c/g > 52415 [SYN, ACK] Seq=0 Ack=1 Win=16384 Len=0 MSS=1460 WS=0 SACK_PERM=1
3   0.018033    10.103.1.15 172.10.8.139    TCP 52415 > 914c/g [ACK] Seq=1 Ack=1 Win=1280 Len=0
4   0.019551    10.103.1.15 172.10.8.139    TCP 52415 > 914c/g [PSH, ACK] Seq=1 Ack=1 Win=2816 Len=92
5   0.060038    172.10.8.139    10.103.1.15 TCP 914c/g > 52415 [PSH, ACK] Seq=1 Ack=93 Win=65443 Len=16
......DATA........
17  0.473170    10.103.1.15 172.10.8.139    TCP 52415 > 914c/g [PSH, ACK] Seq=1069 Ack=1256 Win=11264 Len=16
18  0.474000    10.103.1.15 172.10.8.139    TCP 52415 > 914c/g [FIN, ACK] Seq=1085 Ack=1256 Win=65024 Len=0
19  0.474073    172.10.8.139    10.103.1.15 TCP 914c/g > 52415 [ACK] Seq=1256 Ack=1086 Win=64451 Len=0
22  0.480231    172.10.8.139    10.103.1.15 TCP 914c/g > 52415 [FIN, ACK] Seq=1256 Ack=1086 Win=64451 Len=0
25  0.498708    10.103.1.15 172.10.8.139    TCP 52415 > 914c/g [ACK] Seq=1086 Ack=1257 Win=65024 Len=0

NEW Server NOT Working!

1   0.000000    10.103.1.15 10.100.10.32    TCP 52350 > 914c/g [SYN] Seq=0 Win=8192 Len=0 MSS=1300 WS=8 SACK_PERM=1
2   0.000052    10.100.10.32    10.103.1.15 TCP 914c/g > 52350 [SYN, ACK] Seq=0 Ack=1 Win=8192 Len=0 MSS=1460 WS=8 SACK_PERM=1
3   0.137702    10.103.1.15 10.100.10.32    TCP 52350 > 914c/g [ACK] Seq=1 Ack=1 Win=1280 Len=0
4   0.138323    10.103.1.15 10.100.10.32    TCP 52350 > 914c/g [ACK] Seq=1 Ack=1 Win=2816 Len=5
5   0.139280    10.100.10.32    10.103.1.15 TCP 914c/g > 52350 [FIN, ACK] Seq=1 Ack=6 Win=131072 Len=0
6   0.286775    10.103.1.15 10.100.10.32    TCP 52350 > 914c/g [PSH, ACK] Seq=6 Ack=2 Win=2816 Len=87
7   0.286797    10.100.10.32    10.103.1.15 TCP 914c/g > 52350 [RST, ACK] Seq=2 Ack=93 Win=0 Len=0
8   0.286810    10.103.1.15 10.100.10.32    TCP 52350 > 914c/g [FIN, ACK] Seq=93 Ack=2 Win=66048 Len=0
9   0.286816    10.100.10.32    10.103.1.15 TCP 914c/g > 52350 [RST] Seq=2 Win=0 Len=0

Can anyone shed any light on what is going on this has me scratching my head and kicking the servers.......

Thanks

share|improve this question
    
if it is windows, kicking is always appropriate! –  Mike Pennington May 5 '11 at 10:56
    
Windows is easy to kick but to kick linux you have to be a super user ;) –  MikeT May 5 '11 at 17:02
    
your point is? I can't do anything meaningful on Windows7 without Administrator rights –  Mike Pennington May 5 '11 at 17:11
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.