mwillmott's questions

I am trying to set up VPN on our server but something strange seems to be going on with port 1723. We are not on a typical internet connection: the connection is broadcast over radio transmitters and so a CAT5 cable comes straight into the office and we just plug it into a switch. The provider handles DHCP, port forwarding and seperates all the different networks. So we don't have a router. Our provider has opened every TCP and UDP port and forwarded it our servers IP (i know we don't need every port but it wasn't working so we decided to do this temporarily).

However, something is blocking port 1723. The required rules are enabled in the server firewall (i believe). When the firewall is enabled and we attempt to connect it says "Connection timed out". When the firewall is disabled is says "Connection refused". This seems to suggest that it is the server blocking this rather than something else on the network.

Does anyone have any suggestions as to what might be wrong?

Michael

I am running SBS 2008 and have just installed SQL 2008 alongside SQL 2005. My understanding is that the default instance created in SQL 2005 is not needed and only the SBSMONITORING instance is needed. I have removed the default instance (as i want to create a new default instance in SQL 2008) and everything has worked but the reporting services remains installed and i can't get rid of it. No error messages are generated during the uninstall process so i have no idea what is going on.

Any thoughts?

Michael

So i am running IIS7 with one SSL site on it. I have a few different domains and subdomains that all point to my external IP. When using http they all direct to their respective sites using host headers. Whenever someone uses https on any of the domains they all point to my SSL site.

I only want people who type in https://sub.domain.com (for example) to end up at my secure site and for anything else to just not go there, it can throw an error or direct to the http version, it doesn't matter.

Is there a way of getting IIS7 to check the host header and throw an error if it doesn't match my specific subdomain?

Thanks,

Michael

I have Exchange 2007 installed on SBS 2008. I also run a web server on the network. I only have one static IP and all traffic trough port 443 is routed to the webserver.

I would like to publish the ActiveSync application externally. If i temporarily route 443 traffic to the SBS then it is published (along with owa and everything else which i don't want).

Is there a way to host the ActiveSync application on the web server (Server 2008 with IIS7) or to get it to route traffic meant for the ActiveSync application?

I have tried creating a site on the webserver which uses the ActiveSync folder on the SBS but that does not seem to work.

Thanks,

Michael

Simply, the Sharepoint intranet site that is automatically installed with SBS 2008 is bound to port 5555 in IIS so to get to it you can browse to server-name:5555 and then authenticate using domain credentials.

I have added another binding on port 80 using a host header so intranet.localdomain.local (and added the required record in the DNS).

This works fine from any computer on the domain, you can go to the nicer address and authenticate no problem. However, when you browse to the port 80 binding on the local server it reaches it but fails to authenticate.

I cannot figure out why and it is really annoying. Not essential to fix but it would be nice. Any ideas?

Michael

I am running FSRM on SBS 2008 to apply storage quotas to user folders. Is it then possible to display these user specific quotas and usage when the user logs onto an intranet website that is using ASP.NET?

i.e. User1 logs onto the intranet to see a message that says he has a quota limit of 5Gb on a specific folder and he is using 4GB of it.

Thanks,

Michael

I have come across this problem before, it doesn't generally get in the way too much but i would really like to know why it happens.

I am running SBS 2008, i changed the Bindings for the Sharepoint intranet so that instead of browing it via server-name:987 i can browse it on port 80 using the host header intranet.localdomain.local (for which an A record has been configured in DNS).

When client computers browse to intranet.localdomain.local it then asks them to authenitcate which they do with their windows credentials and ta da it works no problem. When i browse to intranet.localdomain.local on the SBS server it doesn't authenticate with windows credentials. It just doesn't work. If i browse to it using the original server-name:987 then it works fine.

Does anybody know why this is?

I am completely stumped and don't have a great deal to go on so i am hopping that somebody can suggest what might be wrong.

I have been successfully running a DNS server and Webserver, they are both on separate machines behind a router. My domains nameservers point to the DNS server which contains the a records. The router sends all DNS traffic (coming in at port 53) to the DNS server and routes all HTTP traffic (ports 80 and 443) to the webserver.

Everything has been working fine for ages... until all of a sudden it didn't. Now, whenever i try to view any of the websites i host it just doesn't work. "The connection to the server was reset whilst the page was loading".

When i try to view the websites from inside the network, every single one of my domains points to the router.

The odd thing is, if i view the one website that is configured to use SSL from anywhere then it works so it seems to only be a port 80 issue.

I have recently installed SP2 on the webserver (Windows Server 2008), other than that i am pretty sure nothing else has changed. The NAT tables are all correct on the router.

I don't understand! Any suggestions would be greatly appreciated.

I have installed VisualSVN server on Windows Server 2008. The server is part of a domain but not the domain controller, it is just a data server and now an SVN server. VisualSVN uses port 80 and can only be access from inside the network (i do i by going to the dns name of the server). However, ever since i have installed this, other computers on the network can no longer access the shared folders on the server EXCEPT the domain controller which has no problems accessing the shares.

I am stumped, i am guessing it is something to do with Apache running and not using host-headers (or whatever the Apache equivalent may be) but just being bound to the servers DNS name or IP.

Any suggestions?