where is netdiag for 2008?

does anyone know where is netdiag for windows server 2008? i've looked up and
down the interent and i cant find anything. tried installing the windows 2003
support tools sp2 verison and it told me it wasnt compatible.
also is there a 2008 support forum like this one.?

--
ulyses96

"ulyses_96" <> wrote in message
news:0D06AE74-287F-4C27-A2F0-...
> does anyone know where is netdiag for windows server 2008? i've looked up
> and
> down the interent and i cant find anything. tried installing the windows
> 2003
> support tools sp2 verison and it told me it wasnt compatible.
> also is there a 2008 support forum like this one.?

NetDiag is apparently deprecated in Windows 2008 or just doesn't
work. (I cannot imagine why this would be unless there is some
newer or better tool.)

DCDiag is built in if the server is a DC.

This is the Windows Server general support for (at least) Windows
2003 and 2008 (maybe 2000 too although there were older 2000
groups).

Hopefully the MS newsgroup admins will get away from version
specific names on newsgroups -- they are generally not that useful
-- unless there is some overwhelming reason in a particular instance
and/or a major departure in the product.

2000-2008 Server should all be in the same group for most subsystems
anyway, although 2000 has it's own set of groups.

Vista probably deserves a group (at least one) separate from XP.

I too am interested to hear about Netdiag or alternatives in 2008.

FWIW: You might try to GUI/icon Network repair button in the
tool tray if you just have a problem -- it is loosely similar to
NetDiag /fix.

Apparently netdiag is not supplied with or supported in Server 2008 or
Vista.

http://forums.microsoft.com/TechNet/...7997&SiteID=17

"Herb Martin" <> wrote in message
news:...
>
> "ulyses_96" <> wrote in message
> news:0D06AE74-287F-4C27-A2F0-...
>> does anyone know where is netdiag for windows server 2008? i've looked up
>> and
>> down the interent and i cant find anything. tried installing the windows
>> 2003
>> support tools sp2 verison and it told me it wasnt compatible.
>> also is there a 2008 support forum like this one.?
>
> NetDiag is apparently deprecated in Windows 2008 or just doesn't
> work. (I cannot imagine why this would be unless there is some
> newer or better tool.)
>
> DCDiag is built in if the server is a DC.
>
> This is the Windows Server general support for (at least) Windows
> 2003 and 2008 (maybe 2000 too although there were older 2000
> groups).
>
> Hopefully the MS newsgroup admins will get away from version
> specific names on newsgroups -- they are generally not that useful
> -- unless there is some overwhelming reason in a particular instance
> and/or a major departure in the product.
>
> 2000-2008 Server should all be in the same group for most subsystems
> anyway, although 2000 has it's own set of groups.
>
> Vista probably deserves a group (at least one) separate from XP.
>
> I too am interested to hear about Netdiag or alternatives in 2008.
>
> FWIW: You might try to GUI/icon Network repair button in the
> tool tray if you just have a problem -- it is loosely similar to
> NetDiag /fix.
>
>
>

htanks for the reply !
--
ulyses96


"Bill Grant" wrote:

> Apparently netdiag is not supplied with or supported in Server 2008 or
> Vista.
>
> http://forums.microsoft.com/TechNet/...7997&SiteID=17
>
> "Herb Martin" <> wrote in message
> news:...
> >
> > "ulyses_96" <> wrote in message
> > news:0D06AE74-287F-4C27-A2F0-...
> >> does anyone know where is netdiag for windows server 2008? i've looked up
> >> and
> >> down the interent and i cant find anything. tried installing the windows
> >> 2003
> >> support tools sp2 verison and it told me it wasnt compatible.
> >> also is there a 2008 support forum like this one.?
> >
> > NetDiag is apparently deprecated in Windows 2008 or just doesn't
> > work. (I cannot imagine why this would be unless there is some
> > newer or better tool.)
> >
> > DCDiag is built in if the server is a DC.
> >
> > This is the Windows Server general support for (at least) Windows
> > 2003 and 2008 (maybe 2000 too although there were older 2000
> > groups).
> >
> > Hopefully the MS newsgroup admins will get away from version
> > specific names on newsgroups -- they are generally not that useful
> > -- unless there is some overwhelming reason in a particular instance
> > and/or a major departure in the product.
> >
> > 2000-2008 Server should all be in the same group for most subsystems
> > anyway, although 2000 has it's own set of groups.
> >
> > Vista probably deserves a group (at least one) separate from XP.
> >
> > I too am interested to hear about Netdiag or alternatives in 2008.
> >
> > FWIW: You might try to GUI/icon Network repair button in the
> > tool tray if you just have a problem -- it is loosely similar to
> > NetDiag /fix.
> >
> >
> >
>
>

