Showing posts with label laptop. Show all posts
Showing posts with label laptop. Show all posts

Tuesday, March 20, 2012

Report Builder load failure on WAN-side of firewall

All,

Can anyone shed some light on this problem:

Using the same laptop and credentials I can successfully load Report Builder ONLY from the LAN-side of the firewall. However, if I reconnect using my Sprint AirCard I cannot load Report Builder; I get the now infamous "The remote server returned an error: (401) Unauthorized."

What ports are used by Reporting Service?

Thanks,

Brian

I'm not sure what's up with the AirCard connection, but I think I can explain the WAN/LAN difference. On the LAN side your default Windows credentials are sufficient to access the Report Builder files at http://hostname/reportserver/reportbuilder. On the WAN side, Windows integrated authentication doesn't work, so you get no Report Builder. The reason is that ClickOnce (which is responsible for downloading the application files to the client) cannot prompt for credentials, and it doesn't get any from IE, so if default Windows credentials don't work, you get nothing. The solution is to configure IIS on the report server to allow anonymous access to the virtual directory I mentioned above.

|||Does this work with port 443 also?

Report Builder load failure on WAN-side of firewall

All,

Can anyone shed some light on this problem:

Using the same laptop and credentials I can successfully load Report Builder ONLY from the LAN-side of the firewall. However, if I reconnect using my Sprint AirCard I cannot load Report Builder; I get the now infamous "The remote server returned an error: (401) Unauthorized."

What ports are used by Reporting Service?

Thanks,

Brian

I'm not sure what's up with the AirCard connection, but I think I can explain the WAN/LAN difference. On the LAN side your default Windows credentials are sufficient to access the Report Builder files at http://hostname/reportserver/reportbuilder. On the WAN side, Windows integrated authentication doesn't work, so you get no Report Builder. The reason is that ClickOnce (which is responsible for downloading the application files to the client) cannot prompt for credentials, and it doesn't get any from IE, so if default Windows credentials don't work, you get nothing. The solution is to configure IIS on the report server to allow anonymous access to the virtual directory I mentioned above.

|||Does this work with port 443 also?

Tuesday, February 21, 2012

Replication/Admin Help

We run a small business with a LAN of 2 pcs, a laptop pc, and a web server that runs Win2k Server with Exchange on it. My pc is used for most of the development and it also houses SQL Server (Developer) 2k. We have SQL Server (Developer) installed on the other network pc as well.

Here's the problem: We sometimes have to take my pc with us to use at different sites (with no internet connectivity at the time). When this happens, any data access on our web site is 'down' because our web data is in the sql server db on my machine. I want to replicate the db on the other pc so that we can take that machine to the different sites. I am having trouble getting this done.

Can someone give me some direction? Is there a good tutorial or a book or whatever somewhere? I am really in need of some sql server admin knowledgebase.

Thanks!!Have you considered merge replication? you could then publish to your network sites from either computer with transactional publications and have the two "master" databases have a merge publication between them. When the machine goes off site, the other will continue to provide data to the site and when the other machine returns, any update made to it can be merged with the local machine.

if this will do the trick, books online should have all you need as far as setting it up goes...|||Have you considered merge replication? you could then publish to your network sites from either computer with transactional publications and have the two "master" databases have a merge publication between them. When the machine goes off site, the other will continue to provide data to the site and when the other machine returns, any update made to it can be merged with the local machine.

if this will do the trick, books online should have all you need as far as setting it up goes...