» Не видно компьютеров в сетевом окружении, пинги идут

setqqq
выше посмотри что написал 2as Причин неисправности может быть очень много.

какая ОС на всех компах в 192.168.ххх.ххх ? какие настройки сделаны.
уважаемый мы не телепаты давайте информацию чтоб можно было дальше продолжать.

p..s уже много раз писалось пишется и буит писаться хорошо сформулированный вопрос - половина ответа

Добавлено:
Profi1C
в настройках сетевой карты стоит не стоит галка на энергосбережение ? ч..з какие интервалы времени такое "счастье" вылетает ?

У меня был случай. Сеть ~50 машин. Один комп не виден в сети. Пингуется, находится через поиск, сам сеть видит, а его никто. И ресурсы на нем есть расшареные. Выяснилось что это все потому что в строке "описания" на закладке "имя компьютера" в "свойствах" была написана длинная строка на русском языке. Поменял и все стало на свои места.

Подскажите пожалуйста есть локальная сеть, но я не могу видеть подключенные к ней компьютеры, к моему компу также подключен ADSL модемю Вот ipconfig:

Настройка протокола IP для Windows


Подключение по локальной сети 3 - Ethernet адаптер:

DNS-суффикс этого подключения . . :
IP-адрес . . . . . . . . . . . . : 192.168.14.168
Маска подсети . . . . . . . . . . : 255.255.0.0
Основной шлюз . . . . . . . . . . : 192.168.192.249

Подключение по локальной сети 2 - Ethernet адаптер:

DNS-суффикс этого подключения . . : telecom.by
IP-адрес . . . . . . . . . . . . : 10.3.24.31
Маска подсети . . . . . . . . . . : 255.255.252.0
Основной шлюз . . . . . . . . . . : 10.3.24.1

ADSL - PPP адаптер:

DNS-суффикс этого подключения . . :
IP-адрес . . . . . . . . . . . . : 93.125.66.10
Маска подсети . . . . . . . . . . : 255.255.255.255
Основной шлюз . . . . . . . . . . : 93.125.66.10

NetBIOS включен на сетевухе, на которой локальная сеть д.б. видна, в остальных местах отключена. вроде все темы проштудировал, все почитал и попробовал, но ничего не выходит...

Lubitel1
ipconfig с других компов под спойлер давай

Вот Ipconfig другого компа, с кот. все видно нормально:
C:\Documents and Settings\user>ipconfig

Настройка протокола IP для Windows


Подключение по локальной сети 7 - Ethernet адаптер:

DNS-суффикс этого подключения . . :
IP-адрес . . . . . . . . . . . . : 192.168.14.141
Маска подсети . . . . . . . . . . : 255.255.0.0
Основной шлюз . . . . . . . . . . : 192.168.192.220

Опять, таки, на этот компьютер я зайти могу (через IP), правда почему-то в расшаренные папки его не могу попасть...

так ! у тя вот эти два компа в одной группе нах-ся ? и как ты их добавлял в эту самую группу ??

Через "Мой компьютер" свойства, закладка "Имя Компьютера", рабочая группа - изменить - раб. группа MHN.

Сетевое окружение\Установить малую или домашнюю сеть ---. еще её сделай

что с пользователями ? гость открыт или нет ???
XpTweaker XPAntySpy запусти посмотри что выставлено в настройках сети

Гость включен, XPAntySpy прошелся из локальной сети отключен только "отключить встроенный брандамаузер", все остальное включено (ну т.е. птички не стоят), из служб по XPAntySpy отключено только "служба сообщений" и "служба индексации файлов"...

Цитата:

Сетевое окружение\Установить малую или домашнюю сеть

сделал ?

Делал, все осталось как и было...

вытяни руки - всё дело в них

Lubitel1

По моему опыту - в сети д.б. всего один комп, осуществляющий функцию сетевого браузера. В противном случае - возможна конкуренция и компы не будут видны. Нужно отключить на всех компах службу обозревателя компов в сети, оставив ее только на одном, который включен более всех других по времени. Если посмотреть лог событий, то там можно найти запись об объявлении выбороы Демократия, мать ее... Это справедливо для одноранговой сети. При наличии домена контроллер автоматом берет на себя функцию броузинга сети и всегда все хорошо. Как при Сталине

Kernell32 очень умно, ну можешь, в принципе, об стену убится...

alexeySTP очень похоже на правду, нда службу на всех компах проблематично будет выключить, сеть домашняя, компов около 200, я там и 10 человек не знаю, можно поподробнее объяснить по поводу "Записи об объявлении выбора или выборов" (тут непонятно)?

Все просто - проверяешь "просмотр событий - система" и там видишь запись о том, что комп такой-то объявил себя обозревателем сети и что назначаются перевыборы. После этого, как правило, в сетевое окружение рабочей группы войти не удается, а расшаренные ресурсы видны только по IP. У тебя, судя по всему, ситуация тупиковая... Ибо если нет мастер-браузера, то что ты увидишь в сетевом окружении? Выборы, как правило, ничем не заканчиваются. Причем, от типа ОС это не зависит. Ей-бо, без отключения (останова) службы на всех компах, кроме одного, в одноранговой сети все хорошо не бывает. То есть, бывает, но очень недолго - рано или поздно возникает описанная ситуация.

Kernell32
Я никогда не присоединял ни один комп к рабочей группе workgroup. Все видны сразу при наличии только одного компа, проводящего обзор сети.

Lubitel1
слушай мужик, там всё проще простого. я эту шаньгу великое множество раз ставил и всё по сей день работает. а Товарищу alexeySTP с его опытом можно идти дальше. службу "обозреватель компов" ты отрубить то отрубишь только вот где отрубишь никакого "Отобразить компьютеры рабочей группы" в жизни недождешься. то что есть один комп на котором это всё хранится я не спорюю.


Цитата:

При наличии домена контроллер автоматом берет на себя функцию броузинга сети и всегда все хорошо

ненадо впутывать домен и раб. группу это две большие разницы.
теперь по факту: "у вас нет прав тра-та-та--та обратитесь к админу" - какие пользователи созданы и включены на компьютере на который пытаемся зайти ? где инфа ! с которого пытаемся зайти что за пользователь и какие у него права ?? в настройках сетевеого подключения неубрана ли галка "Общий доступ к файлам и принтерам" - ???

Добавлено:
alexeySTP

Цитата:

Kernell32
Я никогда не присоединял ни один комп к рабочей группе workgroup. Все видны сразу при наличии только одного компа

p..s если они заведены в эту группу и тот кто пытается из любой группы зайти в видимоё workgroup имеет права на это, и на workgoup'овском компе разрешен соответствующий доступ.

Добавлено:

Цитата:

Все видны сразу при наличии только одного компа

какого компа ? взять офисную сеть. есть там один комп пускай на нём мылосерв крутится, инет ч..з роутер. мылосервак надо пологать должен работать постоянно для тех кто включен и для тех кто на него почту шлёт(т..е для всех) - вырубим его хоть на сутки ]:-> остальные компы включай выключай перезагружай но они будут видеть себя и без него, но с включенной слудбой обозревателя компов на всех машинах. вывод: служба должна быть включена постоянно. Чесно говоря я эту схему больше всех неперевариваю. Потомучто можно и без обозревателя файлы перекидывать.

Kernell32

А, собственно, с большинством выдвинутых постулатов спорить никто и не собирается.
Логично, что копирование файлов с/на шары не нуждается в обозревателе сети - это очевидно.
Далее - доступ к шарам осуществляется по пользователям в соответствии с выданными правами на каждом отдельно взятом компе - с этим тоже глупо спорить.
Сеть с доменом и одноранговая сеть - 2 большие разницы - а кто же против?
Если убрать галку общего доступа к принтерам и файлам - на комп войти нельзя - это очевидно.
Однако повторюсь, что у мелкомягких есть косячок по одноранговой сети - если начинается конкуренция среди машин за право взять функции основного обозревателя сети на себя, выборы зачастую ничем не оканчиваются и в рабочую группу вообще зайти нельзя. Собственно, с этим (наверное) и был связан вопрос.
Опять же, наличие одного обозревателя в сети - это просто упрощение схемы. Именно сервер должен нести эту функцию, т.к. он включен постоянно. Во всяком случае, у меня в одноранговой сети все так и работает и всегда видны все компы в сетевом окружении, даже подключенные через VPN.
Критерий истины - эксперимент. Пусть человек просто попробует, если ему надо видеть компы в сетевом окружении. Широковещательные пакеты-то ходят по сети! Они не могут не ходить!

alexeySTP
согласен пусть попробует хуже небудет

что то с DNS, может группы разные. перебей маки если с образа ставил винду!

nekisliy
ты хоть сам то понял что вообще ляпнул ?

Цитата:

ты хоть сам то понял что вообще ляпнул ?

Это называется стрельба по площадям - авось попадет.
Вывалил все термины, которые знает

Добрый день проблема с вводом компьютера в домен. Не могу ввести комп (Windows 2k8 64x ) пишет сетевой путь не найдет причем домен пингуется все нормально только в если строке вводить имя не видит (т.е \\lvs.onpp). заходит на любой комьтер.
netdiag -v c компьютера
[more]
Gathering IPX configuration information.
Querying status of the Netcard drivers... Passed
Testing IpConfig - pinging the DHCP Server... Passed
Testing Domain membership... Passed
Gathering NetBT configuration information.
Testing for autoconfiguration... Passed
Testing IP loopback ping... Passed
Testing default gateways... Passed
Enumerating local and remote NetBT name cache... Passed
Testing the WINS server
Подключение по локальной сети 2
There is no primary WINS server defined for this adapter.
There is no secondary WINS server defined for this adapter.
Gathering Winsock information.
Testing DNS
Testing redirector and browser... Failed
Testing trust relationships... Skipped
Testing Kerberos authentication... Skipped
Gathering routing information
Gathering network statistics information.
Gathering configuration of bindings.
Gathering RAS connection information
Gathering Modem information
Gathering Netware information
Gathering IP Security information

