Network issues in Windows Server 2008 R2

Question

System administration

Already once asked a similar question, but the answers, unfortunately, were not enough to put everything in order.
So, there is a “server” (in quotation marks, because the server is usually called uninterrupted and problem-free equipment), on which RemoteApp with 1C is running.

Configuration

:
CPU: Intel Core i7-870 (Lynnfield, B1)
2933 MHz (22.00x133.3) @ 3210 MHz (24.00x133.8)
Motherboard: ASUS P7P55D PRO
Chipset: Intel P55 (IbexPeak)
Memory: 16384 MBytes @ 668 MHz, 9.0-9-9-24
— 4096 MB PC10600 DDR3 SDRAM — Samsung M378B5273CH0-CH9
— 4096 MB PC10600 DDR3 SDRAM — Samsung M378B5273CH0-CH9
— 4096 MB PC10600 DDR3 SDRAM — Samsung M378B5273CH0-CH9
— 4096 MB PC10600 DDR3 SDRAM — Samsung M378B5273CH0-CH9
Graphics: nVIDIA GeForce 210 (GT218), 512 MB DDR2 SDRAM
Drive: WDC WD20EARS-00MVWB0, 1953.5 GB, Serial ATA 3Gb/s
Drive: WDC WD20EARS-00MVWB0, 1953.5 GB, Serial ATA 3Gb/s
Drive: WDC WD10EALX-009BA0, 976.8 GB, Serial ATA 6Gb/s
Drive: WDC WD10EALX-009BA0, 976.8 GB, Serial ATA 6Gb/s
Drive: Optiarc DVD RW AD-7260S, DVD+R DL
Drive: Intel Raid 1 Volume, Disk drive
Sound: Intel 5 Series/34x0 Chipset PCH — High Definition Audio Controller [B3]
Sound: nVIDIA GT218 — High Definition Audio Controller
Network: RealTek Semiconductor RTL8168D/8111D PCI-E Gigabit Ethernet Adapter
OS: Microsoft Windows Server 2008 R2 Standard (x64) Build 7601

When a static IP address is set, such a fun occurs (ping starts on itself):

Pings

C:\Windows\System32>ping 192.168.2.23

Обмен пакетами с 192.168.2.23 по с 32 байтами данных:
Ответ от 127.0.0.1: Заданная сеть недоступна.
Ответ от 127.0.0.1: Заданная сеть недоступна.
Ответ от 127.0.0.1: Заданная сеть недоступна.
Ответ от 127.0.0.1: Заданная сеть недоступна.

Статистика Ping для 192.168.2.23:
Пакетов: отправлено = 4, получено = 4, потеряно = 0
(0% потерь)

C:\Windows\System32>ping 192.168.2.108

Обмен пакетами с 192.168.2.108 по с 32 байтами данных:
Общий сбой.
Общий сбой.
Общий сбой.

Статистика Ping для 192.168.2.108:
Пакетов: отправлено = 3, получено = 0, потеряно = 3
(100% потерь)
Control-C
^C
C:\Windows\System32>ping localhost

Обмен пакетами с VIDEOSERVER [::1] с 32 байтами данных:
Ответ от ::1: время<1мс
Ответ от ::1: время<1мс
Ответ от ::1: время<1мс

Статистика Ping для ::1:
Пакетов: отправлено = 3, получено = 3, потеряно = 0
(0% потерь)
Приблизительное время приема-передачи в мс:
Минимальное = 0мсек, Максимальное = 0 мсек, Среднее = 0 мсек
Control-C
^C
C:\Windows\System32>ping 127.0.0.1

Обмен пакетами с 127.0.0.1 по с 32 байтами данных:
Ответ от 127.0.0.1: число байт=32 время<1мс TTL=128
Ответ от 127.0.0.1: число байт=32 время<1мс TTL=128
Ответ от 127.0.0.1: число байт=32 время<1мс TTL=128
Ответ от 127.0.0.1: число байт=32 время<1мс TTL=128

Статистика Ping для 127.0.0.1:
Пакетов: отправлено = 4, получено = 4, потеряно = 0
(0% потерь)
Приблизительное время приема-передачи в мс:
Минимальное = 0мсек, Максимальное = 0 мсек, Среднее = 0 мсек

C:\Windows\System32>

We ping our friend from another computer

C:\Users\Manager 23>ping 192.168.2.108

Обмен пакетами с 192.168.2.108 по с 32 байтами данных:
Ответ от 192.168.2.108: число байт=32 время=1мс TTL=128
Ответ от 192.168.2.108: число байт=32 время<1мс TTL=128
Ответ от 192.168.2.108: число байт=32 время<1мс TTL=128
Ответ от 192.168.2.108: число байт=32 время<1мс TTL=128

Статистика Ping для 192.168.2.108:
Пакетов: отправлено = 4, получено = 4, потеряно = 0
(0% потерь)
Приблизительное время приема-передачи в мс:
Минимальное = 0мсек, Максимальное = 1 мсек, Среднее = 0 мсек

C:\Users\Manager 23>

Under such circumstances, it is not visible in networked environments, nor is it observing anyone. But if you refer to it by the network name-patronymic (more precisely, only by name, since there is no domain), then you can connect. Well, RDP works.

If you put the dynamics, then everything works more or less tolerably. Only the IP changes, because the IP-distributing device is D-Link 2540 or someone similar, with a crooked firmware that is not able to save a static IP address, which is also impossible to update for some reason.

Does it make sense to try to stick a second network into it? And in general, with what all this can be caused? Is it possible to fix it without reinstalling? (The latter, of course, would not hurt - I don’t like to inherit crookedly working things. In my opinion, it’s easier to demolish everything and set it up from scratch. But this takes time, which never exists).

Well, as always - please do not beat, do not pour and treat with understanding.

UPD: Well, today I plugged in the network card I had at hand, and everything miraculously (or miraculously) worked. But it still didn't solve the issue.

Answer 1

It is worth updating the driver for the network card, or installing another one. Also check the brandmauer, and make the commentator's commands higher.

Answer 2

1. Disable IPv6
2. Make sure you only have 1 network adapter
3. Show ipconfig /all, route print for static address and ipconfig /all for dynamic address

Answer 3

the server is called uninterrupted and problem-free equipment

HA-HA-HA-HA-HA
Do a route print.

Answer 4

Well, I turned it off in network IPv6, it no longer connects via RDP. So, I'll write everything on Monday :(

Answer 5

For advice on chopping off ipv6, you need to beat the course textbook 70-642 on the head.
For some reason, ipv4 breaks for you, but for ipv6 everything works fine.
To begin with - which switch, transfer the network to 10Mbit / Half-duplex, and check if it works - increase the speed and turn on duplex.

Answer 6

By the way, same problem. Only the terminal server is lifted. The network behaves strangely from time to time.

Answer 7

Are all available updates for 2008r2 worth it? I had a farm at my last job, there were no problems with it - the same TS + 1c

Answer 8

Yes, I update regularly.