Application Issues with W2K3 SP1 - Networking Timeout??

Hi,

We have a Radiology PACS viewer app that runs just great with W2K3, but not
with SP1 installed. I have scoured the internet for some answers, and the
only two problems I have seen after SP1 is installed is problems with DCOM
applications, and then TCPIP timeout.

I have gone through and checked for the DCOM problem, but I am pretty sure
it is not that. I am now suspecting network timeout issues. The appliction
talks HTTP to 1 of 2 IIS web servers through a Summit 5i load balance
switch. These web servers talk to 1 of 5 database servers that send back
xrays/CT's back to the viewer. If I run this client on a non-SP1 server,
the app runs just fine, but as soon as SP1 is installed the requests seem to
timeout. The request goes out, but nothing makes it way back.

I have tried different network cards, and tried setting the MTU to 1500, but
nothing works.

The vendor does not really want to help us at all. When they found out we
were trying to get it running on a non-supported platform, they did not
really have any interest in solving the problem.

Does anyone have any ideas what needs to be looked at and where to look at?

Thanks,

Sean

You'll have to sniff each segment and see if you can find where the problem
is at. You could also follow the vendors suggestion and uninstall SP1.


"Sean P. Donaghey" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> Hi,
>
> We have a Radiology PACS viewer app that runs just great with W2K3, but
not
> with SP1 installed. I have scoured the internet for some answers, and the
> only two problems I have seen after SP1 is installed is problems with DCOM
> applications, and then TCPIP timeout.
>
> I have gone through and checked for the DCOM problem, but I am pretty sure
> it is not that. I am now suspecting network timeout issues. The
appliction
> talks HTTP to 1 of 2 IIS web servers through a Summit 5i load balance
> switch. These web servers talk to 1 of 5 database servers that send back
> xrays/CT's back to the viewer. If I run this client on a non-SP1 server,
> the app runs just fine, but as soon as SP1 is installed the requests seem
to
> timeout. The request goes out, but nothing makes it way back.
>
> I have tried different network cards, and tried setting the MTU to 1500,
but
> nothing works.
>
> The vendor does not really want to help us at all. When they found out we
> were trying to get it running on a non-supported platform, they did not
> really have any interest in solving the problem.
>
> Does anyone have any ideas what needs to be looked at and where to look
at?
>
> Thanks,
>
> Sean
>
>

The vendor never suggested removing SP1. I was the one that foud out the
problem. They don't support Server 2003.

"Neteng" <(E-Mail Removed)> wrote in message
news:%23n$(E-Mail Removed)...
> You'll have to sniff each segment and see if you can find where the
> problem
> is at. You could also follow the vendors suggestion and uninstall SP1.
>
>
> "Sean P. Donaghey" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
>> Hi,
>>
>> We have a Radiology PACS viewer app that runs just great with W2K3, but
> not
>> with SP1 installed. I have scoured the internet for some answers, and
>> the
>> only two problems I have seen after SP1 is installed is problems with
>> DCOM
>> applications, and then TCPIP timeout.
>>
>> I have gone through and checked for the DCOM problem, but I am pretty
>> sure
>> it is not that. I am now suspecting network timeout issues. The
> appliction
>> talks HTTP to 1 of 2 IIS web servers through a Summit 5i load balance
>> switch. These web servers talk to 1 of 5 database servers that send back
>> xrays/CT's back to the viewer. If I run this client on a non-SP1 server,
>> the app runs just fine, but as soon as SP1 is installed the requests seem
> to
>> timeout. The request goes out, but nothing makes it way back.
>>
>> I have tried different network cards, and tried setting the MTU to 1500,
> but
>> nothing works.
>>
>> The vendor does not really want to help us at all. When they found out
>> we
>> were trying to get it running on a non-supported platform, they did not
>> really have any interest in solving the problem.
>>
>> Does anyone have any ideas what needs to be looked at and where to look
> at?
>>
>> Thanks,
>>
>> Sean
>>
>>
>
>

Then get off of Server 2003, there is a reason they don't support it!

"Sean P. Donaghey" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> The vendor never suggested removing SP1. I was the one that foud out the
> problem. They don't support Server 2003.
>
> "Neteng" <(E-Mail Removed)> wrote in message
> news:%23n$(E-Mail Removed)...
> > You'll have to sniff each segment and see if you can find where the
> > problem
> > is at. You could also follow the vendors suggestion and uninstall SP1.
> >
> >
> > "Sean P. Donaghey" <(E-Mail Removed)> wrote in message
> > news:%(E-Mail Removed)...
> >> Hi,
> >>
> >> We have a Radiology PACS viewer app that runs just great with W2K3, but
> > not
> >> with SP1 installed. I have scoured the internet for some answers, and
> >> the
> >> only two problems I have seen after SP1 is installed is problems with
> >> DCOM
> >> applications, and then TCPIP timeout.
> >>
> >> I have gone through and checked for the DCOM problem, but I am pretty
> >> sure
> >> it is not that. I am now suspecting network timeout issues. The
> > appliction
> >> talks HTTP to 1 of 2 IIS web servers through a Summit 5i load balance
> >> switch. These web servers talk to 1 of 5 database servers that send
back
> >> xrays/CT's back to the viewer. If I run this client on a non-SP1
server,
> >> the app runs just fine, but as soon as SP1 is installed the requests
seem
> > to
> >> timeout. The request goes out, but nothing makes it way back.
> >>
> >> I have tried different network cards, and tried setting the MTU to
1500,
> > but
> >> nothing works.
> >>
> >> The vendor does not really want to help us at all. When they found out
> >> we
> >> were trying to get it running on a non-supported platform, they did not
> >> really have any interest in solving the problem.
> >>
> >> Does anyone have any ideas what needs to be looked at and where to look
> > at?
> >>
> >> Thanks,
> >>
> >> Sean
> >>
> >>
> >
> >
>
>