Tests complete.


Computer Name: SERVER-WSUS
DNS Host Name: SERVER-WSUS.lvs.onpp
DNS Domain Name: lvs.onpp
System info : Windows Server (R) 2008 Standard (Build 6002)
Processor : Intel64 Family 6 Model 15 Stepping 11, GenuineIntel
Hotfixes : none detected


Netcard queries test . . . . . . . : Passed

Information of Netcard drivers:

---------------------------------------------------------------------------
Description: RAS асинхронный адаптер
Device: \DEVICE\{D6D34145-B91A-41F3-81AE-F9C2103FAE90}

Media State: Connected

Device State: Connected
Connect Time: 00:09:05
Media Speed: 28 Kbps

Packets Sent: 0
Bytes Sent (Optional): 0

Packets Received: 0
Directed Pkts Recd (Optional): 0
Bytes Received (Optional): 0
Directed Bytes Recd (Optional): 0

[WARNING] The net card 'RAS асинхронный адаптер' may not be working because it has not received any packets.
---------------------------------------------------------------------------
Description: Intel(R) PRO/1000 PL Network Connection - Teefer2 Miniport
Device: \DEVICE\{D4A5D3CA-765B-48DC-804B-C5A0E6343588}

Media State: Connected

Device State: Connected
Connect Time: 00:09:32
Media Speed: 100 Mbps

Packets Sent: 2230
Bytes Sent (Optional): 344272

Packets Received: 11634
Directed Pkts Recd (Optional): 2195
Bytes Received (Optional): 577788
Directed Bytes Recd (Optional): 577788

---------------------------------------------------------------------------
Description: Минипорт WAN (Сетевой монитор) - Teefer2 Miniport
Device: \DEVICE\{47FCE59A-0DC9-4B98-A079-AECFF5DB2748}

Media State: Connected

Device State: Connected
Connect Time: 00:09:32
Media Speed: 115 Kbps

Packets Sent: 0
Bytes Sent (Optional): 0

Packets Received: 0
Directed Pkts Recd (Optional): 0
Bytes Received (Optional): 0
Directed Bytes Recd (Optional): 0

[WARNING] The net card 'Минипорт WAN (Сетевой монитор) - Teefer2 Miniport' may not be working because it has not received any packets.
---------------------------------------------------------------------------
Description: Минипорт WAN (IP) - Teefer2 Miniport
Device: \DEVICE\{51327B08-FA3F-423B-930E-C17A64D86141}

Media State: Connected

Device State: Connected
Connect Time: 00:09:32
Media Speed: 115 Kbps

Packets Sent: 0
Bytes Sent (Optional): 0

Packets Received: 0
Directed Pkts Recd (Optional): 0
Bytes Received (Optional): 0
Directed Bytes Recd (Optional): 0

[WARNING] The net card 'Минипорт WAN (IP) - Teefer2 Miniport' may not be working because it has not received any packets.
---------------------------------------------------------------------------
Description: Минипорт WAN (IPv6) - Teefer2 Miniport
Device: \DEVICE\{6AB88503-FB07-4554-8A00-5529A53DD15C}

Media State: Connected

Device State: Connected
Connect Time: 00:09:32
Media Speed: 115 Kbps

Packets Sent: 0
Bytes Sent (Optional): 0

Packets Received: 0
Directed Pkts Recd (Optional): 0
Bytes Received (Optional): 0
Directed Bytes Recd (Optional): 0

[WARNING] The net card 'Минипорт WAN (IPv6) - Teefer2 Miniport' may not be working because it has not received any packets.
---------------------------------------------------------------------------
Description: Минипорт WAN (PPTP)
Device: \DEVICE\{57B78A29-B37D-4C4E-BB9F-7CA4341A3D5E}

Media State: Connected

Device State: Connected
Connect Time: 00:00:00
Media Speed: 0 bps

Packets Sent: 0
Bytes Sent (Optional): 0

Packets Received: 0
Directed Pkts Recd (Optional): 0
Bytes Received (Optional): 0
Directed Bytes Recd (Optional): 0

[WARNING] The net card 'Минипорт WAN (PPTP)' may not be working because it has not received any packets.
---------------------------------------------------------------------------
Description: Минипорт WAN (PPPoE)
Device: \DEVICE\{26B3A979-9D29-46C7-A2BF-ED49D03898E1}

Media State: Connected

Device State: Connected
Connect Time: 00:00:00
Media Speed: 0 bps

Packets Sent: 0
Bytes Sent (Optional): 0

Packets Received: 0
Directed Pkts Recd (Optional): 0
Bytes Received (Optional): 0
Directed Bytes Recd (Optional): 0

[WARNING] The net card 'Минипорт WAN (PPPoE)' may not be working because it has not received any packets.
---------------------------------------------------------------------------
Description: Минипорт WAN (IPv6)
Device: \DEVICE\NDISWANIPV6

Media State: Connected

Device State: Connected
Connect Time: 00:09:32
Media Speed: 115 Kbps

Packets Sent: 0
Bytes Sent (Optional): 0

Packets Received: 0
Directed Pkts Recd (Optional): 0
Bytes Received (Optional): 0
Directed Bytes Recd (Optional): 0

[WARNING] The net card 'Минипорт WAN (IPv6)' may not be working because it has not received any packets.
---------------------------------------------------------------------------
Description: Минипорт WAN (IP)
Device: \DEVICE\NDISWANIP

Media State: Connected

Device State: Connected
Connect Time: 00:09:32
Media Speed: 115 Kbps

Packets Sent: 0
Bytes Sent (Optional): 0

Packets Received: 0
Directed Pkts Recd (Optional): 0
Bytes Received (Optional): 0
Directed Bytes Recd (Optional): 0

[WARNING] The net card 'Минипорт WAN (IP)' may not be working because it has not received any packets.
---------------------------------------------------------------------------
Description: Минипорт WAN (Сетевой монитор)
Device: \DEVICE\NDISWANBH

Media State: Connected

Device State: Connected
Connect Time: 00:09:32
Media Speed: 115 Kbps

Packets Sent: 0
Bytes Sent (Optional): 0

Packets Received: 0
Directed Pkts Recd (Optional): 0
Bytes Received (Optional): 0
Directed Bytes Recd (Optional): 0

[WARNING] The net card 'Минипорт WAN (Сетевой монитор)' may not be working because it has not received any packets.
---------------------------------------------------------------------------
Description: Минипорт WAN (L2TP)
Device: \DEVICE\{9C7E9359-5E4D-4116-A49D-51DA1DB18E4C}
GetStats failed for 'Минипорт WAN (L2TP)'. [ERROR_GEN_FAILURE]
---------------------------------------------------------------------------
Description: Intel(R) PRO/1000 PL Network Connection
Device: \DEVICE\{5679D40D-F3E6-4738-8B2F-73AECC65875A}

Media State: Connected

Device State: Connected
Connect Time: 00:09:32
Media Speed: 100 Mbps

Packets Sent: 2230
Bytes Sent (Optional): 344272

Packets Received: 11634
Directed Pkts Recd (Optional): 2195
Bytes Received (Optional): 577788
Directed Bytes Recd (Optional): 577788

---------------------------------------------------------------------------
Description: isatap.lvs.onpp
Device: \DEVICE\{699CF414-21C5-439E-A707-4F4879F84276}
GetStats failed for 'isatap.lvs.onpp'. [ERROR_GEN_FAILURE]
---------------------------------------------------------------------------
[PASS] - At least one netcard is in the 'Connected' state.



Per interface results:

Adapter : Подключение по локальной сети 2
Adapter ID . . . . . . . . : {5679D40D-F3E6-4738-8B2F-73AECC65875A}

Netcard queries test . . . : Passed

Adapter type . . . . . . . : Ethernet
Host Name. . . . . . . . . : SERVER-WSUS.lvs.onpp
Description. . . . . . . . : Intel(R) PRO/1000 PL Network Connection
Physical Address . . . . . : 00-30-48-93-1F-2B
Dhcp Enabled . . . . . . . : Yes
DHCP ClassID . . . . . . . :
Autoconfiguration Enabled. : Yes
IP Address . . . . . . . . : 192.168.7.116
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . : 192.168.7.5
DHCP Server. . . . . . . . : 192.168.7.8
Lease Obtained . . . . . . : 9 -®пЎап 2009 Ј. 15:07:29
Lease Expires. . . . . . . : 11 -®пЎап 2009 Ј. 15:07:29
Dns Servers. . . . . . . . : 192.168.7.10
192.168.7.8

IpConfig results . . . . . : Passed
Pinging DHCP server - reachable

AutoConfiguration results. . . . . . : Passed
AutoConfiguration is not in use.

Default gateway test . . . : Passed
Pinging gateway 192.168.7.5 - reachable
At least one gateway reachable for this adapter.

NetBT name test. . . . . . : Passed
NetBT_Tcpip_{5679D40D-F3E6-4738-8B2F-73AECC65875A}
No names have been found.

WINS service test. . . . . : Skipped
There is no primary WINS server defined for this adapter.
There is no secondary WINS server defined for this adapter.
There are no WINS servers configured for this interface.
IPX test : IPX is not installed on this machine.


Global results:


IP General configuration
LMHOSTS Enabled. . . . . . . . : Yes
DNS for WINS resolution. . . . : Enabled
Node Type. . . . . . . . . . . : Hybrid
NBT Scope ID . . . . . . . . . :
Routing Enabled. . . . . . . . : No
WINS Proxy Enabled . . . . . . : No
DNS resolution for NETBIOS . . : No



