I have a Windows 2008 R2 Server Core machine and would like to disable IPv6 on one of its network adapters. Essentially this if there was a UI:
Any ideas?
I have VM1 acting as an Active Directory and DNS server, and have installed SmarterMail (Free) on VM2.
If I remote desktop to VM2 I can connect to the mail server fine if I use 127.0.0.1:25. However if I use the computer name VM2:25 or VM2.domain.local:25 the connection times out.
In DNS I've added an MX record and pointed it back to VM2. This didn't make any difference.
I've checked the firewall settings (although I wouldn't think they would apply when logged on to the local machine) and added a rule for TCP on ports 25 and 110.
Still I can't connect when using the actual machine name. Any ideas?
Update based on Jim B's answer:
I can ping vm2 and get its IPv6 address returned.
Turning off Windows Firewall makes no difference.
I've tried enabling every relevant setting without success. (In terms of relay, the default settings seem to let you log in but won't let you relay without an account.)
I didn't mention there are two NICs on this VM, one set on the internal network of 192.168.200.x and the other set on NAT. I've bound SmarterMail to 192.168.200.x but alas still no progress.
For the purposes of running Active Directory and DNS Server, what are the minimum memory requirements for Server Core 2008 R2?
I've read of someone using 256MB. This seems pretty low although summing up the memory usage when running tasklist suggests it's OK.
Is there any way to know?
I'm building my first Windows 2008 Server Core machine (running R2) and want to rename the IPv4 network interfaces to something more meaningful.
It seems most likely that this is done using netsh interface ipv4 set but looking through the help hasn't turned anything up.
Could someone please advise the correct procedure?
I'm setting up two VMs under VirtualBox - one acting as an Active Directory controller, and the other joined to the domain. Both are running Windows Server 2008.
I'm trying to get the network settings right so that both VMs can access the Internet (they need to obtain an IP address from the host's network), and so that Active Directory works as well.
Everything was going fine until I installed the AD role, then that server could no longer access the Internet. I left the IP address to obtain automatically and bypassed the warning that appears, so I was surprised this stopped working.
I've fiddled with different network adapter options in VirtualBox and read up about them but haven't had any success so far. (Networking isn't something I have a strong knowledge of.) Does anyone know what the steps are to get this working?
Update, more detail:
Here is a list of different network settings I've tried on the domain controller. For all of these the DNS server has been set to 127.0.0.1 followed by the DNS servers used by the host.
Using "VirtualBox Host-Only Ethernet Adapter":
- Set to "Obtain IP address automatically" and picks up an address in the 192.168.56.x range
- No Internet access and cannot ping other addresses on the host's network
- Didn't test client accessing the domain controller
Using "Bridged Adapter":
- Set to "Obtain IP address automatically" and picks up a Windows auto-configured IP address starting with 169
- No Internet access and cannot ping other addresses on the host's network
- Didn't test client accessing the domain controller
Using "NAT":
- Set to "Obtain IP address automatically" and picks up a network configuration very similar to the host
- Internet access works fine
- Client cannot access the domain controller
Both VMs can talk to each other using "Internal networking" however obviously this means no Internet access.
I've been attempting to configure some links on the SSP home page. Most of these, including search admin, work fine. However the following give me an "Access Denied" error:
- User profiles and properties
- Profile services policies
- My Site settings
- Audiences
I've tried using the farm administrator account, SSP account, SSP web app account, and my own account which is a local administrator. Nothing is appearing in the ULS logs.
The only thing I know that might have caused this is that the service accounts were changed from local accounts to domain accounts.
Any ideas on what this could be or how to troubleshoot?
I'm investigating an issue where a user is uploading a large document to the web server. This is resulting in a time out at their end. However I'm wondering if it is possible to detect this from the server in order to determine if other users are affected.
There is a connection made while the document is being uploaded. So I'm wondering if IIS 6 is able to detect and record or log anywhere when a client request has timed out?
Possible Duplicate:
Perform an Unattended Install of Server 2008?
I'm new to unattended deployments and would like to create a script to do the following:
- Install of Windows Server 2008 including product key
- Install of components such as IIS
- Creation of local users
- Kick off other setup programs (e.g. for SQL Server)
The script would only be run every so often as it's for the creation of new virtual machines. However the final installation does need to be exactly the same each time which is why I'd like to script it.
I've been reading through the Windows AIK pages on TechNet and found several options. None seem to describe my scenario exactly and there is a lot of information there.
Does someone have some high-level points on how I would achieve these things and/or what specific doco I should read?
What is the best way to set up a SQL Server deployment that can be easily repeated across multiple virtual servers? Does Microsoft provide something for this, or perhaps Powershell scripts?
I'm using a web application (SharePoint) to create a database for Microsoft Single Sign On. Every attempt to create the database is giving a 'login failed' style error. For testing purposes I am using the same account on the SharePoint web application and timer service, Microsoft SSO Service, and in the 'Manage Server Settings for Single Sign-On' page in SharePoint.
The two SQL Server errors being logged are:
Login failed for user 'blah'
Error: 18456, Severity: 14, State: 16.
The Windows Server event log error show the same 'Login failed' message with the word 'master' in the data section.
I have tried:
- Giving the user sysadmin permission on SQL Server
- Changing the default database to one where the user has db_owner permission as well as setting it to 'master'
- Making the user local administrator on the SQL Server
The comments in this article on the SQL Protocols blog state that:
State=16 means that the incoming user does not have permissions to log into the target database... This can also happen if for example the default database for user FOO is not online (for example the database is marked suspect).
I think I've covered the permissions and SharePoint is using the databases so they shouldn't be marked suspect.
Does anyone have some ideas?
Every two to three days we are getting the following SCOM error:
The database tempdb in SQL instance MSSQLSERVER on computer sqlserver has experienced a significant change in free space
This has been happening since installing SharePoint 2007 SP2 and occurs in the middle of the night, probably while SharePoint is performing search indexing tasks.
Currently tempdb has a size of 313.88 MB and free space of 49.72 MB. I've been told the threshold for the alert is 45%. We are using SQL Server 2005 64-bit.
How can I resolve this issue and should tempdb be configured differently? I'm acting as an accidental DBA on this one! Thanks...
After backing up and restoring a site collection, incoming e-mail for the site collection no longer works.
In the ULS log, the following message appears (where mailalias is the name of the e-mail alias):
The Incoming E-Mail service has completed a batch. The elapsed time was 00:00:00. The service processed 1 message(s) in total. Errors occurred processing 1 message(s): Message ID: <0b7d0469-8bdc-4d9c-9834-aada5c458037@server> The following aliases were unknown: mailalias
In this case incoming e-mail for the alias is associated with an event handler/receiver.
I have a Windows Server 2003 SP1 machine that was service packed to SP2. If I now add additional components such as IIS to this machine, do I need to reinstall SP2?
If Windows handles this for me, how does it do so?
How do you implement high availability on SQL Server 2000? Are there any 3rd party tools out there or any other ideas?
In SharePoint it is possible to configure the Primary and Secondary site collection administrators from SharePoint Central Administration. It is also possible to configure them from the Site Collection Administrators page under Site Settings.
What is the difference between these two? Does it matter in functionality if a user is added to one vs the other?
I need to find out if full text search is installed on SQL Server 2005. I don't have permission to log into the box and fire up Setup to check. However I can run SQL Server Management Studio and connect to run queries with sysadmin permissions.
Does anyone know how to detect if this feature is installed?
Virtualization has some great benefits, but there are times when a virtualized server needs more performance and should be moved to physical.
My question is, how do you tell when these times are? I'm looking for measurable data and metrics that show moving a server to its own physical box would make a significant difference to performance. Personally I'm interested in Windows but presumably the essentials are the same across all platforms.
What app pool settings are recommended for a public facing web site in IIS?
What matters when making decisions about this (e.g. traffic, type of web application, etc...)?
Will the default settings be OK?
I'm mostly interested in hosting SharePoint on IIS6 and IIS7 but not exclusively!
In the recent past I was asked to set up a reporting facility for upper management so they can spy on what web sites users are visiting. This was done without any notice given to users. Unfortunately, I have a good friend with some rather unusual tastes who I knew would be caught! He also knew I set up the reporting...
To me, the lack of user notification was unethical. What similar experiences have you had that haven't "felt right" and left you questioning what to do? How did you deal with it?
At my organisation there are conflicting schools of thoughts around service accounts. This has come up because they wish to deploy SQL Server for the sole purpose of running SharePoint databases.
One group believe that a different service account should be used for each server application and for each environment (e.g. production, UAT/test, development). So in this example each SQL Server installation for SharePoint would have its own service account for prod, UAT and dev. Their reasons are security and preventing interference between environments.
Another believes that service accounts should be shared between production and test environments. So for the example there would be one SQL Server service account across prod, UAT and dev. (I'm not sure about sharing that account between different server applications.) Their reasons are security again as there are less passwords to change and reduced complexity.
Considering security, uptime and reliability, protection against mistakes, risk management, etc... what should be the recommended approach?
Thank you!