I have a sharepoint site hosted on windows server 2008 r2 and iis7.
the sharepoint site is hosted on port 80.
when I browse the site by typing the IP of the machine I receive a login window asking for credentials to connect the Machine. after providing credentials another login window asks for credentials to connect to the sharepoint site.
my question is that when a user logs in to a sharepoint site he uses the credentials specified in the active directory, so why in my case I recieve the login window twice ?
thanks
I've seen this before but rough guess:
When a SharePoint site has a reference to a resource held inside another site (not necessarily SharePoint).
e.g.
http://mysharepoint/
contains perhaps an image with the url http://someothersite/images/someimage.gif.
Not necessarily an image, it would be any resource.
Best way to check could be to view source and check to see if there are any urls pointing to outside the site.
Also check for urls starting with https: .
Hope this helps.
Another thought:
Since you're accessing the site through the IP address, maybe its treating your IP address site (http://192.168.1.1) seperately to the actual host headed sharepoint site (http://actualsharepointsite). Therefore the first authentication prompt is for the IP address host headed site and the second is for the actual host header of the sharepoint site.
To eliminate this, I would try (if you have access to these areas):
a) Logon to the actual box, and browse the site on the actual server using its proper host header (might need host file entry and proxy bypass setup depending on your environment). See how many times you're prompted for login details.
or b) In Central Admin, try to setup Alternate Access Mapping from the IP Address url to the actual host headed url.
Sorry if this doesn't help..
Related
I am going through the kentico11 developer essential training and the first requirement is to setup a kentico11 site. I followed the instructions and when done this is all I get
Error Message:
Either the website is stopped or the requested domain name is not configured for any website: http://localhost/Kentico11/CMSMessages/invalidwebsite.aspx
If you're an administrator of this site, you need to go to Sites and make sure the following domain name is configured either in the site properties or a domain alias of a running web site: localhost
How do I proceed? I applied the license in the training package
Once you have added the license for the domain you are using to run the site, you need to add the domain to the Site domain name field in the Sites application in Kentico.
Open the Sites application.
Edit (pencil icon) the site.
Type the domain into the Site domain name property on the General tab - since you are running the site under localhost, simply add localhost to the field.
Click Save.
Now when you visit the homepage, the error message should no longer appear.
Documentation reference:
https://docs.xperience.io/k11/configuring-kentico/managing-sites/setting-domain-names-for-sites
I have come to an issue while logging into the Parallels Plesk Panel with the username and password provided by our hosting agent.
It was going fine until I removed a directory through FileZilla application, which was holding the contents of a running live website.
After resetting the directory, I got an error message:
Internal error: Domain Service Web not exists: domain=example.com,
id=XXXX Domain Service Web not exists: domain=example.com, id=XXXX File
DSWeb.php Line 76 Type PleskFatalException
Then I found a solution after searching the error. But that was saying about removing and adding entries from and to psa database. I am using a windows system and no way to access this psa database.
Then I found some server administration service providers can solve this issue but they are asking tickets and payments. I doubt if they can help or if they ask me the credentials of the service. Is that the only and safe solution?
And somewhere else I saw I can use dbclient utility for running SQL query on Windows. How does that help?
Now I can't login through the panel, it shows the error:
The xxx.xxx.xxx.xx page isn’t working
xxx.xxx.xxx.xx redirected you too many times. Try: Reloading the page
Clearing your cookies ERR_TOO_MANY_REDIRECTS
I am not able to access mail accounts and some domains(were running good) show this error message:
The service is unavailable.
The one which I removed (directory and files) shows Web Server's Default Page of Parallels Plesk Panel when accessing the domain address through web browser.
I don't see any questions like this here in Stack overflow, but there are tags.
Waiting for your suggestion and help me to find the best solution for this.
Have you tried this?
http://download1.parallels.com/Plesk/PP11/11.0/Doc/ru-RU/online/plesk-linux-advanced-administration-guide/index.htm?fileName=68745.htm
Trouble shouting for:
Cannot Access Panel
Cannot Log In to Panel
If you get the error message "Access for administrator from address xx.xx.xx.xx is restricted in accordance with IP Access restriction policy currently applied." when trying to access Parallels Plesk Panel, it means that the Panel IP access policy does not allow you to log in from your current IP.
To access Panel from an IP address:
Here is a way of access psa table.
1-Log in to the server via SSH.Using Putty
2-Change the IP access policy in the psa database:
To find the current policy and its restricted and allowed IP addressess,run the following commands.
mysql -uadmin -p`cat /etc/psa/.psa.shadow ` psa
mysql> select * from cp_access;
mysql> select * from misc where param='access_policy';
Panel in a Virtuozzo Container: Broken Layout
I just purchased a domain for my blogger blog through google(goDaddy)
Currently, it is pointed to blogger web host.
I'd like to point it to my own web host as well, so i can host files, while not losing my blog stuffs from blogger.
Is this possible? for a domain to have 2 web host?
I'm sorry, i'm really new to these domain and hosting, any help would be appreciated. Thanks!
You can keep your domain on your site and then setup a subdomain-- like blog.YOURDOMAIN.COM-- and point that to your blogger account.
Go to http://www.google.com/a/domainname, replacing domainname with your domain name.
Now you will need to login to your Google account utilizing a username and password you previously created specifically for Google Apps for your domain. If you do not know this information, click 'Can't access your account.'
Once logged in, click the 'Domain Settings' tab.
Click on "Advanced DNS Settings".
You will now see listed your Sign-In Name, Password, and PIN.
Click Sign-In to DNS Console and use the Sign-In Name and Password to login.
You should now be in the Domain Control Center. Click Forward, and then select Forward Subdomain.
In the Add subdomain field, enter the subdomain.
Select http:// or https:// depending on your server settings.
In Forward this subdomain to, enter the URL you want to forward the subdomain to. This will be the URL for your Blogger blog.
To view additional options, click Advanced Options, and then select one of the following:
Forward Only — Specifies the length of time for this forwarding setting. Select one of the following redirect types:
I am permanently forwarding my domain — Redirects to the site you specified in the Forward To field using a "301 Moved Permanently" HTTP response. The HTTP 301 response code tells user-agents (including search engines) the location has permanently moved.
I am only temporarily forwarding my domain — Redirects to the site you specified in the Forward To field using a "302 Found" HTTP response. The HTTP 302 response code tells user-agents (including search engines) that the location has temporarily moved.
Forward with Masking
Title — Displays at the top of the browser window and in search results.
Description — A short description of your website to display in search engine results.
Keyword — A list of comma-separated keywords that describe the content and purpose of your website.
Click OK.
The main domain you just continue to point to the IP of your web host.
We have a SharePoint site which serves as our company site on the internet. Our company has 2 domains ".com" and ".co.uk". SharePoint works fine when you access the site using the ".com" domain. The problem is, when you try to access the site using the ".co.uk" domain, some pages (ones including custom lists, settings pages) do not work properly.
After doing some research, I found out that I needed to add the ".co.uk" domain under Sharepoint access mappings to make it work properly, but when I do that, I am redirected to the ".com" domain. By the way, the".com" domain already exists in the accesss mappings page.
So, what's the best way to configure our Sharepoint site to work for 2 different domains?
In addition to the alternate address mapping create a IIS website for it. This link might not 100% apply to what your using, but you should be able to make ends meet with it.
http://www.isaserver.org/img/upl/spskit/3quickstart/3quickstart.htm#_Toc58577520
I solved the problem today. Here's how:
First I learned how to extend a Sharepoint site using the video: http://technet.microsoft.com/en-us/sharepoint/Video/ff679931.
In SharePoint Central Administration, I extended the default site (SharePoint - 80) for the ".com" domain.
Used "Create a new IIS web site Name" option, used domain name as the name,
Used port 80, domain name as the host header and the default sharepoint path,
Didn't change Authentication and SSL options, allowed anonymous access
Used the ".com" domain in URL and used Internet as the zone.
After extending a new IIS site was created. In Internet Manager, I clicked "Edit Bindings" option for the new site. The ".com" domain was already set in bindings. I added the ".co.uk" domain into bindings as well.
In Central Administration > Alternate Access Mappings, I set the ".com" domain URL as the Default zone and the ".co.uk" domain as the Internet zone. This automatically added internal URLs for both domains.
I have a website running on a Windows 2003 server on IIS 6, serving pages for a LAN where everybody is working with a domain account. On other machines this works fine, no-one has to login to the website, the dynamic scripts pick-up the account-name from the HTTP request.
Only, when browsing from the server itself (via remote desktop e.g.), Internet Explorer still pops up the domain-login-dialog when navigating to this site. (both the usual URL and http://localhost/). This was no problem on the Windows 2000 server we recently migrated the website from.
I had this problem or similar and solved it by:
adding http://localhost to list of Intranet sites, via IE > Tools > options > security > Local intranet > Sites > advanced > add http://localhost. (This is necessary if you have IE Enhanced Security installed which assigns all intranet Web sites and all UNC paths that are not explicitly listed in the Local intranet zone to the Internet zone, even localhost or other domains that don't contain '.' symbol which would normally be considered intranet by default.)
also on Security > Local Intranet > see what level of security you're on, to ensure that logon details are passed through. If it's Custom then click the Custom Level... button, scroll right to the bottom, under User Authentication > logon > for me it's 'Automatic logon only in Intranet zone', which works.
Did you configure IE on your Windows 2003 box for "Enable Integrated Windows Authentication"? This needs to be configured in IE6 to automatically use the logged-in user credentials.
You'll probably have better luck on ServerFault for this issue, as it's probably down to server configuration. Take a look at this KBAlertz.com article, yes it's specific to SharePoint, but some bits are more general. I suspect (given that you've said you've migrated to a new machine), that the issue is around the new machine not being "trusted for delegation" so look at the part titled "Configure trust for delegation for Web parts"
Configure trust for delegation for Web
parts To configure the IIS server to
be trusted for delegation, follow
these steps:
Start Active Directory Users and Computers.
In the left pane, click Computers.
In the right pane, right-click the name of the IIS server, and then
click Properties.
Click the General tab, click to select the Trust computer for
delegation check box, and then click
OK.
Quit Active Directory Users and Computers.
If the application pool identity is
configured to use a domain user
account, the user account must be
trusted for delegation before you can
use Kerberos authentication. To
configure the domain account to be
trusted for delegation, follow these
steps:
On the domain controller, start Active Directory Users and Computers.
In the left pane, click Users.
In the right pane, right-click the name of the user account, and then
click Properties.
Click the Account tab, under Account Options, click to select the
Account is trusted for delegation
check box, and then click OK.
Quit Active Directory Users and Computers.
If the application pool identity is a
domain user account, you must
configure an SPN for that account. To
configure a SPN for the domain user
account, follow these steps:
Download and install the Setspn.exe command-line tool. To do
so, visit the following Microsoft Web
site:
http://www.microsoft.com/downloads/details.aspx?FamilyID=5fd831fd-ab77-46a3-9cfe-ff01d29e5c46&DisplayLang=en
(http://www.microsoft.com/downloads/details.aspx?FamilyID=5fd831fd-ab77-46a3-9cfe-ff01d29e5c46&DisplayLang=en)
Use the Setspn.exe tool to add an SPN for the domain account. To do
so, type the following line at the
command prompt, and then press ENTER,
where ServerName is the fully
qualified domain name (FQDN) of the
server, Domain is the name of the
domain, and UserName is the name of
the domain user account:
Setspn -A HTTP/ServerName Domain\UserName