thanks for the reply!
--
ulyses96


"Herb Martin" wrote:

>
> "ulyses_96" <> wrote in message
> news:0D06AE74-287F-4C27-A2F0-...
> > does anyone know where is netdiag for windows server 2008? i've looked up
> > and
> > down the interent and i cant find anything. tried installing the windows
> > 2003
> > support tools sp2 verison and it told me it wasnt compatible.
> > also is there a 2008 support forum like this one.?
>
> NetDiag is apparently deprecated in Windows 2008 or just doesn't
> work. (I cannot imagine why this would be unless there is some
> newer or better tool.)
>
> DCDiag is built in if the server is a DC.
>
> This is the Windows Server general support for (at least) Windows
> 2003 and 2008 (maybe 2000 too although there were older 2000
> groups).
>
> Hopefully the MS newsgroup admins will get away from version
> specific names on newsgroups -- they are generally not that useful
> -- unless there is some overwhelming reason in a particular instance
> and/or a major departure in the product.
>
> 2000-2008 Server should all be in the same group for most subsystems
> anyway, although 2000 has it's own set of groups.
>
> Vista probably deserves a group (at least one) separate from XP.
>
> I too am interested to hear about Netdiag or alternatives in 2008.
>
> FWIW: You might try to GUI/icon Network repair button in the
> tool tray if you just have a problem -- it is loosely similar to
> NetDiag /fix.
>
>
>
>

"ulyses_96" <> wrote in message
news:2BB593E4-B77C-463C-B981-...
> thanks for the reply!

Sure but...

Well, I was hoping for someone to tell us about a good alternative.

Hello ulyses_96,

If you do an inplace upgrade form 2003 with support tools installed before,
it will be also there in 2008 and works like before. Additional just extract
it from 2003 support tools and copy it to 2008 and it will work also. Did
it both ways for testing and works without any problem.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> does anyone know where is netdiag for windows server 2008? i've looked
> up and down the interent and i cant find anything. tried installing
> the windows 2003 support tools sp2 verison and it told me it wasnt
> compatible. also is there a 2008 support forum like this one.?
>

"Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
news: .com...
> Hello ulyses_96,
>
> If you do an inplace upgrade form 2003 with support tools installed
> before, it will be also there in 2008 and works like before. Additional
> just extract it from 2003 support tools and copy it to 2008 and it will
> work also. Did it both ways for testing and works without any problem.
>
> Best regards
>
> Meinolf Weber

I heard and thought ulyses said, that the 2003 version gives errors when
run.

Does it really work?


> Disclaimer: This posting is provided "AS IS" with no warranties, and
> confers no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
>> does anyone know where is netdiag for windows server 2008? i've looked
>> up and down the interent and i cant find anything. tried installing
>> the windows 2003 support tools sp2 verison and it told me it wasnt
>> compatible. also is there a 2008 support forum like this one.?
>>
>
>

Hello Herb,

Here an output from member server 2008:
Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\Administrator>netdiag

..............................

Computer Name: SERVER2008
DNS Host Name: Server2008
System info : Windows Server (R) 2008 Enterprise (Build 6001)
Processor : x86 Family 6 Model 15 Stepping 6, GenuineIntel
Hotfixes : none detected


