Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

companyweb/remote page can not be displayed

Status
Not open for further replies.

modularsolutions

Technical User
Oct 10, 2006
2
GB
I was reading through the follwoing thread thread931-1197504 and thought i would give you my own findings. I have installed several servers with SBE2003 installed on them and on one i had the annoying problem of the companyweb/remote not being displayed. If i got the client to put in the page was fine.

I found that compared to the other servers, the problomatic server was running a newer ASP.NET (2.0.50727), so i changed it to the older version (1.1.4322)and more importantly i found there was a virtual directory called "Remote" in both Default Web Site and Companyweb. I deleted one (up to you which one as not everyone uses companyweb) and it worked fine.
 
Interesting. Several hundred SBS boxes deployed, and I haven't seen that before.

You're forwarding port 4125 to the server, correct?
You're following the installation procedure EXACTLY when building the server, correct?

Anything in the event logs?

Pat Richard, MCSE MCSA:Messaging CNA MVP
Want to know how email works? Read for yourself -
 
As i said it was the first time i had ever seen this problem and it confused me as well as a couple of other associate IT companies we work with. I just felt i would share my findings as i never found my solution any where else on the net!

We did have a few problems with this server as we built it as we tried running the wizards at the same time as we transferred 65Gb of data!

Lesson learnt that the data transfer, should be done on it's own (even if it was done by taking the old server off line and installing the old HDD in as a slave).

There were various issues in the events but mainly to do with DNS, which i wouldn't think has much to do with IIS when testing internally. I think all the problems were caused by the wizards crashing as i mentioned before
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top