Link to home
Start Free TrialLog in
Avatar of bnrtech
bnrtech

asked on

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?
Avatar of umeshshi
umeshshi

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
Avatar of bnrtech

ASKER

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
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.
Avatar of bnrtech

ASKER

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
Avatar of bnrtech

ASKER

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.
Avatar of bnrtech

ASKER

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 :)
ASKER CERTIFIED SOLUTION
Avatar of bnrtech
bnrtech

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