Netcard queries test . . . . . . . : Passed
[WARNING] The net card 'RAS Async Adapter' may not be working because
it has
not received any packets.
GetStats failed for 'isatap.{102636F6-4122-4FFD-859C-6F22D0FEA246}'.
[ERROR_
GEN_FAILURE]



Per interface results:

Adapter : Local Area Connection

Netcard queries test . . . : Passed

Host Name. . . . . . . . . : Server2008
IP Address . . . . . . . . : 10.90.3.42
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . : 10.90.3.1
Dns Servers. . . . . . . . : 10.90.3.1


AutoConfiguration results. . . . . . : Passed

Default gateway test . . . : Passed

NetBT name test. . . . . . : Passed
[WARNING] At least one of the <00> 'WorkStation Service', <03> 'Messenge
r Service', <20> 'WINS' names is missing.
No remote names have been found.

WINS service test. . . . . : Skipped
There are no WINS servers configured for this interface.


Global results:


Domain membership test . . . . . . : Passed
Dns domain name is not specified.
Dns forest name is not specified.


NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{102636F6-4122-4FFD-859C-6F22D0FEA246}
1 NetBt transport currently configured.


Autonet address test . . . . . . . : Passed


IP loopback ping test. . . . . . . : Passed


Default gateway test . . . . . . . : Passed


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


Winsock test . . . . . . . . . . . : Passed


DNS test . . . . . . . . . . . . . : Passed


Redir and Browser test . . . . . . : Passed
List of NetBt transports currently bound to the Redir
NetBT_Tcpip_{102636F6-4122-4FFD-859C-6F22D0FEA246}
The redir is bound to 1 NetBt transport.

List of NetBt transports currently bound to the browser
NetBT_Tcpip_{102636F6-4122-4FFD-859C-6F22D0FEA246}
The browser is bound to 1 NetBt transport.


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


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


Trust relationship test. . . . . . : Skipped


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


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


Bindings test. . . . . . . . . . . : Passed


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

C:\Users\Administrator>

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
> news: .com...
>
>> Hello ulyses_96,
>>
>> If you do an inplace upgrade form 2003 with support tools installed
>> before, it will be also there in 2008 and works like before.
>> Additional just extract it from 2003 support tools and copy it to
>> 2008 and it will work also. Did it both ways for testing and works
>> without any problem.
>>
>> Best regards
>>
>> Meinolf Weber
>>
> I heard and thought ulyses said, that the 2003 version gives errors
> when run.
>
> Does it really work?
>
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers no rights.
>> ** Please do NOT email, only reply to Newsgroups
>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>> does anyone know where is netdiag for windows server 2008? i've
>>> looked up and down the interent and i cant find anything. tried
>>> installing the windows 2003 support tools sp2 verison and it told me
>>> it wasnt compatible. also is there a 2008 support forum like this
>>> one.?
>>>

Hello Herb,

Even it is really big, netdiag /v from the 2008 member server:

Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\Administrator>netdiag /v

Gathering IPX configuration information.
Querying status of the Netcard drivers... 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
Local Area Connection
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... Passed
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: SERVER2008
DNS Host Name: Server2008
DNS Domain Name: (null)
System info : Windows Server (R) 2008 Enterprise (Build 6001)
Processor : x86 Family 6 Model 15 Stepping 6, GenuineIntel
Hotfixes : none detected


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

Information of Netcard drivers:

---------------------------------------------------------------------------
Description: RAS Async Adapter
Device: \DEVICE\{A88743F6-C3B1-46E7-A73F-9A2B67BED8BC}

Media State: Connected

Device State: Connected
Connect Time: 00:12:26
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 Async Adapter' may not be working because
it has
not received any packets.
---------------------------------------------------------------------------
Description: Intel 21140-Based PCI Fast Ethernet Adapter (Emulated)
Device: \DEVICE\{102636F6-4122-4FFD-859C-6F22D0FEA246}

Media State: Connected

Device State: Connected
Connect Time: 00:14:28
Media Speed: 100 Mbps

Packets Sent: 794
Bytes Sent (Optional): 225684

