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

Maybe this will help =========================================== New registry entry for controlling the TCP Acknowledgment (ACK) behavior in Windows XP and in Windows Server 2003 http://support.microsoft.com/kb/328890

I've already tried that, 100 differant ways...I cant figure it out, no matter what I set that to it does the exact same thing

It look like a Ident or DNS issue. After ident timeout (15 sec), the server continue with the connection process. Danny Larouche, cwna ciw

Could you explain a little deeper? I'm not exactly an expert on any of this stuff :) I'm not even sure what Ident is....

Well there's no way that it is a DNS issue, I just set up the machines to use the same DNS as the 2000's do, and I even had the 03 client log into the 2000's database and it was perfect. Still don't know about Ident or what that does? I do wonder though if I need the hotfix described here: http://support.microsoft.com/kb/815230 Anyone?

Negative, that hotfix did not work