can not open default page

I am unable to access either http://192.168.187.1 or  http://192.168.187.1/owa from inside the LAN.

My setup is pretty basic. I have a W2003 Server which is 192.168.187.1 and one laptop (192.168.187.2) that is sucessfully joined to the domain.

Any suggestions?
bnrtechAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

umeshshiCommented:
Just do one thing bnrtech open web browser in W2003 and try to access it , if it is not working then check in the DOcuments tab in "Default Web Site" properties  of IIS snap in Administrative Tools in Control panel wether the main html or asp file is added i.e the main page you want to see.And also check "World Wide Web Publishing Service" service is started
0
bnrtechAuthor Commented:
I sat at the W2003 server and tried accessing http://192.168.187.1. Page can not be displayed. I also tried http://192.168.187.1/owa the IE icon kept spinning and interesting (bottom left corner) it appeared as if it were trying to access http://192.168.187.10/login.asp.

Main page for http://192.168.187.1 is listed as default.aspx and this file is located in the appropiate wwwroot directory.

WWW service is started (and set to automatic)
I
0
pcsmitpraCommented:
Please check you have mapped your website to correct Ip address and data path is mapped correctly. Add the home page you want to IIS -> Website-> Properties->  'Document tab' -> Default page.
0
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

bnrtechAuthor Commented:
I beleive this all looks good. The home directory is set to c:\inetpub\wwwroot and this location does contain default.aspx. Attached are some screen shots that I believe answer the other items you noted. I believe everything in these items are ok (??).
web-site.JPG
default.JPG
0
bnrtechAuthor Commented:
Anyone good with SharePoint? This problem most likely has to do with SharePoint being on this server. I say this because....

I finally had a chance to open a MS support call. First they sent me to the que that handles OWA. The support guy tried somethings but had no luck. Than the OWA person confereced in someone with the IIS team. The IIS person 'kicked the tires' but no luck. Than the IIS person noticed that I had SharePoint installed on this server too, so she did some testing to see if IIS was ok when outside of SharePoint and IIS responded correctly. So than we concluded that we need a SharePoint support person on the call, but they are only available (accordint to the OWA and IIS support people) via a call back service. This was yesterday and I am waiting to hear from the SharePoint person. Stay tuned.
0
bnrtechAuthor Commented:
this one definitely falls in the 'unbelievable' category.

So after mutiple conversations with MS (with support from OWA, IIS and SharePoint team) I have gotten absolutely no where. Clearly the problem has more to do with SharePoint playing nice with other apps, but no one can identify and/or resolve the actual problem.

So after wasting too much of my personal time on this matter I have decided to do a fresh install on this server and only put E2007 back on this box. Than setup a seperate box to host SharePoint and SQL. I can tell you that there was a collective sigh of relief by MS when I decided to scrap the current setup and start over :)
0
bnrtechAuthor Commented:
Well folks I am back up and running. I did a complete clean install of W2003 (64bit), E2007 and all updates for both products. Once I did that everything worked perfectly. Moral of the story - SharePoint was the problem. Thanks for trying to help me!
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft IIS Web Server

From novice to tech pro — start learning today.