Packets Received: 2353
Directed Pkts Recd (Optional): 2174
Bytes Received (Optional): 518850
Directed Bytes Recd (Optional): 518850

---------------------------------------------------------------------------
Description: Teredo Tunneling Pseudo-Interface
Device: \DEVICE\{BC16F2BF-ABB8-4571-91B3-852B61FAB16A}

Media State: Connected

Device State: Connected
Connect Time: 00:14:30
Media Speed: 10 Mbps

Packets Sent: 15
Bytes Sent (Optional): 1132

Packets Received: 3
Directed Pkts Recd (Optional): 3
Bytes Received (Optional): 456
Directed Bytes Recd (Optional): 456

---------------------------------------------------------------------------
Description: isatap.{102636F6-4122-4FFD-859C-6F22D0FEA246}
Device: \DEVICE\{8A594E27-196C-4587-9A5E-713D464949C4}
GetStats failed for 'isatap.{102636F6-4122-4FFD-859C-6F22D0FEA246}'.
[ERROR_
GEN_FAILURE]
---------------------------------------------------------------------------
[PASS] - At least one netcard is in the 'Connected' state.



Per interface results:

Adapter : Local Area Connection
Adapter ID . . . . . . . . : {102636F6-4122-4FFD-859C-6F22D0FEA246}

Netcard queries test . . . : Passed

Adapter type . . . . . . . : Ethernet
Host Name. . . . . . . . . : Server2008
Description. . . . . . . . : Intel 21140-Based PCI Fast Ethernet
Adapter
(Emulated)
Physical Address . . . . . : 00-03-FF-F6-0F-51
Dhcp Enabled . . . . . . . : No
DHCP ClassID . . . . . . . :
Autoconfiguration Enabled. : Yes
IP Address . . . . . . . . : 10.90.3.42
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . : 10.90.3.1
Dns Servers. . . . . . . . : 10.90.3.1

IpConfig results . . . . . : Passed

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

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

NetBT name test. . . . . . : Passed
NetBT_Tcpip_{102636F6-4122-4FFD-859C-6F22D0FEA246}
SERVER2008 <00> UNIQUE REGISTERED
WORKGROUP <00> GROUP REGISTERED
SERVER2008 <20> UNIQUE REGISTERED
[WARNING] At least one of the <00> 'WorkStation Service', <03> 'Messenge
r Service', <20> 'WINS' names is missing.

NetBios Resolution : via DHCP

No remote 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 . . . . : WORKGROUP
Dns domain name is not specified.
Dns forest name is not specified.
Domain Guid. . . . . . . . . . : {00000000-0000-0000-0000-000000000000}
Logon User . . . . . . . . . . : Administrator
Logon Domain . . . . . . . . . : SERVER2008


NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{102636F6-4122-4FFD-859C-6F22D0FEA246}
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
Servi
ce', <03> 'Messenger Service', <20> 'WINS' names defined.


Winsock test . . . . . . . . . . . : Passed
The number of protocols which have been reported : 16
Description: MSAFD Tcpip [TCP/IP]
Provider Version :2
Max message size : Stream Oriented
Description: MSAFD Tcpip [UDP/IP]
Provider Version :2
Description: MSAFD Tcpip [TCP/IPv6]
Provider Version :2
Max message size : Stream Oriented
Description: MSAFD Tcpip [UDP/IPv6]
Provider Version :2
Description: RSVP TCPv6 Service Provider
Provider Version :2
Max message size : Stream Oriented
Description: RSVP TCP Service Provider
Provider Version :2
Max message size : Stream Oriented
Description: RSVP UDPv6 Service Provider
Provider Version :2
Description: RSVP UDP Service Provider
Provider Version :2
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{102636F6-4122-4FFD-859C
-6F22D0FEA246}] SEQPACKET 6
Provider Version :2
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{102636F6-4122-4FFD-859C
-6F22D0FEA246}] DATAGRAM 6
Provider Version :2
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip6_{8A594E27-196C-4587-9A5
E-713D464949C4}] SEQPACKET 0
Provider Version :2
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip6_{8A594E27-196C-4587-9A5
E-713D464949C4}] DATAGRAM 0
Provider Version :2
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip6_{BC16F2BF-ABB8-4571-91B
3-852B61FAB16A}] SEQPACKET 1
Provider Version :2
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip6_{BC16F2BF-ABB8-4571-91B
3-852B61FAB16A}] DATAGRAM 1
Provider Version :2
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip6_{102636F6-4122-4FFD-859
C-6F22D0FEA246}] SEQPACKET 7
Provider Version :2
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip6_{102636F6-4122-4FFD-859
C-6F22D0FEA246}] DATAGRAM 7
Provider Version :2