Domain membership test . . . . . . : Passed
Machine is a . . . . . . . . . : Standalone Server
Netbios Workgroup name . . . . : 123
Dns domain name is not specified.
Dns forest name is not specified.
Domain Guid. . . . . . . . . . : {00000000-0000-0000-0000-000000000000}
Logon User . . . . . . . . . . : Администратор
Logon Domain . . . . . . . . . : SERVER-WSUS


NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{5679D40D-F3E6-4738-8B2F-73AECC65875A}
1 NetBt transport currently configured.


Autonet address test . . . . . . . : Passed
PASS - you have at least one non-autoconfigured IP address


IP loopback ping test. . . . . . . : Passed
PASS - pinging IP loopback address was successful.
Your IP stack is most probably OK.


Default gateway test . . . . . . . : Passed
PASS - you have at least one reachable gateway.


NetBT name test. . . . . . . . . . : Passed
No NetBT scope defined
[WARNING] You don't have a single interface with the <00> 'WorkStation Service', <03> 'Messenger Service', <20> 'WINS' names defined.


Winsock test . . . . . . . . . . . : Passed
The number of protocols which have been reported : 8
Description: MSAFD Tcpip [TCP/IPv6]
Provider Version :2
Max message size : Stream Oriented
Description: MSAFD Tcpip [UDP/IPv6]
Provider Version :2
Description: MSAFD Tcpip [TCP/IP]
Provider Version :2
Max message size : Stream Oriented
Description: MSAFD Tcpip [UDP/IP]
Provider Version :2
Description: Поставщик услуг RSVP TCPv6
Provider Version :2
Max message size : Stream Oriented
Description: Поставщик услуг RSVP TCP
Provider Version :2
Max message size : Stream Oriented
Description: Поставщик услуг RSVP UDPv6
Provider Version :2
Description: Поставщик услуг RSVP UDP
Provider Version :2

Max UDP size : 65507 bytes


DNS test . . . . . . . . . . . . . : Passed
Interface {5679D40D-F3E6-4738-8B2F-73AECC65875A}
DNS Domain: lvs.onpp
DNS Servers: 192.168.7.10 192.168.7.8
IP Address: Expected registration with PDN (primary DNS domain name):
Hostname: SERVER-WSUS.lvs.onpp.
Authoritative zone: lvs.onpp.
Primary DNS server: server-dc1.lvs.onpp 192.168.7.10
Authoritative NS:192.168.7.10 192.168.12.10 192.168.1.10 192.168.5.10 192.168.6.10 192.168.10.10 192.168.2.10 192.168.4.10 192.168.7.9 192.168.1.9 192.168.5.9 192.168.6.9 192.168.10.9 192.168.2.9 192.168.4.9 192.168.12.9 192.168.7.8 192.168.4.8 192.168.5.8 192.168.6.8 192.168.2.8 192.168.10.8 192.168.12.8 192.168.1.8


Redir and Browser test . . . . . . : Failed
List of transports currently bound to the Redir
NetbiosSmb
NetBT_Tcpip_{5679D40D-F3E6-4738-8B2F-73AECC65875A}
The redir is bound to 1 NetBt transport.

List of transports currently bound to the browser
NetBT_Tcpip_{5679D40D-F3E6-4738-8B2F-73AECC65875A}
The browser is bound to 1 NetBt transport.
[FATAL] Cannot send mailslot message to 'SERVER-WSUS' via browser. [ERROR_INVALID_FUNCTION]


DC discovery test. . . . . . . . . : Skipped


DC list test . . . . . . . . . . . : Skipped


Trust relationship test. . . . . . : Skipped


Kerberos test. . . . . . . . . . . : Skipped


LDAP test. . . . . . . . . . . . . : Skipped


Routing table test . . . . . . . . : Passed
Active Routes :
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.7.5 192.168.7.116 20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 306
127.0.0.1 255.255.255.255 127.0.0.1 127.0.0.1 306
127.255.255.255 255.255.255.255 127.0.0.1 127.0.0.1 306
192.168.7.0 255.255.255.0 192.168.7.116 192.168.7.116 276
192.168.7.116 255.255.255.255 192.168.7.116 192.168.7.116 276
192.168.7.255 255.255.255.255 192.168.7.116 192.168.7.116 276
224.0.0.0 240.0.0.0 127.0.0.1 127.0.0.1 306
224.0.0.0 240.0.0.0 192.168.7.116 192.168.7.116 276
255.255.255.255 255.255.255.255 127.0.0.1 127.0.0.1 306
255.255.255.255 255.255.255.255 192.168.7.116 192.168.7.116 276
No persistent route entries.


Netstat information test . . . . . : Passed


Interface Statistics

Received Sent
Unicast Packets 4330242 1133814
Non-unicast packets 28290 981
Discards 3 3
Errors 0 0
Unknown protocols 0 785908

Interface index = 1
Description = Software Loopback Interface 1
Type = 24
MTU = 1500
Speed = 1073741824
Physical Address = 00-00-00-00-00-00
Administrative Status = 1
Operational Status = 1
Last Changed = 0
Output Queue Length = 0


Interface index = 2
Description = WAN Miniport (SSTP)
Type = 131
MTU = 4091
Speed = 1073741824
Physical Address = 00-00-00-00-00-00
Administrative Status = 1
Operational Status = 1
Last Changed = 0
Output Queue Length = 0


Interface index = 3
Description = ЊЁ-ЁЇ®ав WAN (L2TP)
Type = 131
MTU = 1460
Speed = 1073741824
Physical Address = 00-00-00-00-00-00
Administrative Status = 1
Operational Status = 1
Last Changed = 0
Output Queue Length = 0


Interface index = 4
Description = ЊЁ-ЁЇ®ав WAN (PPTP)
Type = 131
MTU = 1464
Speed = 1073741824
Physical Address = 50-50-54-50-30-30
Administrative Status = 1
Operational Status = 1
Last Changed = 0
Output Queue Length = 0


Interface index = 5
Description = ЊЁ-ЁЇ®ав WAN (PPPoE)
Type = 23
MTU = 1494
Speed = 1073741824
Physical Address = 33-50-6F-45-30-30
Administrative Status = 1
Operational Status = 1
Last Changed = 0
Output Queue Length = 0


Interface index = 6
Description = ЊЁ-ЁЇ®ав WAN (IPv6)
Type = 6
MTU = 1500
Speed = 115200
Physical Address = 9a-40-20-52-41-53
Administrative Status = 1
Operational Status = 1
Last Changed = 0
Output Queue Length = 0


Interface index = 7
Description = ЊЁ-ЁЇ®ав WAN (‘ҐвҐў®© ¬®-Ёв®а)
Type = 6
MTU = 1500
Speed = 115200
Physical Address = 9a-40-20-52-41-53
Administrative Status = 1
Operational Status = 1
Last Changed = 0
Output Queue Length = 0


Interface index = 8
Description = ЊЁ-ЁЇ®ав WAN (IP)
Type = 6
MTU = 1500
Speed = 115200
Physical Address = 9a-40-20-52-41-53
Administrative Status = 1
Operational Status = 1
Last Changed = 0
Output Queue Length = 0


Interface index = 9
Description = RAS  бЁ-еа®--л©  ¤ ЇвҐа
Type = 23
MTU = 3256
Speed = 28800
Physical Address = 20-41-53-59-4E-FF
Administrative Status = 1
Operational Status = 1
Last Changed = 0
Output Queue Length = 0


Interface index = 10
Description = ЊЁ-ЁЇ®ав WAN (IPv6) - Teefer2 Miniport
Type = 6
MTU = 1500
Speed = 115200
Physical Address = 9a-40-20-52-41-53
Administrative Status = 1
Operational Status = 1
Last Changed = 0
Output Queue Length = 0


Interface index = 11
Description = ЊЁ-ЁЇ®ав WAN (‘ҐвҐў®© ¬®-Ёв®а) - Teefer2 Miniport
Type = 6
MTU = 1500
Speed = 115200
Physical Address = 9a-40-20-52-41-53
Administrative Status = 1
Operational Status = 1
Last Changed = 0
Output Queue Length = 0


Interface index = 12
Description = ЊЁ-ЁЇ®ав WAN (IP) - Teefer2 Miniport
Type = 6
MTU = 1500
Speed = 115200
Physical Address = 9a-40-20-52-41-53
Administrative Status = 1
Operational Status = 1
Last Changed = 0
Output Queue Length = 0


Interface index = 13
Description = Intel(R) PRO/1000 PM Network Connection
Type = 6
MTU = 0
Speed = 0
Physical Address = 00-30-48-93-1F-2A
Administrative Status = 2
Operational Status = 6
Last Changed = 0
Output Queue Length = 0


Interface index = 14
Description = Intel(R) PRO/1000 PM Network Connection - Teefer2 Miniport
Type = 6
MTU = 0
Speed = 0
Physical Address = 00-30-48-93-1F-2A
Administrative Status = 1
Operational Status = 2
Last Changed = 0
Output Queue Length = 0


Interface index = 15
Description = Intel(R) PRO/1000 PL Network Connection
Type = 6
MTU = 1500
Speed = 100000000
Physical Address = 00-30-48-93-1F-2B
Administrative Status = 1
Operational Status = 1
Last Changed = 0
Output Queue Length = 0


Interface index = 16
Description = Intel(R) PRO/1000 PL Network Connection - Teefer2 Miniport
Type = 6
MTU = 1500
Speed = 100000000
Physical Address = 00-30-48-93-1F-2B
Administrative Status = 1
Operational Status = 1
Last Changed = 0
Output Queue Length = 0


Interface index = 20
Description = isatap.lvs.onpp
Type = 131
MTU = 1280
Speed = 100000
Physical Address = 00-00-00-00-00-00
Administrative Status = 1
Operational Status = 2
Last Changed = 0
Output Queue Length = 0


