Windows 2000 IIS Strange Issue

If this is not the correct newsgroup to post this question please let me know where to post.

I have a very strange issue that just came up with a client. My server is located in the Eastern US and the client is in the UK. Suddenly when they post to our server on port 80 nothing is received. We can watch the logs and other traffic is working fine as well the data received to the web page. Our network group proved the traffic does reach the server but then it just seems to disappear.

The receiving application is ASP.NET and works fine with many other clients. Does anyone know how to get IIS to tell me where the issue might be? I have everything possible turned on in IIS logging and it shows nothing. It's like the POST just vanishes without IIS ever knowing about it.

For a test we had them perform the same process with HTTPS and it works. For now this seems to be the work around but I have been asked that it not be a permanent solution and the client is demanding an explanation.

Thanks,

Matt

In news:%(E-Mail Removed),
Matt <(E-Mail Removed)> stated, which I commented on
below:
> If this is not the correct newsgroup to post this question please let
> me know where to post.
>
> I have a very strange issue that just came up with a client. My
> server is located in the Eastern US and the client is in the UK.
> Suddenly when they post to our server on port 80 nothing is received.
> We can watch the logs and other traffic is working fine as well the
> data received to the web page. Our network group proved the traffic
> does reach the server but then it just seems to disappear.
>
> The receiving application is ASP.NET and works fine with many other
> clients. Does anyone know how to get IIS to tell me where the issue
> might be? I have everything possible turned on in IIS logging and it
> shows nothing. It's like the POST just vanishes without IIS ever
> knowing about it.
>
> For a test we had them perform the same process with HTTPS and it
> works. For now this seems to be the work around but I have been
> asked that it not be a permanent solution and the client is demanding
> an explanation.
>
> Thanks,
>
> Matt

I am assuming they are opening the website as a web folder to make this work
(IE-File, open, type in URL, check the box 'Open as a Web Folder'. If so,
it's possible that UDP 1023 and above needs to be opened. SSL doesn't
require UDP >1023.

FTP works alot better. :-)

--
Ace
Innovative IT Concepts, Inc (IITCI)
Willow Grove, PA

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Directory Services
Microsoft Certified Trainer

Having difficulty reading or finding responses to your post?
Instead of the website you're using, I suggest to use OEx (Outlook Express
or any other newsreader), and configure a news account, pointing to
news.microsoft.com. This is a direct link to the Microsoft Public
Newsgroups. It is FREE and requires NO ISP's Usenet account. OEx allows you
to easily find, track threads, cross-post, sort by date, poster's name,
watched threads or subject.
It's easy:

How to Configure OEx for Internet News
http://support.microsoft.com/?id=171164

Infinite Diversities in Infinite Combinations
Assimilation Imminent. Resistance is Futile
"Very funny Scotty. Now, beam down my clothes."

The only constant in life is change...

No that is not the case. It is used just as web browser page. They can't even browse the page on port 80. Like I said, 443 is working fine.
"Ace Fekay [MVP]" <(E-Mail Removed)> wrote in message news:(E-Mail Removed)...
In news:%(E-Mail Removed),
Matt <(E-Mail Removed)> stated, which I commented on
below:
> If this is not the correct newsgroup to post this question please let
> me know where to post.
>
> I have a very strange issue that just came up with a client. My
> server is located in the Eastern US and the client is in the UK.
> Suddenly when they post to our server on port 80 nothing is received.
> We can watch the logs and other traffic is working fine as well the
> data received to the web page. Our network group proved the traffic
> does reach the server but then it just seems to disappear.
>
> The receiving application is ASP.NET and works fine with many other
> clients. Does anyone know how to get IIS to tell me where the issue
> might be? I have everything possible turned on in IIS logging and it
> shows nothing. It's like the POST just vanishes without IIS ever
> knowing about it.
>
> For a test we had them perform the same process with HTTPS and it
> works. For now this seems to be the work around but I have been
> asked that it not be a permanent solution and the client is demanding
> an explanation.
>
> Thanks,
>
> Matt

I am assuming they are opening the website as a web folder to make this work
(IE-File, open, type in URL, check the box 'Open as a Web Folder'. If so,
it's possible that UDP 1023 and above needs to be opened. SSL doesn't
require UDP >1023.

FTP works alot better. :-)

--
Ace
Innovative IT Concepts, Inc (IITCI)
Willow Grove, PA

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Directory Services
Microsoft Certified Trainer

Having difficulty reading or finding responses to your post?
Instead of the website you're using, I suggest to use OEx (Outlook Express
or any other newsreader), and configure a news account, pointing to
news.microsoft.com. This is a direct link to the Microsoft Public
Newsgroups. It is FREE and requires NO ISP's Usenet account. OEx allows you
to easily find, track threads, cross-post, sort by date, poster's name,
watched threads or subject.
It's easy:

How to Configure OEx for Internet News
http://support.microsoft.com/?id=171164

Infinite Diversities in Infinite Combinations
Assimilation Imminent. Resistance is Futile
"Very funny Scotty. Now, beam down my clothes."

The only constant in life is change...

In news:(E-Mail Removed),
Matt <(E-Mail Removed)> stated, which I commented on
below:
> No that is not the case. It is used just as web browser page. They
> can't even browse the page on port 80. Like I said, 443 is working
> fine.

Then the only other thing I can think of is something is now interfering or
conflicting with port 80, or it was disabled.

Ace

How could something be conflicting with just one client while hundreds of
others work fine?


"Ace Fekay [MVP]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> In news:(E-Mail Removed),
> Matt <(E-Mail Removed)> stated, which I commented on
> below:
>> No that is not the case. It is used just as web browser page. They
>> can't even browse the page on port 80. Like I said, 443 is working
>> fine.
>
> Then the only other thing I can think of is something is now interfering
> or conflicting with port 80, or it was disabled.
>
> Ace
>

In news:(E-Mail Removed),
Matt <(E-Mail Removed)> stated, which I commented on
below:
> How could something be conflicting with just one client while
> hundreds of others work fine?

That is a good question. If I had an opportunity to work on it, I may be
able to find out why. IIS can be complicated, but I just look at the basics
and work from the ground up. I used to run a web service using multiple IIS
servers in an NLB. One of our clients hosts numerous company sites for their
own clients, but sorry I cannot mention their names, because everyone here
will know them in a split second.

But to continue with the issue, if something is not conflicting, then I may
start looking at what else may be installed, such as if the Security and
Config wizard was ever run, URLScan, an IPSec filter, or a number of other
security apps installed (AV softawre may have firewall features) that may
have a factor or be causing this.

Sorry, can't think of anything else other than the above.

Ace