Link to home
Start Free TrialLog in
Avatar of William Fulks
William FulksFlag for United States of America

asked on

Internal Site Redirecting to .Com Site

I work for a city government and we are running a web-based app called Cityworks on a server called pwapp. To access the app you just open up http:\\pwapp\cityworks in your browser.

What's happening is that random times throughout the week, the site will stop working and give "page cannot be displayed" errors on individual pages. If you refresh 2 or 3 times, the page will eventually come up. Sometimes it will pull up hugedomains.com when you hit refresh at the login screen.

It turns out that hugedomains owns pwapp.com, which tells me that something on the site is not responding and causing a redirect from local pwapp to pwapp.com. However, it does this in IE, Firefox, and Chrome, so I don't think it's a browser-specific setting.

I've already contacted Cityworks support and they were like, "Ummmm....never heard of that one before" and I'm waiting to hear back from their tech. That was four days ago.

We are running a virtual Windows Server 2008 R2 with IIS 7. Nothing is set in HTTP Redirect.

Sometimes I can run iisreset from an elevated command prompt and that fixes it for a few hours or even a few days, and other times it does nothing. Rebooting the server gets the same results. Fixes are always temporary.

I'm not sure if it is an IIS issue or a DNS problem or something wrong with Cityworks' app.

Any ideas?
ASKER CERTIFIED SOLUTION
Avatar of Bud Durland
Bud Durland
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of William Fulks

ASKER

Thanks for the input. When I get back to work on Monday I will do some more tests and let you know.
Well guys, I suggested that they use the FQDN and they have not reported any more problems this week. I'm going to keep this open one more day and then close this and give points. Thanks again!
Thanks for the input, guys. We haven't had any more issues this week.