networking
926 TopicsOutlook is sending duplicated mails
Hello dear Microsoft Community I've got following problem: With one of our clients there is an issue with Outlook/Mailing The mailbox is IMAP If he sends Mails to someone they'll recieve the sent message, for like 20 times. the only suspicous thing is, that we can see 3 duplicates of that mail in the 'sent' folder. but regardless it was recieved alot more than 3 times, either way. Do you have an idea ? I already updatet Microsoft Windows & Microsoft Office 365 made a new profile checked for Add-Ins or antivirus applications I also looked it up on our firewall we also checked the log on the mailserver greetings and im looking forward to recieve some help from YOU217KViews1like5CommentsI can't Turn on network discovery
Hi Why in Advanced sharing settinggs the Turn on network discovery can't save the settings in Windows Server 2019 Preview? Although as an admin I turn it on and save settings, it's again off when I open Advanced sharing settinggs. The second problem is that when I click Choose media streaming optons, I get the message The page failed to load.211KViews1like22CommentsWindows Server 2019 Build 17623 SMB1 does no more exists?
Hello, I tried for a test to enable SMB1 support for the build 17623, but when I give the PowerShell command: Set-SmbServerConfiguration -EnableSMB1Protocol $true I have the error: Set-SmbServerConfiguration : The specified service does not exist. At line:1 char:1 + Set-SmbServerConfiguration -EnableSMB1Protocol $true + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (MSFT_SmbServerConfiguration:ROOT/Microsoft/...erConfiguration) [Set-SmbSe rverConfiguration], CimException + FullyQualifiedErrorId : Windows System Error 1243,Set-SmbServerConfiguration Could you confirm that it is no more possible to enable SMB1? I know it is deprecated, but we have still a pair of Windows Server 2003 domain controllers and so it is not possible to join the domain for the server with the build. MarcoSolved200KViews0likes11CommentsWindows Server 2019 warns No Internet Access after AD, DNS and DHCP setup
Hi all. I have a Windows Server 2019 VM (HyperV) where I setup my first DC. I also setup DNS and DHCP on the server. After deploying these, the yellow warning icon appeared on the network icon in the bottom right corner, and it says "No internet access". Indeed, Internet access seems to be working normally. The only issue is the DNS sometimes unable to resolve certain random domains. It seems that unbinding IPv6 from the NIC almost solved this issue, but the warning icon and the No Internet message remains. I tried the troubleshooting tool. It is unable to diagnose the issue, and suggests a network reset. I did it twice, but it did not change anything. I took a dump of the network packets when the diagnostic tool is run, but I see nothing unusual. It finally connects to http://www.microsoft.com:80/ which I think is the normal way to determine if Internet is available. The server responds 200 Ok and some codes. I don't know where to look further. My ipconfig /all: Windows IP Configuration Host Name . . . . . . . . . . . . : SrvApp19 Primary Dns Suffix . . . . . . . : psw.local Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : psw.local Ethernet adapter Ethernet: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft Hyper-V Network Adapter Physical Address. . . . . . . . . : 00-15-5D-00-78-03 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes IPv4 Address. . . . . . . . . . . : 10.0.0.112(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 10.0.0.254 DNS Servers . . . . . . . . . . . : 127.0.0.1 NetBIOS over Tcpip. . . . . . . . : Enabled I attach one of the diagnostic reports. Thank to anyone who can help.181KViews1like19CommentsDCOM was unable to communicate with the computer
i ran dcdiag on all my for dc 2,3,4,5 dc2 = windows 2016 dc3 = windows 2012 dc4 = windows 2012 dc5 = windows 2016 I get the following error DCOM was unable to communicate with the computer 1.1.1.1 using any of the configured protocols; requested by PID 19f8 (C:\Windows\system32\dcdiag.exe). An error event occurred. EventID: 0x0000272C Time Generated: 10/08/2020 11:20:39 Event String: DCOM was unable to communicate with the computer 10.10.0.1 using any of the configured protocols; requested by PID 19f8 (C:\Windows\system32\dcdiag.exe). An error event occurred. EventID: 0x0000272C Time Generated: 10/08/2020 11:21:57 Also, note that 10.10.0.1 IP does not exist and its not configured in nic or forwards Please assist171KViews0likes14CommentsMoving domain between Office 365 tenants
I need to move one SMTP domain between Office 365 tenants. If I add this domain to tenant 2 so that I can get the TXT record for for verification will it have effect for email routing for users that are sending mail to this domain from tenant 2?165KViews0likes5CommentsBest practices: sharing folders, NTFS+share permissions and the Everyone permissiion
Hi! Trying to follow best practices on sharing data folders using security groups instead of users, I rolled down the hill and I can't go any further. I have a data folder shared on the network. The data is on my Server 2016 (I tried this on a Server 2012R2 and it does the same). Inside that folder, there is a subfolder that I want to give permissions. So I created a security group and give permission to that security group (following https://social.technet.microsoft.com/Forums/office/en-US/c6242159-d15d-417e-91f8-eb19c0da3a35/best-practices-for-basic-ntfs-permissions-on-a-share?forum=winserverfiles) and put a user into that group. Then I tried to use it to no avail. The user can't access the folder. If I directly put the user in the permission list instead of using the security group, it works as expected. If I analyze the effective permissions, I get X everywhere for the group, with "Share" on the "Access limited by" column. But the network share is Everyone - Full Control (and no other in the list). As you can see https://superuser.com/questions/1276744/windows-file-permission-access-limited-by-share https://social.technet.microsoft.com/Forums/ie/en-US/b58a08ee-7d7c-4d73-a8e3-587a89f0d67a/domain-users-recieve-access-denied-errors-for-folders-they-have-permissions-to-access?forum=winserverfiles, https://social.technet.microsoft.com/Forums/windows/en-US/d1248276-3955-4c68-9027-c8f1a82185b4/quotaccess-limited-by-sharequot-unable-to-access-files-via-security-group-membership?forum=winserverfiles or https://social.technet.microsoft.com/Forums/en-US/7ee5e34c-bbfa-41c9-a08b-49e3eca7353c/access-limited-by-share-for-effective-permission-on-assigned-group-if-the-group-doesnt-have?forum=winserverfiles, I'm not alone. The last post has the correct identification of the problem: the security group that I use is not included in the definition of Everyone for Microsoft, so I have to manually add the security group to the root share permission. But having dozens of security groups, adding all of them to the root share folder's permission list is not a funny thing to do. So, what's the correct way of doing this?Solved159KViews1like5CommentsBypass LBFO Teaming deprecation on Hyper-V and Windows Server 2022
Starting with Windows Server 1903 and 1909, Hyper-V virtual switches on an LBFO-type network adapter cluster are deprecated (see documentation). The technology remains supported, but it will not evolve. It is recommended to create an aggregate of type SET. In practice The SET is a very interesting technology that has some constraints. The interfaces used must have identical characteristics: Manufacturer Model Link speed Configuration Even if these constraints do not seem huge, we are very far from the flexibility of LBFO Teaming. As a reminder, this one has absolutely no constraints. In practice the SET is recommended with network interfaces of 10Gb or more. Therefore, we are very far from the target of the LBFO (use of all integrated boards with motherboard pro, Home Lab, refurbish). If SET cannot be used As of Windows Server 2022, it is not possible to use the Hyper-V Management Console to create a virtual switch with LBFO, as it will prompt an error saying that LBFO have been depreciated. However, it is possible to use PowerShell to create this virtual switch. First, create the Teaming of your network cards using the Server Manager, in my case the teaming will be with LACP mode and Dynamic load balancing mode. Then execute the below PowerShell Command to create the virtual switch based on the teaming created in the previous step: New-VMSwitch -Name "LAN" -NetAdapterName "LINK-AGGREGATION" -AllowNetLbfoTeams $true -AllowManagementOS $true In detail: The virtual switch will be named "LAN" The network adapter cluster teaming is named "LINK-AGGREGATION" The aggregate remains usable to access the Hyper-V host. You will see your network teaming up and running on Hyper-V host. Thats it!152KViews6likes10Comments