Interface index = 21
Description = ЊЁ-ЁЇ®ав WAN (IPv6)-QoS Packet Scheduler-0000
Type = 6
MTU = 1500
Speed = 115200
Physical Address = 9a-40-20-52-41-53
Administrative Status = 1
Operational Status = 1
Last Changed = 0
Output Queue Length = 0


Interface index = 22
Description = ЊЁ-ЁЇ®ав WAN (IP)-QoS Packet Scheduler-0000
Type = 6
MTU = 1500
Speed = 115200
Physical Address = 9a-40-20-52-41-53
Administrative Status = 1
Operational Status = 1
Last Changed = 0
Output Queue Length = 0


Interface index = 23
Description = ЊЁ-ЁЇ®ав WAN (‘ҐвҐў®© ¬®-Ёв®а)-QoS Packet Scheduler-0000
Type = 6
MTU = 1500
Speed = 115200
Physical Address = 9a-40-20-52-41-53
Administrative Status = 1
Operational Status = 1
Last Changed = 0
Output Queue Length = 0


Interface index = 24
Description = Intel(R) PRO/1000 PL Network Connection-QoS Packet Scheduler-0000
Type = 6
MTU = 1500
Speed = 100000000
Physical Address = 00-30-48-93-1F-2B
Administrative Status = 1
Operational Status = 1
Last Changed = 0
Output Queue Length = 0



Active Connections

Proto Local Address Foreign Address State
TCP SERVER-WSUS:epmap SERVER-WSUS.lvs.onpp:0 LISTENING
TCP SERVER-WSUS:2638 SERVER-WSUS.lvs.onpp:0 LISTENING
TCP SERVER-WSUS:ms-wbt-server SERVER-WSUS.lvs.onpp:0 LISTENING
TCP SERVER-WSUS:7070 SERVER-WSUS.lvs.onpp:0 LISTENING
TCP SERVER-WSUS:8009 SERVER-WSUS.lvs.onpp:0 LISTENING
TCP SERVER-WSUS:8443 SERVER-WSUS.lvs.onpp:0 LISTENING
TCP SERVER-WSUS:9090 SERVER-WSUS.lvs.onpp:0 LISTENING
TCP SERVER-WSUS:49152 SERVER-WSUS.lvs.onpp:0 LISTENING
TCP SERVER-WSUS:49153 SERVER-WSUS.lvs.onpp:0 LISTENING
TCP SERVER-WSUS:49154 SERVER-WSUS.lvs.onpp:0 LISTENING
TCP SERVER-WSUS:49155 SERVER-WSUS.lvs.onpp:0 LISTENING
TCP SERVER-WSUS:49157 SERVER-WSUS.lvs.onpp:0 LISTENING
TCP SERVER-WSUS:http SERVER-WSUS.lvs.onpp:49320 TIME_WAIT
TCP SERVER-WSUS:http SERVER-WSUS.lvs.onpp:49321 TIME_WAIT
TCP SERVER-WSUS:http SERVER-WSUS.lvs.onpp:49322 TIME_WAIT
TCP SERVER-WSUS:http SERVER-WSUS.lvs.onpp:49323 TIME_WAIT
TCP SERVER-WSUS:http SERVER-WSUS.lvs.onpp:49324 TIME_WAIT
TCP SERVER-WSUS:http SERVER-WSUS.lvs.onpp:49325 TIME_WAIT
TCP SERVER-WSUS:http SERVER-WSUS.lvs.onpp:49327 TIME_WAIT
TCP SERVER-WSUS:http SERVER-WSUS.lvs.onpp:49328 TIME_WAIT
TCP SERVER-WSUS:http SERVER-WSUS.lvs.onpp:49329 TIME_WAIT
TCP SERVER-WSUS:http SERVER-WSUS.lvs.onpp:49330 TIME_WAIT
TCP SERVER-WSUS:http SERVER-WSUS.lvs.onpp:49331 TIME_WAIT
TCP SERVER-WSUS:http SERVER-WSUS.lvs.onpp:49332 TIME_WAIT
TCP SERVER-WSUS:http SERVER-WSUS.lvs.onpp:49333 TIME_WAIT
TCP SERVER-WSUS:http SERVER-WSUS.lvs.onpp:49334 TIME_WAIT
TCP SERVER-WSUS:http SERVER-WSUS.lvs.onpp:49335 TIME_WAIT
TCP SERVER-WSUS:http SERVER-WSUS.lvs.onpp:49336 TIME_WAIT
TCP SERVER-WSUS:http SERVER-WSUS.lvs.onpp:49338 TIME_WAIT
TCP SERVER-WSUS:http SERVER-WSUS.lvs.onpp:49339 TIME_WAIT
TCP SERVER-WSUS:http SERVER-WSUS.lvs.onpp:49340 TIME_WAIT
TCP SERVER-WSUS:2638 SERVER-WSUS.lvs.onpp:49160 ESTABLISHED
TCP SERVER-WSUS:2638 SERVER-WSUS.lvs.onpp:49161 ESTABLISHED
TCP SERVER-WSUS:2638 SERVER-WSUS.lvs.onpp:49166 ESTABLISHED
TCP SERVER-WSUS:2638 SERVER-WSUS.lvs.onpp:49167 ESTABLISHED
TCP SERVER-WSUS:2638 SERVER-WSUS.lvs.onpp:49168 ESTABLISHED
TCP SERVER-WSUS:2638 SERVER-WSUS.lvs.onpp:49190 ESTABLISHED
TCP SERVER-WSUS:2638 SERVER-WSUS.lvs.onpp:49191 ESTABLISHED
TCP SERVER-WSUS:2638 SERVER-WSUS.lvs.onpp:49192 ESTABLISHED
TCP SERVER-WSUS:7071 SERVER-WSUS.lvs.onpp:0 LISTENING
TCP SERVER-WSUS:7072 SERVER-WSUS.lvs.onpp:0 LISTENING
TCP SERVER-WSUS:7072 SERVER-WSUS.lvs.onpp:49169 ESTABLISHED
TCP SERVER-WSUS:7072 SERVER-WSUS.lvs.onpp:49175 ESTABLISHED
TCP SERVER-WSUS:7072 SERVER-WSUS.lvs.onpp:49178 ESTABLISHED
TCP SERVER-WSUS:7072 SERVER-WSUS.lvs.onpp:49180 ESTABLISHED
TCP SERVER-WSUS:8005 SERVER-WSUS.lvs.onpp:0 LISTENING
TCP SERVER-WSUS:49160 SERVER-WSUS.lvs.onpp:2638 ESTABLISHED
TCP SERVER-WSUS:49161 SERVER-WSUS.lvs.onpp:2638 ESTABLISHED
TCP SERVER-WSUS:49166 SERVER-WSUS.lvs.onpp:2638 ESTABLISHED
TCP SERVER-WSUS:49167 SERVER-WSUS.lvs.onpp:2638 ESTABLISHED
TCP SERVER-WSUS:49168 SERVER-WSUS.lvs.onpp:2638 ESTABLISHED
TCP SERVER-WSUS:49169 SERVER-WSUS.lvs.onpp:7072 ESTABLISHED
TCP SERVER-WSUS:49175 SERVER-WSUS.lvs.onpp:7072 ESTABLISHED
TCP SERVER-WSUS:49178 SERVER-WSUS.lvs.onpp:7072 ESTABLISHED
TCP SERVER-WSUS:49180 SERVER-WSUS.lvs.onpp:7072 ESTABLISHED
TCP SERVER-WSUS:49190 SERVER-WSUS.lvs.onpp:2638 ESTABLISHED
TCP SERVER-WSUS:49191 SERVER-WSUS.lvs.onpp:2638 ESTABLISHED
TCP SERVER-WSUS:49192 SERVER-WSUS.lvs.onpp:2638 ESTABLISHED
TCP SERVER-WSUS:http server-dcad.lvs.onpp:4719 TIME_WAIT
TCP SERVER-WSUS:http server-dcad.lvs.onpp:4720 TIME_WAIT
TCP SERVER-WSUS:http server-dc1.lvs.onpp:2490 TIME_WAIT
TCP SERVER-WSUS:http server-dc1.lvs.onpp:2491 TIME_WAIT
TCP SERVER-WSUS:http lvs-o915pom.lvs.onpp:1618 TIME_WAIT
TCP SERVER-WSUS:http lvs-o915vent.lvs.onpp:1562 TIME_WAIT
TCP SERVER-WSUS:http lvs-o915ssv.lvs.onpp:2486 TIME_WAIT
TCP SERVER-WSUS:http lvs-o915graf.lvs.onpp:1444 TIME_WAIT
TCP SERVER-WSUS:http lvs-o915inn.lvs.onpp:1851 TIME_WAIT
TCP SERVER-WSUS:http lvs-o915inn.lvs.onpp:1852 TIME_WAIT
TCP SERVER-WSUS:http lvs-o915print.lvs.onpp:1576 TIME_WAIT
TCP SERVER-WSUS:http lvs-o915pln.lvs.onpp:1545 TIME_WAIT
TCP SERVER-WSUS:http lvs-o915sha.lvs.onpp:2134 TIME_WAIT
TCP SERVER-WSUS:http lvs-o915sha.lvs.onpp:2135 TIME_WAIT
TCP SERVER-WSUS:http lvs-o915vek.lvs.onpp:1568 TIME_WAIT
TCP SERVER-WSUS:http server-ugs.lvs.onpp:3366 TIME_WAIT
TCP SERVER-WSUS:http server-ugs.lvs.onpp:3367 TIME_WAIT
TCP SERVER-WSUS:http server-file.lvs.onpp:2596 TIME_WAIT
TCP SERVER-WSUS:http server-file.lvs.onpp:2597 TIME_WAIT
TCP SERVER-WSUS:http lvs-admin.lvs.onpp:3600 TIME_WAIT
TCP SERVER-WSUS:http lvs-admin.lvs.onpp:3601 TIME_WAIT
TCP SERVER-WSUS:http lvs-tehnopro.lvs.onpp:4024 TIME_WAIT
TCP SERVER-WSUS:http lvs-tehnopro.lvs.onpp:4025 TIME_WAIT
TCP SERVER-WSUS:http lvs-pravo.lvs.onpp:3089 TIME_WAIT
TCP SERVER-WSUS:http lvs-pravo.lvs.onpp:3090 TIME_WAIT
TCP SERVER-WSUS:netbios-ssn SERVER-WSUS.lvs.onpp:0 LISTENING
TCP SERVER-WSUS:49229 server-dc1.lvs.onpp:netbios-ssn ESTABLISHED
UDP SERVER-WSUS:bootpc *:*
UDP SERVER-WSUS:ntp *:*
UDP SERVER-WSUS:isakmp *:*
UDP SERVER-WSUS:syslog *:*
UDP SERVER-WSUS:radius *:*
UDP SERVER-WSUS:3702 *:*
UDP SERVER-WSUS:ipsec-msft *:*
UDP SERVER-WSUS:llmnr *:*
UDP SERVER-WSUS:55877 *:*
UDP SERVER-WSUS:64160 *:*
UDP SERVER-WSUS:tftp *:*
UDP SERVER-WSUS:53939 *:*
UDP SERVER-WSUS:55569 *:*
UDP SERVER-WSUS:60547 *:*
UDP SERVER-WSUS:tftp *:*
UDP SERVER-WSUS:netbios-ns *:*
UDP SERVER-WSUS:netbios-dgm *:*


