ping
3 Topics
Networking Related Commands for Azure App Services
First published on MSDN on Jul 24, 2017 The purpose of this blog is to give a general overview of the available commands to troubleshoot network connectivity issues with web apps, specifically when connecting the web apps to VNETs either in an App Service Environment (ASE) or a standard web app with a Point-to-Site VPN connection.81KViews4likes1Comment
Cannot reach/ping second 2019 server via Site-to-Site VPN, all other computers can be reached
Hi! I REALLY need help on this issue! Main office has: 192.168.1.0/24 Branch office: 192.168.2.0/24 i.e. two different subnets. DHCP is configured in the routers on each side; main/branch (i.e. no DHCP configured in the server). Main office has two Windows Server 2019: 1. Main server with AD, DNS, DC 2. Application server that is joined to domain and there are also clients in the main office: 3. Normal domain connected clients (Win10 and Win8) I can ping forth and back between all computers but when I try to ping from Branch to Main office towards the "2. Application Server" I don't get through. I have no probem to ping from Branch to "1. Main server" or towards normal clients in the "main network". If I ping "2. Application server" from any local computer on the Main office side, the server responds. Basic fault tracing tells me it's a server configuration thing versus the Branch network, something in the "2. Application server" stops the calls, right? I have checked the server's firewall (incoming ping) and also temporarely turned off the firewall, but no success. So firewall seems to be out of the question. I also added the branch's subnet in "1. Main server" under AD Services and Sites, no success. I really can't understand this magic going on in the second server, why doesn't it respond to calls from the Branch side? Please help! br /MarcusSolved4.4KViews0likes3Comments
Windows Server 2016 is not pingable while it can ping other devices and have DNS problems
Hello Community, I have the following problem: On my VMWare vSphere ESXi 6.7 I have two Windows Server 2016 VMs. One (WDS-01) provides the AD, DNS and DHCP Server, the other one (WDS-02) should provide the WDS and WSUS. While WDS-01 works perfect, I can't ping the WDS-02 from the WDS-01 or the coreswitch of my network. WDS-02 also don't have connection to the internet due to a problem with DNS name resolution. But i was able to add WDS-02 to my domain and WDS-02 was able to receive an IP-address lease from my DHCP Service running on WDS-01. WDS-02 can ping all other devices in the network but like I allready said, its not pingable itself. Hope somebody can help me with this problem. Thank you! JonasSolved91KViews0likes9Comments