Max UDP size : 65507 bytes


DNS test . . . . . . . . . . . . . : Passed
Interface {102636F6-4122-4FFD-859C-6F22D0FEA246}
DNS Domain:
DNS Servers: 10.90.3.1
IP Address: Interface {BC16F2BF-ABB8-4571-91B3-852B61FAB16A}
DNS Domain:
DNS Servers:
IP Address:

Redir and Browser test . . . . . . : Passed
List of transports currently bound to the Redir
NetbiosSmb
NetBT_Tcpip_{102636F6-4122-4FFD-859C-6F22D0FEA246}
The redir is bound to 1 NetBt transport.

List of transports currently bound to the browser
NetBT_Tcpip_{102636F6-4122-4FFD-859C-6F22D0FEA246}
The browser is bound to 1 NetBt transport.


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 10.90.3.1 10.90.3.42
276
10.90.3.0 255.255.255.0 10.90.3.42 10.90.3.42
276
10.90.3.42 255.255.255.255 10.90.3.42 10.90.3.42
276
10.90.3.255 255.255.255.255 10.90.3.42 10.90.3.42
276
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
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 10.90.3.42 10.90.3.42
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 10.90.3.42 10.90.3.42
276

Persistent Route Entries:
0.0.0.0 0.0.0.0 10.90.3.1 0
9999


Netstat information test . . . . . : Passed


Interface Statistics