IP Statistics

Packets Received = 11 021
Received Header Errors = 0
Received Address Errors = 519
Datagrams Forwarded = 0
Unknown Protocols Received = 0
Received Packets Discarded = 23
Received Packets Delivered = 256 837
Output Requests = 248 237
Routing Discards = 0
Discarded Output Packets = 25
Output Packet No Route = 0
Reassembly Required = 0
Reassembly Successful = 0
Reassembly Failures = 0
Datagrams successfully fragmented = 0
Datagrams failing fragmentation = 0
Fragments Created = 0
Forwarding = 2
Default TTL = 128
Reassembly timeout = 60


TCP Statistics

Active Opens = 175
Passive Opens = 282
Failed Connection Attempts = 34
Reset Connections = 23
Current Connections = 25
Received Segments = 248 120
Segment Sent = 247 887
Segment Retransmitted = 68
Retransmission Timeout Algorithm = rsre
Minimum Retransmission Timeout = 10
Maximum Retransmission Timeout = -1
Maximum Number of Connections = -1


UDP Statistics

Datagrams Received = 8 823
No Ports = 23
Receive Errors = 0
Datagrams Sent = 378


ICMP Statistics

Received Sent
Messages 70 70
Errors 0 0
Destination Unreachable 13 13
Time Exceeded 0 0
Parameter Problems 0 0
Source Quenchs 0 0
Redirects 0 0
Echos 21 21
Echo Replies 36 36
Timestamps 0 0
Timestamp Replies 0 0
Address Masks 0 0
Address Mask Replies 0 0


Bindings test. . . . . . . . . . . : Passed
Component Name : Intel(R) Advanced Network Services Protocol
Bind Name: iANSProtocol
Binding Paths:
Owner of the binding path : Intel(R) Advanced Network Services Protocol
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Intel(R) Advanced Network Services Protocol
Lower Component: Intel(R) PRO/1000 PL Network Connection

Owner of the binding path : Intel(R) Advanced Network Services Protocol
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Intel(R) Advanced Network Services Protocol
Lower Component: Intel(R) PRO/1000 PM Network Connection


Component Name : Microsoft TCP/IP version 6 - Tunnels
Bind Name: TCPIP6TUNNEL
Binding Paths:
Owner of the binding path : Microsoft TCP/IP version 6 - Tunnels
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5_ip6_tunnel
Upper Component: Microsoft TCP/IP version 6 - Tunnels
Lower Component: isatap.lvs.onpp


Component Name : Internet Protocol (TCP/IP) - Tunnels
Bind Name: TCPIPTUNNEL
Binding Paths:

Component Name : Microsoft NetbiosSmb
Bind Name: Smb
Binding Paths:
Owner of the binding path : Microsoft NetbiosSmb
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: tdi
Upper Component: Microsoft NetbiosSmb
Lower Component: Intel(R) Advanced Network Services Protocol
-Interface Name: ndis5
Upper Component: Intel(R) Advanced Network Services Protocol
Lower Component: Intel(R) PRO/1000 PL Network Connection

Owner of the binding path : Microsoft NetbiosSmb
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: tdi
Upper Component: Microsoft NetbiosSmb
Lower Component: Intel(R) Advanced Network Services Protocol
-Interface Name: ndis5
Upper Component: Intel(R) Advanced Network Services Protocol
Lower Component: Intel(R) PRO/1000 PM Network Connection

Owner of the binding path : Microsoft NetbiosSmb
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: tdi
Upper Component: Microsoft NetbiosSmb
Lower Component: Internet Protocol Version 4 (TCP/IPv4)
-Interface Name: ndis5
Upper Component: Internet Protocol Version 4 (TCP/IPv4)
Lower Component: Intel(R) PRO/1000 PL Network Connection

Owner of the binding path : Microsoft NetbiosSmb
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: tdi
Upper Component: Microsoft NetbiosSmb
Lower Component: Internet Protocol Version 4 (TCP/IPv4)
-Interface Name: ndis5
Upper Component: Internet Protocol Version 4 (TCP/IPv4)
Lower Component: Intel(R) PRO/1000 PM Network Connection

Owner of the binding path : Microsoft NetbiosSmb
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: tdi
Upper Component: Microsoft NetbiosSmb
Lower Component: Internet Protocol Version 6 (TCP/IPv6)
-Interface Name: ndis5_ip6_tunnel
Upper Component: Internet Protocol Version 6 (TCP/IPv6)
Lower Component: isatap.lvs.onpp

Owner of the binding path : Microsoft NetbiosSmb
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: tdi
Upper Component: Microsoft NetbiosSmb
Lower Component: Internet Protocol Version 6 (TCP/IPv6)
-Interface Name: ndis5
Upper Component: Internet Protocol Version 6 (TCP/IPv6)
Lower Component: Intel(R) PRO/1000 PL Network Connection

Owner of the binding path : Microsoft NetbiosSmb
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: tdi
Upper Component: Microsoft NetbiosSmb
Lower Component: Internet Protocol Version 6 (TCP/IPv6)
-Interface Name: ndis5
Upper Component: Internet Protocol Version 6 (TCP/IPv6)
Lower Component: Intel(R) PRO/1000 PM Network Connection


Component Name : Remote Access IP ARP Driver
Bind Name: Wanarp
Binding Paths:
Owner of the binding path : Remote Access IP ARP Driver
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiswanip
Upper Component: Remote Access IP ARP Driver
Lower Component: Минипорт WAN (IP)


Component Name : Message-oriented TCP/IP Protocol (SMB session)
Bind Name: NetbiosSmb
Binding Paths:

Component Name : WINS Client(TCP/IP) Protocol
Bind Name: NetBT
Binding Paths:
Owner of the binding path : WINS Client(TCP/IP) Protocol
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Intel(R) Advanced Network Services Protocol
-Interface Name: ndis5
Upper Component: Intel(R) Advanced Network Services Protocol
Lower Component: Intel(R) PRO/1000 PL Network Connection

Owner of the binding path : WINS Client(TCP/IP) Protocol
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Intel(R) Advanced Network Services Protocol
-Interface Name: ndis5
Upper Component: Intel(R) Advanced Network Services Protocol
Lower Component: Intel(R) PRO/1000 PM Network Connection

Owner of the binding path : WINS Client(TCP/IP) Protocol
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol Version 4 (TCP/IPv4)
-Interface Name: ndis5
Upper Component: Internet Protocol Version 4 (TCP/IPv4)
Lower Component: Intel(R) PRO/1000 PL Network Connection

Owner of the binding path : WINS Client(TCP/IP) Protocol
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol Version 4 (TCP/IPv4)
-Interface Name: ndis5
Upper Component: Internet Protocol Version 4 (TCP/IPv4)
Lower Component: Intel(R) PRO/1000 PM Network Connection

Owner of the binding path : WINS Client(TCP/IP) Protocol
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol Version 6 (TCP/IPv6)
-Interface Name: ndis5_ip6_tunnel
Upper Component: Internet Protocol Version 6 (TCP/IPv6)
Lower Component: isatap.lvs.onpp

Owner of the binding path : WINS Client(TCP/IP) Protocol
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol Version 6 (TCP/IPv6)
-Interface Name: ndis5
Upper Component: Internet Protocol Version 6 (TCP/IPv6)
Lower Component: Intel(R) PRO/1000 PL Network Connection

Owner of the binding path : WINS Client(TCP/IP) Protocol
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol Version 6 (TCP/IPv6)
-Interface Name: ndis5
Upper Component: Internet Protocol Version 6 (TCP/IPv6)
Lower Component: Intel(R) PRO/1000 PM Network Connection


Component Name : Internet Protocol Version 6 (TCP/IPv6)
Bind Name: Tcpip6
Binding Paths:
Owner of the binding path : Internet Protocol Version 6 (TCP/IPv6)
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5_ip6_tunnel
Upper Component: Internet Protocol Version 6 (TCP/IPv6)
Lower Component: isatap.lvs.onpp

Owner of the binding path : Internet Protocol Version 6 (TCP/IPv6)
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Internet Protocol Version 6 (TCP/IPv6)
Lower Component: Intel(R) PRO/1000 PL Network Connection

Owner of the binding path : Internet Protocol Version 6 (TCP/IPv6)
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Internet Protocol Version 6 (TCP/IPv6)
Lower Component: Intel(R) PRO/1000 PM Network Connection


