Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

SBS2k3 TCP ACK Delay?


  • Please log in to reply
3 replies to this topic

#1 mysticryuujin

mysticryuujin

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:09:40 PM

Posted 08 March 2005 - 03:01 PM

Hello,
We are trying to install older accounting software onto SBS2003 Prem. The software works fine under Windows 2000 and it WORKS under SBS2003.

However the problem is, the time it takes for data to be transferred to one computer from the server is exceptionally long. I've tried all the Tcp registry tweaks (maybe I did them wrong, I don't know anymore heh) but nothing is working. When I do a sniff of the network I notice that there is a small delay and then 15 second gap of data flow after a TCP ACK from the server. I'll put links at the bottom for reference with the sniff of the 2000 and SBS 2003 network. It takes roughly 3 seconds for the 2000 server/client to log in, but it takes about 16 for the 2003.

The software we are trying to use, Smart Shop Manager, is no longer supported and it uses Interbase 5.6, that is no longer supported either. One thing I noticed is that if File and Print Sharing is on, the 2003 server/client communicate with the SMB protocol, but if its not they communicate with the IB protocol, either way the same thing happens so I don't THINK that it is a software/Interbase problem, but I wouldn't rule it out. The 2000 server communicates with the IB protocol.

Any hints, help, or even some motivation would help, I've already put a week
into this.

Thank You,
Chase Wright

the 2000 sniff is here:
http://www.wrightprec.com/s2k%20show

the SBS2k3 sniff is here:
http://www.wrightprec.com/s2k3%20show

BC AdBot (Login to Remove)

 


#2 Grinler

Grinler

    Lawrence Abrams


  • Admin
  • 43,504 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:USA
  • Local time:10:40 PM

Posted 09 March 2005 - 11:51 PM

I see that gap..interesting.

Is this only happening on one computer? Could it be a duplex mismatch issue? Force all the switches/ports on the switches and the computers to the same duplex setting. COuld be a conflict.

Also swap out the cable going to the server

#3 QQQQ

QQQQ

  • Members
  • 377 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:09:40 PM

Posted 10 March 2005 - 09:08 AM

Possibly a DNS issue? Is the SBS 2003 server ip the first one in the DNS for the workstation? If not and you can't make it the first, try adding a entry in the host file. (192.168.1.1 server1)

#4 Grinler

Grinler

    Lawrence Abrams


  • Admin
  • 43,504 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:USA
  • Local time:10:40 PM

Posted 10 March 2005 - 04:05 PM

Good point. Also add it to the lmhosts file as well. Do you have a WINS server set up on the SBS and is the workstations set to use it?




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users