Received Sent
Unicast Packets 1068016 466140
Non-unicast packets 358 148
Discards 0 0
Errors 0 0
Unknown protocols 0 458228

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 Miniport (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 Miniport (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 Miniport (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 Miniport (IPv6)
Type = 6
MTU = 1500
Speed = 1073741824
Physical Address = 94-2D-20-52-41-53
Administrative Status = 1
Operational Status = 1
Last Changed = 0
Output Queue Length = 0


Interface index = 7
Description = WAN Miniport (Network Monitor)
Type = 6
MTU = 1500
Speed = 1073741824
Physical Address = 92-1E-20-52-41-53
Administrative Status = 1
Operational Status = 1
Last Changed = 0
Output Queue Length = 0


Interface index = 8
Description = WAN Miniport (IP)
Type = 6
MTU = 1500
Speed = 1073741824
Physical Address = 92-96-20-52-41-53
Administrative Status = 1
Operational Status = 1
Last Changed = 0
Output Queue Length = 0


Interface index = 9
Description = RAS Async Adapter
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 = Intel 21140-Based PCI Fast Ethernet Adapter
(Emul
ated)
Type = 6
MTU = 1500
Speed = 100000000
Physical Address = 00-03-FF-F6-0F-51
Administrative Status = 1
Operational Status = 1
Last Changed = 0
Output Queue Length = 0


Interface index = 11
Description = Teredo Tunneling Pseudo-Interface
Type = 131
MTU = 1500
Speed = 10000000
Physical Address = 02-00-54-55-4E-01
Administrative Status = 1
Operational Status = 1
Last Changed = 0
Output Queue Length = 0


Interface index = 12
Description = isatap.{102636F6-4122-4FFD-859C-6F22D0FEA246}
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 = 13
Description = WAN Miniport (IPv6)-QoS Packet Scheduler-0000
Type = 6
MTU = 1500
Speed = 1073741824
Physical Address = 94-2D-20-52-41-53
Administrative Status = 1
Operational Status = 1
Last Changed = 0
Output Queue Length = 0


Interface index = 14
Description = WAN Miniport (IP)-QoS Packet Scheduler-0000
Type = 6
MTU = 1500
Speed = 1073741824
Physical Address = 92-96-20-52-41-53
Administrative Status = 1
Operational Status = 1
Last Changed = 0
Output Queue Length = 0


Interface index = 15
Description = WAN Miniport (Network Monitor)-QoS Packet
Schedul
er-0000
Type = 6
MTU = 1500
Speed = 1073741824
Physical Address = 92-1E-20-52-41-53
Administrative Status = 1
Operational Status = 1
Last Changed = 0
Output Queue Length = 0


Interface index = 16
Description = Intel 21140-Based PCI Fast Ethernet Adapter
(Emul
ated)-QoS Packet Scheduler-0000
Type = 6
MTU = 1500
Speed = 100000000
Physical Address = 00-03-FF-F6-0F-51
Administrative Status = 1
Operational Status = 1
Last Changed = 0
Output Queue Length = 0



Active Connections

Proto Local Address Foreign Address State
TCP Server2008:epmap Server2008:0
LISTEN
ING
TCP Server2008:ms-wbt-server Server2008:0
LI
STENING
TCP Server2008:49152 Server2008:0
LISTEN
ING
TCP Server2008:49153 Server2008:0
LISTEN
ING
TCP Server2008:49154 Server2008:0
LISTEN
ING
TCP Server2008:49155 Server2008:0
LISTEN
ING
TCP Server2008:49156 Server2008:0
LISTEN
ING
TCP Server2008:netbios-ssn Server2008:0
LIST
ENING
TCP Server2008:microsoft-ds PC2007:50772
EST
ABLISHED
UDP Server2008:ntp *:*
UDP Server2008:isakmp *:*
UDP Server2008:ipsec-msft *:*
UDP Server2008:llmnr *:*
UDP Server2008:netbios-ns *:*
UDP Server2008:netbios-dgm *:*


IP Statistics

Packets Received = 2,304
Received Header Errors = 0
Received Address Errors = 1,405
Datagrams Forwarded = 0
Unknown Protocols Received = 0
Received Packets Discarded = 83
Received Packets Delivered = 1,000
Output Requests = 829
Routing Discards = 0
Discarded Output Packets = 0
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 = 3
Passive Opens = 33
Failed Connection Attempts = 0
Reset Connections = 35
Current Connections = 1
Received Segments = 723
Segment Sent = 695
Segment Retransmitted = 0
Retransmission Timeout Algorithm = rsre
Minimum Retransmission Timeout = 10
Maximum Retransmission Timeout = -1
Maximum Number of Connections = -1


UDP Statistics

Datagrams Received = 125
No Ports = 0
Receive Errors = 83
Datagrams Sent = 78


ICMP Statistics

Received Sent
Messages 48 48
Errors 0 0
Destination Unreachable 0 0
Time Exceeded 0 0
Parameter Problems 0 0
Source Quenchs 0 0
Redirects 0 0
Echos 16 16
Echo Replies 32 32
Timestamps 0 0
Timestamp Replies 0 0
Address Masks 0 0
Address Mask Replies 0 0


Bindings test. . . . . . . . . . . : Passed
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.{102636F6-4122-4FFD-859C-6F22D0FEA246}

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: Teredo Tunneling Pseudo-Interface


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: 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 21140-Based PCI Fast Ethernet Adapter
(Emulat
ed)

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.{102636F6-4122-4FFD-859C-6F22D0FEA246}

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: Teredo Tunneling Pseudo-Interface

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 21140-Based PCI Fast Ethernet Adapter
(Emulat
ed)


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 Miniport (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: 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 21140-Based PCI Fast Ethernet Adapter
(Emulat
ed)

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.{102636F6-4122-4FFD-859C-6F22D0FEA246}

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: Teredo Tunneling Pseudo-Interface

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 21140-Based PCI Fast Ethernet Adapter
(Emulat
ed)


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.{102636F6-4122-4FFD-859C-6F22D0FEA246}

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: Teredo Tunneling Pseudo-Interface

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 21140-Based PCI Fast Ethernet Adapter
(Emulat
ed)


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 21140-Based PCI Fast Ethernet Adapter
(Emulat
ed)


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 Miniport (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 21140-Based PCI Fast Ethernet Adapter
(Emulat
ed)


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 Async Adapter

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 Miniport (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 Miniport (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 Miniport (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 21140-Based PCI Fast Ethernet Adapter
(Emulat
ed)


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 Dri
ver
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Link-Layer Topology Discovery Mapper I/O Driver
Lower Component: Intel 21140-Based PCI Fast Ethernet Adapter
(Emulat
ed)


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 21140-Based PCI Fast Ethernet Adapter
(Emulat
ed)


Component Name : Client for Microsoft Networks
Bind Name: LanmanWorkstation
Binding Paths:
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 21140-Based PCI Fast Ethernet Adapter
(Emulat
ed)

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.{102636F6-4122-4FFD-859C-6F22D0FEA246}

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: Teredo Tunneling Pseudo-Interface

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 21140-Based PCI Fast Ethernet Adapter
(Emulat
ed)

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: 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 21140-Based PCI Fast Ethernet Adapter
(Emulat
ed)

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.{102636F6-4122-4FFD-859C-6F22D0FEA246}

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: Teredo Tunneling Pseudo-Interface

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 21140-Based PCI Fast Ethernet Adapter
(Emulat
ed)


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 21140-Based PCI Fast Ethernet Adapter
(Emulat
ed)

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 Miniport (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 Miniport (Network Monitor)

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 Miniport (IPv6)


Component Name : File and Printer Sharing for Microsoft Networks
Bind Name: LanmanServer
Binding Paths:
Owner of the binding path : File and Printer Sharing for Microsoft
Netwo
rks
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios_smb
Upper Component: File and Printer Sharing 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 21140-Based PCI Fast Ethernet Adapter
(Emulat
ed)

Owner of the binding path : File and Printer Sharing for Microsoft
Netwo
rks
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios_smb
Upper Component: File and Printer Sharing 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.{102636F6-4122-4FFD-859C-6F22D0FEA246}

Owner of the binding path : File and Printer Sharing for Microsoft
Netwo
rks
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios_smb
Upper Component: File and Printer Sharing 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: Teredo Tunneling Pseudo-Interface

Owner of the binding path : File and Printer Sharing for Microsoft
Netwo
rks
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: netbios_smb
Upper Component: File and Printer Sharing 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 21140-Based PCI Fast Ethernet Adapter
(Emulat
ed)

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

Owner of the binding path : File and Printer Sharing for Microsoft
Netwo
rks
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: tdi
Upper Component: File and Printer Sharing for Microsoft Networks
Lower Component: Internet Protocol Version 6 (TCP/IPv6)
-Interface Name: ndis5_ip6_tunnel
Upper Component: Internet Protocol Version 6 (TCP/IPv6)
Lower Component: isatap.{102636F6-4122-4FFD-859C-6F22D0FEA246}

Owner of the binding path : File and Printer Sharing for Microsoft
Netwo
rks
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: tdi
Upper Component: File and Printer Sharing for Microsoft Networks
Lower Component: Internet Protocol Version 6 (TCP/IPv6)
-Interface Name: ndis5_ip6_tunnel
Upper Component: Internet Protocol Version 6 (TCP/IPv6)
Lower Component: Teredo Tunneling Pseudo-Interface

Owner of the binding path : File and Printer Sharing for Microsoft
Netwo
rks
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: tdi
Upper Component: File and Printer Sharing for Microsoft Networks
Lower Component: Internet Protocol Version 6 (TCP/IPv6)
-Interface Name: ndis5
Upper Component: Internet Protocol Version 6 (TCP/IPv6)
Lower Component: Intel 21140-Based PCI Fast Ethernet Adapter
(Emulat
ed)

Owner of the binding path : File and Printer Sharing for Microsoft
Netwo
rks
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: tdi
Upper Component: File and Printer Sharing for Microsoft Networks
Lower Component: Internet Protocol Version 4 (TCP/IPv4)
-Interface Name: ndis5
Upper Component: Internet Protocol Version 4 (TCP/IPv4)
Lower Component: Intel 21140-Based PCI Fast Ethernet Adapter
(Emulat
ed)

Owner of the binding path : File and Printer Sharing for Microsoft
Netwo
rks
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: File and Printer Sharing 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 21140-Based PCI Fast Ethernet Adapter
(Emulat
ed)

Owner of the binding path : File and Printer Sharing for Microsoft
Netwo
rks
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: File and Printer Sharing 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.{102636F6-4122-4FFD-859C-6F22D0FEA246}

Owner of the binding path : File and Printer Sharing for Microsoft
Netwo
rks
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: File and Printer Sharing 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: Teredo Tunneling Pseudo-Interface

Owner of the binding path : File and Printer Sharing for Microsoft
Netwo
rks
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: File and Printer Sharing 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 21140-Based PCI Fast Ethernet Adapter
(Emulat
ed)


Component Name : NetBIOS Interface
Bind Name: NetBIOS
Binding Paths:
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 21140-Based PCI Fast Ethernet Adapter
(Emulat
ed)

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.{102636F6-4122-4FFD-859C-6F22D0FEA246}

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: Teredo Tunneling Pseudo-Interface

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 21140-Based PCI Fast Ethernet Adapter
(Emulat
ed)


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.{102636F6-4122-4FFD-859C-6F22D0FEA246}
Bind Name: {8A594E27-196C-4587-9A5E-713D464949C4}
Binding Paths:

Component Name : Teredo Tunneling Pseudo-Interface
Bind Name: {BC16F2BF-ABB8-4571-91B3-852B61FAB16A}
Binding Paths:

Component Name : Intel 21140-Based PCI Fast Ethernet Adapter (Emulated)
Bind Name: {102636F6-4122-4FFD-859C-6F22D0FEA246}
Binding Paths:

Component Name : RAS Async Adapter
Bind Name: {A88743F6-C3B1-46E7-A73F-9A2B67BED8BC}
Binding Paths:

Component Name : WAN Miniport (IP)
Bind Name: NdisWanIp
Binding Paths:

Component Name : WAN Miniport (Network Monitor)
Bind Name: NdisWanBh
Binding Paths:

Component Name : WAN Miniport (IPv6)
Bind Name: NdisWanIpv6
Binding Paths:

Component Name : WAN Miniport (PPPOE)
Bind Name: {03AD1C25-1A7E-4F8D-8EF9-46ABAE73F7B6}
Binding Paths:

Component Name : WAN Miniport (PPTP)
Bind Name: {873B2A21-ACBB-40E6-897C-974CCC6492BB}
Binding Paths:

Component Name : WAN Miniport (L2TP)
Bind Name: {DD01BE79-9871-43DD-A2A5-183E1FE4CAFA}
Binding Paths:

Component Name : WAN Miniport (SSTP)
Bind Name: {234D5567-6582-463C-B5DC-1EB2CCE8981D}
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

C:\Users\Administrator>

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
> news: .com...
>
>> Hello ulyses_96,
>>
>> If you do an inplace upgrade form 2003 with support tools installed
>> before, it will be also there in 2008 and works like before.
>> Additional just extract it from 2003 support tools and copy it to
>> 2008 and it will work also. Did it both ways for testing and works
>> without any problem.
>>
>> Best regards
>>
>> Meinolf Weber
>>
> I heard and thought ulyses said, that the 2003 version gives errors
> when run.
>
> Does it really work?
>
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers no rights.
>> ** Please do NOT email, only reply to Newsgroups
>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>> does anyone know where is netdiag for windows server 2008? i've
>>> looked up and down the interent and i cant find anything. tried
>>> installing the windows 2003 support tools sp2 verison and it told me
>>> it wasnt compatible. also is there a 2008 support forum like this
>>> one.?
>>>