Component Name : Internet Protocol Version 4 (TCP/IPv4)
Bind Name: Tcpip
Binding Paths:
Owner of the binding path : Internet Protocol Version 4 (TCP/IPv4)
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Internet Protocol Version 4 (TCP/IPv4)
Lower Component: Intel(R) PRO/1000 PL Network Connection

Owner of the binding path : Internet Protocol Version 4 (TCP/IPv4)
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Internet Protocol Version 4 (TCP/IPv4)
Lower Component: Intel(R) PRO/1000 PM Network Connection


Component Name : Remote Access IPv6 ARP Driver
Bind Name: Wanarpv6
Binding Paths:
Owner of the binding path : Remote Access IPv6 ARP Driver
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiswanipv6
Upper Component: Remote Access IPv6 ARP Driver
Lower Component: Минипорт WAN (IPv6)


Component Name : Point to Point Protocol Over Ethernet
Bind Name: RasPppoe
Binding Paths:
Owner of the binding path : Point to Point Protocol Over Ethernet
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Point to Point Protocol Over Ethernet
Lower Component: Intel(R) PRO/1000 PL Network Connection

Owner of the binding path : Point to Point Protocol Over Ethernet
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Point to Point Protocol Over Ethernet
Lower Component: Intel(R) PRO/1000 PM Network Connection


Component Name : Point to Point Tunneling Protocol
Bind Name: mspptp
Binding Paths:

Component Name : Layer 2 Tunneling Protocol
Bind Name: msl2tp
Binding Paths:

Component Name : Remote Access NDIS WAN Driver
Bind Name: NdisWan
Binding Paths:
Owner of the binding path : Remote Access NDIS WAN Driver
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiswanasync
Upper Component: Remote Access NDIS WAN Driver
Lower Component: RAS асинхронный адаптер

Owner of the binding path : Remote Access NDIS WAN Driver
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiswan
Upper Component: Remote Access NDIS WAN Driver
Lower Component: Минипорт WAN (PPPoE)

Owner of the binding path : Remote Access NDIS WAN Driver
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiswan
Upper Component: Remote Access NDIS WAN Driver
Lower Component: Минипорт WAN (PPTP)

Owner of the binding path : Remote Access NDIS WAN Driver
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiscowan
Upper Component: Remote Access NDIS WAN Driver
Lower Component: Минипорт WAN (L2TP)

Owner of the binding path : Remote Access NDIS WAN Driver
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiscowan
Upper Component: Remote Access NDIS WAN Driver
Lower Component: WAN Miniport (SSTP)


Component Name : SSTP based VPN
Bind Name: mssstp
Binding Paths:

Component Name : NDIS Usermode I/O Protocol
Bind Name: Ndisuio
Binding Paths:
Owner of the binding path : NDIS Usermode I/O Protocol
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: NDIS Usermode I/O Protocol
Lower Component: Intel(R) PRO/1000 PL Network Connection

Owner of the binding path : NDIS Usermode I/O Protocol
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: NDIS Usermode I/O Protocol
Lower Component: Intel(R) PRO/1000 PM Network Connection


Component Name : Link-Layer Topology Discovery Mapper I/O Driver
Bind Name: lltdio
Binding Paths:
Owner of the binding path : Link-Layer Topology Discovery Mapper I/O Driver
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Link-Layer Topology Discovery Mapper I/O Driver
Lower Component: Intel(R) PRO/1000 PL Network Connection

Owner of the binding path : Link-Layer Topology Discovery Mapper I/O Driver
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Link-Layer Topology Discovery Mapper I/O Driver
Lower Component: Intel(R) PRO/1000 PM Network Connection


Component Name : Link-Layer Topology Discovery Responder
Bind Name: rspndr
Binding Paths:
Owner of the binding path : Link-Layer Topology Discovery Responder
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Link-Layer Topology Discovery Responder
Lower Component: Intel(R) PRO/1000 PL Network Connection

Owner of the binding path : Link-Layer Topology Discovery Responder
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Link-Layer Topology Discovery Responder
Lower Component: Intel(R) PRO/1000 PM Network Connection


Component Name : Client for Microsoft Networks
Bind Name: LanmanWorkstation
Binding Paths:
Owner of the binding path : Client for Microsoft Networks
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: netbios_smb
Upper Component: Client for Microsoft Networks
Lower Component: Microsoft NetbiosSmb
-Interface Name: tdi
Upper Component: Microsoft NetbiosSmb
Lower Component: Intel(R) Advanced Network Services Protocol
-Interface Name: ndis5
Upper Component: Intel(R) Advanced Network Services Protocol
Lower Component: Intel(R) PRO/1000 PL Network Connection

Owner of the binding path : Client for Microsoft Networks
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: netbios_smb
Upper Component: Client for Microsoft Networks
Lower Component: Microsoft NetbiosSmb
-Interface Name: tdi
Upper Component: Microsoft NetbiosSmb
Lower Component: Intel(R) Advanced Network Services Protocol
-Interface Name: ndis5
Upper Component: Intel(R) Advanced Network Services Protocol
Lower Component: Intel(R) PRO/1000 PM Network Connection

Owner of the binding path : Client for Microsoft Networks
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios_smb
Upper Component: Client for Microsoft Networks
Lower Component: Microsoft NetbiosSmb
-Interface Name: tdi
Upper Component: Microsoft NetbiosSmb
Lower Component: Internet Protocol Version 4 (TCP/IPv4)
-Interface Name: ndis5
Upper Component: Internet Protocol Version 4 (TCP/IPv4)
Lower Component: Intel(R) PRO/1000 PL Network Connection

Owner of the binding path : Client for Microsoft Networks
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios_smb
Upper Component: Client for Microsoft Networks
Lower Component: Microsoft NetbiosSmb
-Interface Name: tdi
Upper Component: Microsoft NetbiosSmb
Lower Component: Internet Protocol Version 4 (TCP/IPv4)
-Interface Name: ndis5
Upper Component: Internet Protocol Version 4 (TCP/IPv4)
Lower Component: Intel(R) PRO/1000 PM Network Connection

Owner of the binding path : Client for Microsoft Networks
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios_smb
Upper Component: Client for Microsoft Networks
Lower Component: Microsoft NetbiosSmb
-Interface Name: tdi
Upper Component: Microsoft NetbiosSmb
Lower Component: Internet Protocol Version 6 (TCP/IPv6)
-Interface Name: ndis5_ip6_tunnel
Upper Component: Internet Protocol Version 6 (TCP/IPv6)
Lower Component: isatap.lvs.onpp

Owner of the binding path : Client for Microsoft Networks
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: netbios_smb
Upper Component: Client for Microsoft Networks
Lower Component: Microsoft NetbiosSmb
-Interface Name: tdi
Upper Component: Microsoft NetbiosSmb
Lower Component: Internet Protocol Version 6 (TCP/IPv6)
-Interface Name: ndis5
Upper Component: Internet Protocol Version 6 (TCP/IPv6)
Lower Component: Intel(R) PRO/1000 PL Network Connection

Owner of the binding path : Client for Microsoft Networks
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: netbios_smb
Upper Component: Client for Microsoft Networks
Lower Component: Microsoft NetbiosSmb
-Interface Name: tdi
Upper Component: Microsoft NetbiosSmb
Lower Component: Internet Protocol Version 6 (TCP/IPv6)
-Interface Name: ndis5
Upper Component: Internet Protocol Version 6 (TCP/IPv6)
Lower Component: Intel(R) PRO/1000 PM Network Connection

Owner of the binding path : Client for Microsoft Networks
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios_smb
Upper Component: Client for Microsoft Networks
Lower Component: Message-oriented TCP/IP Protocol (SMB session)

Owner of the binding path : Client for Microsoft Networks
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: Client for Microsoft Networks
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Intel(R) Advanced Network Services Protocol
-Interface Name: ndis5
Upper Component: Intel(R) Advanced Network Services Protocol
Lower Component: Intel(R) PRO/1000 PL Network Connection

Owner of the binding path : Client for Microsoft Networks
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: Client for Microsoft Networks
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Intel(R) Advanced Network Services Protocol
-Interface Name: ndis5
Upper Component: Intel(R) Advanced Network Services Protocol
Lower Component: Intel(R) PRO/1000 PM Network Connection

Owner of the binding path : Client for Microsoft Networks
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: Client for Microsoft Networks
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol Version 4 (TCP/IPv4)
-Interface Name: ndis5
Upper Component: Internet Protocol Version 4 (TCP/IPv4)
Lower Component: Intel(R) PRO/1000 PL Network Connection

Owner of the binding path : Client for Microsoft Networks
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: Client for Microsoft Networks
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol Version 4 (TCP/IPv4)
-Interface Name: ndis5
Upper Component: Internet Protocol Version 4 (TCP/IPv4)
Lower Component: Intel(R) PRO/1000 PM Network Connection

Owner of the binding path : Client for Microsoft Networks
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: Client for Microsoft Networks
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol Version 6 (TCP/IPv6)
-Interface Name: ndis5_ip6_tunnel
Upper Component: Internet Protocol Version 6 (TCP/IPv6)
Lower Component: isatap.lvs.onpp

Owner of the binding path : Client for Microsoft Networks
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: Client for Microsoft Networks
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol Version 6 (TCP/IPv6)
-Interface Name: ndis5
Upper Component: Internet Protocol Version 6 (TCP/IPv6)
Lower Component: Intel(R) PRO/1000 PL Network Connection

Owner of the binding path : Client for Microsoft Networks
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: Client for Microsoft Networks
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol Version 6 (TCP/IPv6)
-Interface Name: ndis5
Upper Component: Internet Protocol Version 6 (TCP/IPv6)
Lower Component: Intel(R) PRO/1000 PM Network Connection


