First off, I must mention that I was not around for the install of anything on the server at my company. I came on later and then, due to time restraints on my end, another guy came in to do some Sharepoint work. I think someone other than myself may have messed some stuff up...majorly.
I have no problems connecting to my server from outside and I am able to access any site(s) configured in IIS. I am even able to connect to some state of RWW, however it is not configured correctly at all. When I browse to the RWW site from the SBS Console, it goes to some random test site that someone set up, and does not go to the same site that I access from outside. I can't find where the test site is and can't figure out how to change it. Therefore, I cannot correctly configure the RWW settings for users. Also, the psuedo RWW site that I can access doesn't have all the links like connect to computer, etc. It only has Check Email and Internal Web Site. Also, I have no idea where I can tell the Internal Web Site button to point to my local intranet site.
In IIS, the SBS Web Applications site has the right bindings and this is where I can access the psuedo RWW site, but there is nothing in IIS related to the incorrect test site that the Console points to. Where is the Console getting its site location from and why is it different from the IIS site's location? This is all stuff that I believe was set up during the SBS install so how could it have gotten changed? The location of the RWW site is still in the correct location from what I've read in all other forums, so what is this other location that the Console might be pulling from?
Also, from the Console, I can't even enable the RWW site if I wanted to. There appears to be some major problems and nothing I have tried has fixed anything. I could just scratch it all and create my own version of RWW, but why reinvent the wheel? Is there any way I can fix this, restore it back to default, or reinstall just this part without reinstalling the whole server?
On another note, the Check Email button does nothing as well, which I know is related to OWA. I haven't yet gotten around to fixing the problems with Exchange though, so that can wait for another post.
I have no problems connecting to my server from outside and I am able to access any site(s) configured in IIS. I am even able to connect to some state of RWW, however it is not configured correctly at all. When I browse to the RWW site from the SBS Console, it goes to some random test site that someone set up, and does not go to the same site that I access from outside. I can't find where the test site is and can't figure out how to change it. Therefore, I cannot correctly configure the RWW settings for users. Also, the psuedo RWW site that I can access doesn't have all the links like connect to computer, etc. It only has Check Email and Internal Web Site. Also, I have no idea where I can tell the Internal Web Site button to point to my local intranet site.
In IIS, the SBS Web Applications site has the right bindings and this is where I can access the psuedo RWW site, but there is nothing in IIS related to the incorrect test site that the Console points to. Where is the Console getting its site location from and why is it different from the IIS site's location? This is all stuff that I believe was set up during the SBS install so how could it have gotten changed? The location of the RWW site is still in the correct location from what I've read in all other forums, so what is this other location that the Console might be pulling from?
Also, from the Console, I can't even enable the RWW site if I wanted to. There appears to be some major problems and nothing I have tried has fixed anything. I could just scratch it all and create my own version of RWW, but why reinvent the wheel? Is there any way I can fix this, restore it back to default, or reinstall just this part without reinstalling the whole server?
On another note, the Check Email button does nothing as well, which I know is related to OWA. I haven't yet gotten around to fixing the problems with Exchange though, so that can wait for another post.