Component Name : Symantec Endpoint Protection Firewall
Bind Name: Teefer2
Binding Paths:
Owner of the binding path : Symantec Endpoint Protection Firewall
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Symantec Endpoint Protection Firewall
Lower Component: Intel(R) PRO/1000 PL Network Connection

Owner of the binding path : Symantec Endpoint Protection Firewall
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Symantec Endpoint Protection Firewall
Lower Component: Intel(R) PRO/1000 PM Network Connection

Owner of the binding path : Symantec Endpoint Protection Firewall
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiswanip
Upper Component: Symantec Endpoint Protection Firewall
Lower Component: Минипорт WAN (IP)

Owner of the binding path : Symantec Endpoint Protection Firewall
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiswanbh
Upper Component: Symantec Endpoint Protection Firewall
Lower Component: Минипорт WAN (Сетевой монитор)

Owner of the binding path : Symantec Endpoint Protection Firewall
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiswanipv6
Upper Component: Symantec Endpoint Protection Firewall
Lower Component: Минипорт WAN (IPv6)


Component Name : QoS Packet Scheduler
Bind Name: Psched
Binding Paths:
Owner of the binding path : QoS Packet Scheduler
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: QoS Packet Scheduler
Lower Component: Intel(R) PRO/1000 PL Network Connection

Owner of the binding path : QoS Packet Scheduler
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: QoS Packet Scheduler
Lower Component: Intel(R) PRO/1000 PM Network Connection

Owner of the binding path : QoS Packet Scheduler
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiswanip
Upper Component: QoS Packet Scheduler
Lower Component: Минипорт WAN (IP)

Owner of the binding path : QoS Packet Scheduler
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiswanbh
Upper Component: QoS Packet Scheduler
Lower Component: Минипорт WAN (Сетевой монитор)

Owner of the binding path : QoS Packet Scheduler
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiswanipv6
Upper Component: QoS Packet Scheduler
Lower Component: Минипорт WAN (IPv6)


Component Name : Служба доступа к файлам и принтерам сетей Microsoft
Bind Name: LanmanServer
Binding Paths:
Owner of the binding path : Служба доступа к файлам и принтерам сетей Microsoft
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: tdi
Upper Component: Служба доступа к файлам и принтерам сетей Microsoft
Lower Component: Intel(R) Advanced Network Services Protocol
-Interface Name: ndis5
Upper Component: Intel(R) Advanced Network Services Protocol
Lower Component: Intel(R) PRO/1000 PL Network Connection

Owner of the binding path : Служба доступа к файлам и принтерам сетей Microsoft
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: tdi
Upper Component: Служба доступа к файлам и принтерам сетей Microsoft
Lower Component: Intel(R) Advanced Network Services Protocol
-Interface Name: ndis5
Upper Component: Intel(R) Advanced Network Services Protocol
Lower Component: Intel(R) PRO/1000 PM Network Connection

Owner of the binding path : Служба доступа к файлам и принтерам сетей Microsoft
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: netbios_smb
Upper Component: Служба доступа к файлам и принтерам сетей Microsoft
Lower Component: Microsoft NetbiosSmb
-Interface Name: tdi
Upper Component: Microsoft NetbiosSmb
Lower Component: Intel(R) Advanced Network Services Protocol
-Interface Name: ndis5
Upper Component: Intel(R) Advanced Network Services Protocol
Lower Component: Intel(R) PRO/1000 PL Network Connection

Owner of the binding path : Служба доступа к файлам и принтерам сетей Microsoft
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: netbios_smb
Upper Component: Служба доступа к файлам и принтерам сетей Microsoft
Lower Component: Microsoft NetbiosSmb
-Interface Name: tdi
Upper Component: Microsoft NetbiosSmb
Lower Component: Intel(R) Advanced Network Services Protocol
-Interface Name: ndis5
Upper Component: Intel(R) Advanced Network Services Protocol
Lower Component: Intel(R) PRO/1000 PM Network Connection

Owner of the binding path : Служба доступа к файлам и принтерам сетей Microsoft
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios_smb
Upper Component: Служба доступа к файлам и принтерам сетей Microsoft
Lower Component: Microsoft NetbiosSmb
-Interface Name: tdi
Upper Component: Microsoft NetbiosSmb
Lower Component: Internet Protocol Version 4 (TCP/IPv4)
-Interface Name: ndis5
Upper Component: Internet Protocol Version 4 (TCP/IPv4)
Lower Component: Intel(R) PRO/1000 PL Network Connection

Owner of the binding path : Служба доступа к файлам и принтерам сетей Microsoft
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios_smb
Upper Component: Служба доступа к файлам и принтерам сетей Microsoft
Lower Component: Microsoft NetbiosSmb
-Interface Name: tdi
Upper Component: Microsoft NetbiosSmb
Lower Component: Internet Protocol Version 4 (TCP/IPv4)
-Interface Name: ndis5
Upper Component: Internet Protocol Version 4 (TCP/IPv4)
Lower Component: Intel(R) PRO/1000 PM Network Connection

Owner of the binding path : Служба доступа к файлам и принтерам сетей Microsoft
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios_smb
Upper Component: Служба доступа к файлам и принтерам сетей Microsoft
Lower Component: Microsoft NetbiosSmb
-Interface Name: tdi
Upper Component: Microsoft NetbiosSmb
Lower Component: Internet Protocol Version 6 (TCP/IPv6)
-Interface Name: ndis5_ip6_tunnel
Upper Component: Internet Protocol Version 6 (TCP/IPv6)
Lower Component: isatap.lvs.onpp

Owner of the binding path : Служба доступа к файлам и принтерам сетей Microsoft
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: netbios_smb
Upper Component: Служба доступа к файлам и принтерам сетей Microsoft
Lower Component: Microsoft NetbiosSmb
-Interface Name: tdi
Upper Component: Microsoft NetbiosSmb
Lower Component: Internet Protocol Version 6 (TCP/IPv6)
-Interface Name: ndis5
Upper Component: Internet Protocol Version 6 (TCP/IPv6)
Lower Component: Intel(R) PRO/1000 PL Network Connection

Owner of the binding path : Служба доступа к файлам и принтерам сетей Microsoft
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: netbios_smb
Upper Component: Служба доступа к файлам и принтерам сетей Microsoft
Lower Component: Microsoft NetbiosSmb
-Interface Name: tdi
Upper Component: Microsoft NetbiosSmb
Lower Component: Internet Protocol Version 6 (TCP/IPv6)
-Interface Name: ndis5
Upper Component: Internet Protocol Version 6 (TCP/IPv6)
Lower Component: Intel(R) PRO/1000 PM Network Connection

Owner of the binding path : Служба доступа к файлам и принтерам сетей Microsoft
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: tdi
Upper Component: Служба доступа к файлам и принтерам сетей Microsoft
Lower Component: Internet Protocol Version 4 (TCP/IPv4)
-Interface Name: ndis5
Upper Component: Internet Protocol Version 4 (TCP/IPv4)
Lower Component: Intel(R) PRO/1000 PL Network Connection

Owner of the binding path : Служба доступа к файлам и принтерам сетей Microsoft
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: tdi
Upper Component: Служба доступа к файлам и принтерам сетей Microsoft
Lower Component: Internet Protocol Version 4 (TCP/IPv4)
-Interface Name: ndis5
Upper Component: Internet Protocol Version 4 (TCP/IPv4)
Lower Component: Intel(R) PRO/1000 PM Network Connection

Owner of the binding path : Служба доступа к файлам и принтерам сетей Microsoft
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: tdi
Upper Component: Служба доступа к файлам и принтерам сетей Microsoft
Lower Component: Internet Protocol Version 6 (TCP/IPv6)
-Interface Name: ndis5_ip6_tunnel
Upper Component: Internet Protocol Version 6 (TCP/IPv6)
Lower Component: isatap.lvs.onpp

Owner of the binding path : Служба доступа к файлам и принтерам сетей Microsoft
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: tdi
Upper Component: Служба доступа к файлам и принтерам сетей Microsoft
Lower Component: Internet Protocol Version 6 (TCP/IPv6)
-Interface Name: ndis5
Upper Component: Internet Protocol Version 6 (TCP/IPv6)
Lower Component: Intel(R) PRO/1000 PL Network Connection

Owner of the binding path : Служба доступа к файлам и принтерам сетей Microsoft
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: tdi
Upper Component: Служба доступа к файлам и принтерам сетей Microsoft
Lower Component: Internet Protocol Version 6 (TCP/IPv6)
-Interface Name: ndis5
Upper Component: Internet Protocol Version 6 (TCP/IPv6)
Lower Component: Intel(R) PRO/1000 PM Network Connection

Owner of the binding path : Служба доступа к файлам и принтерам сетей Microsoft
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios_smb
Upper Component: Служба доступа к файлам и принтерам сетей Microsoft
Lower Component: Message-oriented TCP/IP Protocol (SMB session)

Owner of the binding path : Служба доступа к файлам и принтерам сетей Microsoft
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: Служба доступа к файлам и принтерам сетей Microsoft
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Intel(R) Advanced Network Services Protocol
-Interface Name: ndis5
Upper Component: Intel(R) Advanced Network Services Protocol
Lower Component: Intel(R) PRO/1000 PL Network Connection

Owner of the binding path : Служба доступа к файлам и принтерам сетей Microsoft
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: Служба доступа к файлам и принтерам сетей Microsoft
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Intel(R) Advanced Network Services Protocol
-Interface Name: ndis5
Upper Component: Intel(R) Advanced Network Services Protocol
Lower Component: Intel(R) PRO/1000 PM Network Connection

Owner of the binding path : Служба доступа к файлам и принтерам сетей Microsoft
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: Служба доступа к файлам и принтерам сетей Microsoft
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol Version 4 (TCP/IPv4)
-Interface Name: ndis5
Upper Component: Internet Protocol Version 4 (TCP/IPv4)
Lower Component: Intel(R) PRO/1000 PL Network Connection

Owner of the binding path : Служба доступа к файлам и принтерам сетей Microsoft
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: Служба доступа к файлам и принтерам сетей Microsoft
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol Version 4 (TCP/IPv4)
-Interface Name: ndis5
Upper Component: Internet Protocol Version 4 (TCP/IPv4)
Lower Component: Intel(R) PRO/1000 PM Network Connection

Owner of the binding path : Служба доступа к файлам и принтерам сетей Microsoft
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: Служба доступа к файлам и принтерам сетей Microsoft
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol Version 6 (TCP/IPv6)
-Interface Name: ndis5_ip6_tunnel
Upper Component: Internet Protocol Version 6 (TCP/IPv6)
Lower Component: isatap.lvs.onpp

Owner of the binding path : Служба доступа к файлам и принтерам сетей Microsoft
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: Служба доступа к файлам и принтерам сетей Microsoft
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol Version 6 (TCP/IPv6)
-Interface Name: ndis5
Upper Component: Internet Protocol Version 6 (TCP/IPv6)
Lower Component: Intel(R) PRO/1000 PL Network Connection

Owner of the binding path : Служба доступа к файлам и принтерам сетей Microsoft
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: Служба доступа к файлам и принтерам сетей Microsoft
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol Version 6 (TCP/IPv6)
-Interface Name: ndis5
Upper Component: Internet Protocol Version 6 (TCP/IPv6)
Lower Component: Intel(R) PRO/1000 PM Network Connection


Component Name : NetBIOS Interface
Bind Name: NetBIOS
Binding Paths:
Owner of the binding path : NetBIOS Interface
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: NetBIOS Interface
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Intel(R) Advanced Network Services Protocol
-Interface Name: ndis5
Upper Component: Intel(R) Advanced Network Services Protocol
Lower Component: Intel(R) PRO/1000 PL Network Connection

Owner of the binding path : NetBIOS Interface
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: NetBIOS Interface
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Intel(R) Advanced Network Services Protocol
-Interface Name: ndis5
Upper Component: Intel(R) Advanced Network Services Protocol
Lower Component: Intel(R) PRO/1000 PM Network Connection

Owner of the binding path : NetBIOS Interface
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: NetBIOS Interface
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol Version 4 (TCP/IPv4)
-Interface Name: ndis5
Upper Component: Internet Protocol Version 4 (TCP/IPv4)
Lower Component: Intel(R) PRO/1000 PL Network Connection

Owner of the binding path : NetBIOS Interface
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: NetBIOS Interface
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol Version 4 (TCP/IPv4)
-Interface Name: ndis5
Upper Component: Internet Protocol Version 4 (TCP/IPv4)
Lower Component: Intel(R) PRO/1000 PM Network Connection

Owner of the binding path : NetBIOS Interface
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: NetBIOS Interface
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol Version 6 (TCP/IPv6)
-Interface Name: ndis5_ip6_tunnel
Upper Component: Internet Protocol Version 6 (TCP/IPv6)
Lower Component: isatap.lvs.onpp

Owner of the binding path : NetBIOS Interface
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: NetBIOS Interface
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol Version 6 (TCP/IPv6)
-Interface Name: ndis5
Upper Component: Internet Protocol Version 6 (TCP/IPv6)
Lower Component: Intel(R) PRO/1000 PL Network Connection

Owner of the binding path : NetBIOS Interface
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: NetBIOS Interface
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol Version 6 (TCP/IPv6)
-Interface Name: ndis5
Upper Component: Internet Protocol Version 6 (TCP/IPv6)
Lower Component: Intel(R) PRO/1000 PM Network Connection


Component Name : Steelhead
Bind Name: RemoteAccess
Binding Paths:

Component Name : Dial-Up Server
Bind Name: msrassrv
Binding Paths:

Component Name : Remote Access Connection Manager
Bind Name: RasMan
Binding Paths:

Component Name : isatap.lvs.onpp
Bind Name: {699CF414-21C5-439E-A707-4F4879F84276}
Binding Paths:

Component Name : Intel(R) PRO/1000 PL Network Connection
Bind Name: {5679D40D-F3E6-4738-8B2F-73AECC65875A}
Binding Paths:

Component Name : Intel(R) PRO/1000 PM Network Connection
Bind Name: {AB8267A5-FACA-44EF-A3BB-DF36DB463DBC}
Binding Paths:

Component Name : RAS асинхронный адаптер
Bind Name: {D6D34145-B91A-41F3-81AE-F9C2103FAE90}
Binding Paths:

Component Name : Минипорт WAN (IP)
Bind Name: NdisWanIp
Binding Paths:

Component Name : Минипорт WAN (Сетевой монитор)
Bind Name: NdisWanBh
Binding Paths:

Component Name : Минипорт WAN (IPv6)
Bind Name: NdisWanIpv6
Binding Paths:

Component Name : Минипорт WAN (PPPoE)
Bind Name: {26B3A979-9D29-46C7-A2BF-ED49D03898E1}
Binding Paths:

Component Name : Минипорт WAN (PPTP)
Bind Name: {57B78A29-B37D-4C4E-BB9F-7CA4341A3D5E}
Binding Paths:

Component Name : Минипорт WAN (L2TP)
Bind Name: {9C7E9359-5E4D-4116-A49D-51DA1DB18E4C}
Binding Paths:

Component Name : WAN Miniport (SSTP)
Bind Name: {E5977465-57F2-490E-988F-2CEFD5776D84}
Binding Paths:



WAN configuration test . . . . . . : Skipped
No active remote access connections.


Modem diagnostics test . . . . . . : Passed

IP Security test . . . . . . . . . : Skipped

Note: run "netsh ipsec dynamic show /?" for more detailed information


The command completed successfully

[/more]

А ДНС доступен?

да он регистрируется нормально

Прочитал весь топик ответа к сожалению не нашел. Появилась некая проблемма помогите решить. Существует простейшая одноранговая локальная сеть из 6 машин. На всех XP с разными SP-ами. Один комп не видит локальной сети а так же его не видно. Хотя с него все пингуется и даже через командную строку можно войти на другой как по имени так и по IP адресу. И еще интересное замечание. При попытке расшарить какую либо папку на больном компе выдается сообщение о том что отключена "серверная служба". Все службы включены. Вобщем не пойму что не так. Подскажите пожалуйста как быть.

Цитата:

Один комп не видит локальной сети

ну не видит значит что вообще никак нигде ничем никады
надо пологать браузинг не воркает (отобразить комы рабочей группы не показывают) - ?

Прошу прощения, но все перечитать, нет ли подсказки по решению моей проблемы очень тяжело. Я изложу ее, и если стоит (т.е. подсказку я смогу найти) , то я все прочитаю. Возможно же, что у меня нету шансов по решению своей проблемы (моего подхода)!!! Только из-за этого описываю...
Суть в чем? Есть офисная сеть, Виндовс 2003 Сервер, домен с АД (2000 и ХР - на стациях). На Складе (300 метров) - в этой сети несколько ХР/2000 станций, через радиоканал (АНТЕНЫ). Одна станция 2000 стоит в розничном магазине (назовем ее маг2000_офис).
С этой станции идет работа с 1С-системой складского учета (назовем ее 1С-офис), а также находится автономная 1С-система учета розничных продаж в магазине (назовем ее 1С-магазин).
Также в магазине 2 ХР (IP=192.168.0.2 и 192.168.0.3)= одноранговая сеть (Workgroups) /коммутатор стоит, IP=192.168.0.1 / - стоит простая сетевая система Портал розничных продаж. Между системами Портал и 1С-магазин постоянно идет обмен данными:
1) Каждая приходная накладная сначала заносится в 1С-магазин, а затем из 1С-магазин экспортируется за загрузки в систему Портал,
2) Итоги продаж в Портале по закрытию дня экспортируются для ввода в 1С-магазин
и т.п.
Я поставил на маг2000_офис вторую сетевую карту, задал IP=192.168.0.10.
С этой станции пингуются оба компа из рабочей группы, а вот доступ к расшаренным папкам на них - НЕУСТОЙЧИВ....т.е. то работает, то неработает!!!
(Гостя там включил !!!).
Могу ли я добиться такого доступа УСТОЙЧИВО? Есть ли шансы, скажем...
Помогите, пожалуйста.

Цитата:

Я поставил на маг2000_офис вторую сетевую карту, задал IP=192.168.0.10.

Так не делается. Адреса на разных сетевых интерфейсах не должны быть в одной подсети.
Если вы имеете цель повышения пропускной способности, агрегируя два сетевых интерфейса в один, то делается это не так. Почитайте здесь

У меня два компа соединённые кросовером напрямую.
После чисток от вирусов на моём пропала сеть. Контроллер в порядке, полностью всё переустановил: драйвер сетевухи, протоколы, сделал настройку сети...

Короче, когда в пуске набираю "\\имя СВОЕГО!!! компа" то он даже сам себя не нахотит, пишет: "\\comp No network provider accepted the given network path."

При этом наблюдаются следующие странности:

В свойствах компа на закладке Computer Name неактивна кнопка [Network ID], а в смене компьютерного имени не активен раздел Member of где можно задать домен либо рабочую группу. При этом рабочую группу можно задать при прогоне Network Setup Wizard.
Сетевуха Intel Pro 100 Pila

В сетевом соединении всё стандартно:
- клиент MS сетей
- служба доступа к файлам и принтерам
- протокол TCP/IP (ip авто)

И ещё, у меня Win XP Pro SP1 и я поставил три Security-патча которые описаны сдесь

На втором компе всё в порядке.


Подскажите плиз это последствия действий вируса и можно ли восстановить локалку???

Проблема решена!