DCOM Test

I need to test DCOM communication between 2 Windows 2003 Servers, as I
believe I have a problem with it.

Does anyone have a utility/tool/method of checking DCOM client/server on
Windows Server 2003? I have a MS util for Win2K/NT server, but it's no good
on 2k3.

Thanks.

In news:98143969-B3BF-4AF1-93B2-(E-Mail Removed),
The Vogon <(E-Mail Removed)> stated, which I commented on
below:
> I need to test DCOM communication between 2 Windows 2003 Servers, as I
> believe I have a problem with it.
>
> Does anyone have a utility/tool/method of checking DCOM client/server
> on Windows Server 2003? I have a MS util for Win2K/NT server, but
> it's no good on 2k3.
>
> Thanks.

How did you determine you have a problem? Did you install a hotfix and now
experience errors in Event viewer? If so, can you elaborate?

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Having difficulty reading or finding responses to your post?
Instead of the website you're using, I suggest to use OEx (Outlook Express
or any other newsreader), and configure a news account, pointing to
news.microsoft.com. This is a direct link to the Microsoft Public
Newsgroups. It is FREE and requires NO ISP's Usenet account. OEx allows you
to easily find, track threads, cross-post, sort by date, poster's name,
watched threads or subject.

It's easy:
How to Configure OEx for Internet News
http://support.microsoft.com/?id=171164

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Directory Services
Microsoft Certified Trainer
Assimilation Imminent. Resistance is Futile
Infinite Diversities in Infinite Combinations

"Very funny Scotty. Now, beam down my clothes."

The only thing in life is change. Anything more is a blackhole consuming
unnecessary energy.

"Ace Fekay [MVP]" wrote:

> In news:98143969-B3BF-4AF1-93B2-(E-Mail Removed),
> The Vogon <(E-Mail Removed)> stated, which I commented on
> below:
> > I need to test DCOM communication between 2 Windows 2003 Servers, as I
> > believe I have a problem with it.
> >
> > Does anyone have a utility/tool/method of checking DCOM client/server
> > on Windows Server 2003? I have a MS util for Win2K/NT server, but
> > it's no good on 2k3.
> >
> > Thanks.
>
> How did you determine you have a problem? Did you install a hotfix and now
> experience errors in Event viewer? If so, can you elaborate?
>
> --
> Ace
>

My company is an ISP, and I have 4 Win2k3 servers running hosting software
which communicates to secondary clients (such as DNS and mail servers) via
DCOM. 3 of the servers communicate fine, the other does not. The sofware
vendors agree this is a DCOM problem, however they're at a loss as everything
appears to be configured correctly. All servers are on the same LAN and have
no firewalls between them. I can't be 100% sure this is a DCOM problem
though, so I need to test DCOM connectivity.

I'm not getting errors in Event Viewer regarding DCOM, but that doesn't mean
it's not working. Could be network problems (my servers are in a datacenter
so I can't be sure of config), could be security, could be application
issues. There doesn't seem any logic to the situation. I need to rule out
possiblities one by one, and quickly.

Only recent changes have been
1) MS Updates
2) Monthly hotfix patch on hosting software
(bear in mind other 3 servers are ok with same updates and hotfix)

In news:B295F029-9E7E-410F-A941-(E-Mail Removed),
The Vogon <(E-Mail Removed)> stated, which I commented on
below:

> My company is an ISP, and I have 4 Win2k3 servers running hosting
> software which communicates to secondary clients (such as DNS and
> mail servers) via DCOM. 3 of the servers communicate fine, the other
> does not. The sofware vendors agree this is a DCOM problem, however
> they're at a loss as everything appears to be configured correctly.
> All servers are on the same LAN and have no firewalls between them. I
> can't be 100% sure this is a DCOM problem though, so I need to test
> DCOM connectivity.
>
> I'm not getting errors in Event Viewer regarding DCOM, but that
> doesn't mean it's not working. Could be network problems (my servers
> are in a datacenter so I can't be sure of config), could be security,
> could be application issues. There doesn't seem any logic to the
> situation. I need to rule out possiblities one by one, and quickly.
>
> Only recent changes have been
> 1) MS Updates
> 2) Monthly hotfix patch on hosting software
> (bear in mind other 3 servers are ok with same updates and hotfix)

I see. If nothing comes up in the Event viewer concerning DCOM, I don't
think it's DCOM and rather something else happening. There was a patch issue
from back in Dec. If the default drive permissions were altered (I hope
not), and this specific update was put in place, it will render the system
useless with name resoltion and network connectivity. It was based on the
MSDTC, which is related to DCOM.


See if this repost applies to your case and helps:
+++++++++++++++++++++++++++++++++++++++++
I had a client with this problem just yesterday morning. This is a
permissions problem on the %windir%\registration folder.

Systems that have changed the default Access Control List permissions on the
%windir%\registration directory may experience various problems after you
install the Microsoft Security Bulletin MS05-051 for COM+ and MS DTC
http://support.microsoft.com/kb/909444

For specific info, see:
http://blogs.technet.com/steriley/ar...08/414002.aspx
++++++++++++++++++++++++++++++++++++++++

If not, then I would look at what services may have been disabled, such as
the DHCP Client service, which is a required service for name resolution,
whether the system has a static IP or gets it from DHCP.

Third party software can do it too.

Run a netdiag /v /fix > c:\netdiag.txt and copy/paste and post the results
please.

Ace

> Run a netdiag /v /fix > c:\netdiag.txt and copy/paste and post the results
> please.
>
> Ace
>
>
>
>

OK, here's the results of netdiag... The default drive permissions at root
have been altered slightly for 3rd party software.


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: DNS2
DNS Host Name: dns2.vogon.hr
DNS Domain Name: vogon.hr
System info : Windows 2000 Server (Build 3790)
Processor : x86 Family 15 Model 2 Stepping 5, GenuineIntel
Hotfixes :
Installed? Name
Yes KB883939
Yes KB890046
Yes KB893756
Yes KB896358
Yes KB896422
Yes KB896424
Yes KB896428
Yes KB896688
Yes KB896727
Yes KB899587
Yes KB899588
Yes KB899589
Yes KB899591
Yes KB900725
Yes KB901017
Yes KB901214
Yes KB902400
Yes KB903235
Yes KB904706
Yes KB905414
Yes KB905915
Yes KB908519
Yes KB909520
Yes KB910437
Yes KB911564
Yes KB911927
Yes KB912919
Yes KB913446
Yes Q147222
No ServicePackUninstall


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

Information of Netcard drivers:


---------------------------------------------------------------------------
Description: Intel(R) PRO/1000 MT Network Connection - Packet Scheduler
Miniport
Device: \DEVICE\{B1B2FE09-5DB4-44C4-A12E-5654DCA8967A}

Media State: Connected

Device State: Connected
Connect Time: 16:48:52
Media Speed: 10 Mbps

Packets Sent: 34923691
Bytes Sent (Optional): 0

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


---------------------------------------------------------------------------
Description: Intel(R) PRO/1000 MT Network Connection
Device: \DEVICE\{78B36818-9448-425D-81EB-DC087DB10B46}

Media State: Connected

Device State: Connected
Connect Time: 16:48:52
Media Speed: 10 Mbps

Packets Sent: 34923691
Bytes Sent (Optional): 0

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


---------------------------------------------------------------------------
[PASS] - At least one netcard is in the 'Connected' state.



Per interface results:

Adapter : Local Area Connection
Adapter ID . . . . . . . . : {78B36818-9448-425D-81EB-DC087DB10B46}

Netcard queries test . . . : Passed

Adapter type . . . . . . . : Ethernet
Host Name. . . . . . . . . : dns2
Description. . . . . . . . : Intel(R) PRO/1000 MT Network Connection
- Packet Scheduler Miniport
Physical Address . . . . . : 00-C0-9F-30-30-44
Dhcp Enabled . . . . . . . : No
DHCP ClassID . . . . . . . :
Autoconfiguration Enabled. : Yes
IP Address . . . . . . . . : 198.87.86.234
Subnet Mask. . . . . . . . : 255.255.255.0
IP Address . . . . . . . . : 198.87.84.234
Subnet Mask. . . . . . . . : 255.255.255.0
IP Address . . . . . . . . : 198.87.82.73
Subnet Mask. . . . . . . . : 255.255.255.0
IP Address . . . . . . . . : 198.87.86.235
Subnet Mask. . . . . . . . : 255.255.255.0
IP Address . . . . . . . . : 198.87.86.233
Subnet Mask. . . . . . . . : 255.255.255.0
IP Address . . . . . . . . : 198.87.86.232
Subnet Mask. . . . . . . . : 255.255.255.0
IP Address . . . . . . . . : 198.87.86.231
Subnet Mask. . . . . . . . : 255.255.255.0
IP Address . . . . . . . . : 198.87.84.67
Subnet Mask. . . . . . . . : 255.255.255.0
IP Address . . . . . . . . : 198.87.84.233
Subnet Mask. . . . . . . . : 255.255.255.0
IP Address . . . . . . . . : 198.87.84.66
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . : 198.87.84.1
Dns Servers. . . . . . . . : 198.87.84.168
198.87.84.66

IpConfig results . . . . . : Failed

[WARNING] Your default gateway is not on the same subnet as your
IP address.

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

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

NetBT name test. . . . . . : Passed
NetBT_Tcpip_{78B36818-9448-425D-81EB-DC087DB10B46}
DNS2 <00> UNIQUE REGISTERED
VOGON <00> GROUP REGISTERED
DNS2 <20> UNIQUE REGISTERED
VOGON <1E> GROUP REGISTERED
VOGON <1D> UNIQUE REGISTERED
..__MSBROWSE__.<01> GROUP REGISTERED
[WARNING] At least one of the <00> 'WorkStation Service', <03>
'Messenger 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. . . . . . . . . . . : Broadcast
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 . . . . : VOGON
Dns domain name is not specified.
Dns forest name is not specified.
Domain Guid. . . . . . . . . . : {00000000-0000-0000-0000-000000000000}
Logon User . . . . . . . . . . : chris
Logon Domain . . . . . . . . . : DNS2


NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{78B36818-9448-425D-81EB-DC087DB10B46}
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 : 10
Description: MSAFD Tcpip [TCP/IP]
Provider Version :2
Max message size : Stream Oriented
Description: MSAFD Tcpip [UDP/IP]
Provider Version :2
Description: RSVP UDP Service Provider
Provider Version :6
Description: RSVP TCP Service Provider
Provider Version :6
Max message size : Stream Oriented
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{78B36818-9448-425D-81EB-DC087DB10B46}] SEQPACKET 0
Provider Version :2
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{78B36818-9448-425D-81EB-DC087DB10B46}] DATAGRAM 0
Provider Version :2
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{CF5D9604-77E0-4FE1-8E29-3478811CCB4A}] SEQPACKET 1
Provider Version :2
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{CF5D9604-77E0-4FE1-8E29-3478811CCB4A}] DATAGRAM 1
Provider Version :2
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{F3079DD9-DB65-47CA-9A53-884B35E810EA}] SEQPACKET 2
Provider Version :2
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{F3079DD9-DB65-47CA-9A53-884B35E810EA}] DATAGRAM 2
Provider Version :2

Max UDP size : 65507 bytes


DNS test . . . . . . . . . . . . . : Passed
Interface {78B36818-9448-425D-81EB-DC087DB10B46}
DNS Domain:
DNS Servers: 198.87.84.168 198.87.84.66
IP Address: Expected registration with PDN (primary DNS
domain name):
Hostname: dns2.vogon.hr.
Authoritative zone: vogon.hr.
Primary DNS server: dns1.vogon.hr 198.87.84.168
Authoritative NS:198.87.82.73 198.87.84.168
Update is not allowed in zone vogon.hr..


Redir and Browser test . . . . . . : Passed
List of transports currently bound to the Redir
NetbiosSmb
NetBT_Tcpip_{78B36818-9448-425D-81EB-DC087DB10B46}
The redir is bound to 1 NetBt transport.

List of transports currently bound to the browser
NetBT_Tcpip_{78B36818-9448-425D-81EB-DC087DB10B46}
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 198.87.84.1 198.87.84.66 30
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
198.87.82.0 255.255.255.0 198.87.82.73 198.87.84.66 30
198.87.82.73 255.255.255.255 127.0.0.1 127.0.0.1 30
198.87.82.255 255.255.255.255 198.87.82.73 198.87.84.66 30
198.87.84.0 255.255.255.0 198.87.84.66 198.87.84.66 30
198.87.84.66 255.255.255.255 127.0.0.1 127.0.0.1 30
198.87.84.67 255.255.255.255 127.0.0.1 127.0.0.1 30
198.87.84.233 255.255.255.255 127.0.0.1 127.0.0.1 30
198.87.84.234 255.255.255.255 127.0.0.1 127.0.0.1 30
198.87.84.255 255.255.255.255 198.87.84.66 198.87.84.66 30
198.87.86.0 255.255.255.0 198.87.86.234 198.87.84.66 30
198.87.86.231 255.255.255.255 127.0.0.1 127.0.0.1 30
198.87.86.232 255.255.255.255 127.0.0.1 127.0.0.1 30
198.87.86.233 255.255.255.255 127.0.0.1 127.0.0.1 30
198.87.86.234 255.255.255.255 127.0.0.1 127.0.0.1 30
198.87.86.235 255.255.255.255 127.0.0.1 127.0.0.1 30
198.87.86.255 255.255.255.255 198.87.86.234 198.87.84.66 30
224.0.0.0 240.0.0.0 198.87.84.66 198.87.84.66 30
255.255.255.255 255.255.255.255 198.87.84.66 198.87.84.66 1
No persistent route entries.


Netstat information test . . . . . : Passed


Interface Statistics

Received Sent
Unicast Packets 3130553260 514443187
Non-unicast packets 816419 602
Discards 0 0
Errors 0 0
Unknown protocols 133135 458284

Interface index = 1
Description = MS TCP Loopback interface
Type = 24
MTU = 1520
Speed = 10000000
Physical Address = 00-00-00-00-00-00
Administrative Status = 1
Operational Status = 1
Last Changed = 2922947220
Output Queue Length = 0


Interface index = 2
Description = Intel(R) PRO/1000 MT Network Connection -
Packet Scheduler Miniport
Type = 6
MTU = 1500
Speed = 10000000
Physical Address = 00-C0-9F-30-30-44
Administrative Status = 1
Operational Status = 1
Last Changed = 2922947220
Output Queue Length = 15



Active Connections

Proto Local Address Foreign Address State
(Section removed... very long!)


IP Statistics

Packets Received = 32.107.091
Received Header Errors = 1
Received Address Errors = 184.018
Datagrams Forwarded = 0
Unknown Protocols Received = 0
Received Packets Discarded = 0
Received Packets Delivered = 31.923.560
Output Requests = 30.964.348
Routing Discards = 0
Discarded Output Packets = 0
Output Packet No Route = 0
Reassembly Required = 2
Reassembly Successful = 0
Reassembly Failures = 1
Datagrams successfully fragmented = 0
Datagrams failing fragmentation = 1
Fragments Created = 0
Forwarding = 2
Default TTL = 128
Reassembly timeout = 60


TCP Statistics

Active Opens = 331.462
Passive Opens = 432.455
Failed Connection Attempts = 1.520
Reset Connections = 271.171
Current Connections = 493
Received Segments = 31.791.580
Segment Sent = 30.441.259
Segment Retransmitted = 399.459
Retransmission Timeout Algorithm = vanj
Minimum Retransmission Timeout = 300
Maximum Retransmission Timeout = 120.000
Maximum Number of Connections = -1


UDP Statistics

Datagrams Received = 126.419
No Ports = 25.927
Receive Errors = 955
Datagrams Sent = 128.781


ICMP Statistics

Received Sent
Messages 1.801 1.801
Errors 672 672
Destination Unreachable 938 938
Time Exceeded 124 124
Parameter Problems 0 0
Source Quenchs 0 0
Redirects 0 0
Echos 42 42
Echo Replies 25 25
Timestamps 0 0
Timestamp Replies 0 0
Address Masks 0 0
Address Mask Replies 0 0


Bindings test. . . . . . . . . . . : Passed
Component Name : Network Monitor Driver
Bind Name: NM
Binding Paths:
Owner of the binding path : Network Monitor Driver
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Network Monitor Driver
Lower Component: Intel(R) PRO/1000 MT Network Connection

Owner of the binding path : Network Monitor Driver
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiswanbh
Upper Component: Network Monitor Driver
Lower Component: WAN Miniport (Network Monitor)


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 MT Network Connection


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 MT 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: ndiscowan
Upper Component: Remote Access NDIS WAN Driver
Lower Component: Direct Parallel

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: ndiswanasync
Upper Component: Remote Access NDIS WAN Driver
Lower Component: RAS Async Adapter


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 (TCP/IP)
-Interface Name: ndis5
Upper Component: Internet Protocol (TCP/IP)
Lower Component: Intel(R) PRO/1000 MT 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 (TCP/IP)
-Interface Name: ndiswanip
Upper Component: Internet Protocol (TCP/IP)
Lower Component: WAN Miniport (IP)


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

Owner of the binding path : Internet Protocol (TCP/IP)
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiswanip
Upper Component: Internet Protocol (TCP/IP)
Lower Component: WAN Miniport (IP)


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: 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 (TCP/IP)
-Interface Name: ndis5
Upper Component: Internet Protocol (TCP/IP)
Lower Component: Intel(R) PRO/1000 MT 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 (TCP/IP)
-Interface Name: ndiswanip
Upper Component: Internet Protocol (TCP/IP)
Lower Component: WAN Miniport (IP)


Component Name : WebClient
Bind Name: WebClient
Binding Paths:

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 MT 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 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)


Component Name : Wireless Configuration
Bind Name: wzcsvc
Binding Paths:

Component Name : Network Load Balancing
Bind Name: Wlbs
Binding Paths:
Owner of the binding path : Network Load Balancing
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Network Load Balancing
Lower Component: Intel(R) PRO/1000 MT 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 : Dial-Up Client
Bind Name: msrascli
Binding Paths:

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
Networks
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
Networks
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 (TCP/IP)
-Interface Name: ndis5
Upper Component: Internet Protocol (TCP/IP)
Lower Component: Intel(R) PRO/1000 MT Network Connection

Owner of the binding path : File and Printer Sharing for Microsoft
Networks
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 (TCP/IP)
-Interface Name: ndiswanip
Upper Component: Internet Protocol (TCP/IP)
Lower Component: WAN Miniport (IP)


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 (TCP/IP)
-Interface Name: ndis5
Upper Component: Internet Protocol (TCP/IP)
Lower Component: Intel(R) PRO/1000 MT 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 (TCP/IP)
-Interface Name: ndiswanip
Upper Component: Internet Protocol (TCP/IP)
Lower Component: WAN Miniport (IP)


Component Name : Generic Packet Classifier
Bind Name: Gpc
Binding Paths:

Component Name : Application Layer Gateway
Bind Name: ALG
Binding Paths:

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

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

Component Name : Direct Parallel
Bind Name: {427757CC-083D-4EE9-807C-F510C160819E}
Binding Paths:

Component Name : WAN Miniport (PPPOE)
Bind Name: {DB3CC8E0-707E-4CAF-974A-2816E71A1AC7}
Binding Paths:

Component Name : WAN Miniport (PPTP)
Bind Name: {2A08F669-355D-4509-88CB-D12AF20F1E6D}
Binding Paths:

Component Name : WAN Miniport (L2TP)
Bind Name: {47BF8C96-7EC8-48E7-814B-DF3E21450BC8}
Binding Paths:

Component Name : RAS Async Adapter
Bind Name: {61A55318-1E3D-42C1-8B0B-D23E1C6F22EB}
Binding Paths:

Component Name : Intel(R) PRO/1000 MT Network Connection
Bind Name: {78B36818-9448-425D-81EB-DC087DB10B46}
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


Thanks.

In news:6C6FA459-A615-4CBE-B11C-(E-Mail Removed),
The Vogon <(E-Mail Removed)> stated, which I commented on
below:
> OK, here's the results of netdiag... The default drive permissions at
> root have been altered slightly for 3rd party software.
>
>
> 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: DNS2
> DNS Host Name: dns2.vogon.hr
> DNS Domain Name: vogon.hr
> System info : Windows 2000 Server (Build 3790)
> Processor : x86 Family 15 Model 2 Stepping 5, GenuineIntel
> Hotfixes :
> Installed? Name
> Yes KB883939
> Yes KB890046
> Yes KB893756
> Yes KB896358
> Yes KB896422
> Yes KB896424
> Yes KB896428
> Yes KB896688
> Yes KB896727
> Yes KB899587
> Yes KB899588
> Yes KB899589
> Yes KB899591
> Yes KB900725
> Yes KB901017
> Yes KB901214
> Yes KB902400
> Yes KB903235
> Yes KB904706
> Yes KB905414
> Yes KB905915
> Yes KB908519
> Yes KB909520
> Yes KB910437
> Yes KB911564
> Yes KB911927
> Yes KB912919
> Yes KB913446
> Yes Q147222
> No ServicePackUninstall
>
>
> Netcard queries test . . . . . . . : Passed
>
> Information of Netcard drivers:
>
>
>
> Per interface results:
>
> Adapter : Local Area Connection
> Adapter ID . . . . . . . . :
> {78B36818-9448-425D-81EB-DC087DB10B46}
>
> Netcard queries test . . . : Passed
>
> Adapter type . . . . . . . : Ethernet
> Host Name. . . . . . . . . : dns2
> Description. . . . . . . . : Intel(R) PRO/1000 MT Network
> Connection - Packet Scheduler Miniport
> Physical Address . . . . . : 00-C0-9F-30-30-44
> Dhcp Enabled . . . . . . . : No
> DHCP ClassID . . . . . . . :
> Autoconfiguration Enabled. : Yes
> IP Address . . . . . . . . : 198.87.86.234
> Subnet Mask. . . . . . . . : 255.255.255.0
> IP Address . . . . . . . . : 198.87.84.234
> Subnet Mask. . . . . . . . : 255.255.255.0
> IP Address . . . . . . . . : 198.87.82.73
> Subnet Mask. . . . . . . . : 255.255.255.0
> IP Address . . . . . . . . : 198.87.86.235
> Subnet Mask. . . . . . . . : 255.255.255.0
> IP Address . . . . . . . . : 198.87.86.233
> Subnet Mask. . . . . . . . : 255.255.255.0
> IP Address . . . . . . . . : 198.87.86.232
> Subnet Mask. . . . . . . . : 255.255.255.0
> IP Address . . . . . . . . : 198.87.86.231
> Subnet Mask. . . . . . . . : 255.255.255.0
> IP Address . . . . . . . . : 198.87.84.67
> Subnet Mask. . . . . . . . : 255.255.255.0
> IP Address . . . . . . . . : 198.87.84.233
> Subnet Mask. . . . . . . . : 255.255.255.0
> IP Address . . . . . . . . : 198.87.84.66
> Subnet Mask. . . . . . . . : 255.255.255.0
> Default Gateway. . . . . . : 198.87.84.1
> Dns Servers. . . . . . . . : 198.87.84.168
> 198.87.84.66
>
> IpConfig results . . . . . : Failed

> [WARNING] Your default gateway is not on the same subnet as your
> IP address.


Thanks for posting the results.

I see this machine has multiple IPs, however the default gateway is not on
the same subnet as the first IP assigned to this machine. Not really a big
deal, but it shows up in the netdiag. I assume it's a web server or
something.

What concerns me more is that this machine had KB902400 (from MS05-051)
installed on it and the drive permissions were changed (even if they were
just "slightly" changed). THis is the core of the issue in the article I
provided in my previous post. DId you check into that article to determine
if it was helpful?

Actualy for security reasons, it is no longer necessary to alter permissions
on Win2000 or Win2003, not like we used to do on NT4 (which was not secure).
THe security built in to 2000 and 2003 didn't warrant drive permissions
alterations. The recommendations to not alter permissions on 2000 or 2003
was actually in the Reskits, but I don't have a direct link for you to read,
so you;ll have to take my word on it. Unfortunate that altering the drive
will alter DCOM, MSDTC and COM+ apps, such as in your case.

Of course this is conjecture on my part, but the altered permissions
coinciding with 902400 installed seems to be a likely bet.

See if that article I provided helps to change the permissions back.

Ace

>
> Thanks for posting the results.
>
> I see this machine has multiple IPs, however the default gateway is not on
> the same subnet as the first IP assigned to this machine. Not really a big
> deal, but it shows up in the netdiag. I assume it's a web server or
> something.
>
> What concerns me more is that this machine had KB902400 (from MS05-051)
> installed on it and the drive permissions were changed (even if they were
> just "slightly" changed). THis is the core of the issue in the article I
> provided in my previous post. DId you check into that article to determine
> if it was helpful?
>
> Actualy for security reasons, it is no longer necessary to alter permissions
> on Win2000 or Win2003, not like we used to do on NT4 (which was not secure).
> THe security built in to 2000 and 2003 didn't warrant drive permissions
> alterations. The recommendations to not alter permissions on 2000 or 2003
> was actually in the Reskits, but I don't have a direct link for you to read,
> so you;ll have to take my word on it. Unfortunate that altering the drive
> will alter DCOM, MSDTC and COM+ apps, such as in your case.
>
> Of course this is conjecture on my part, but the altered permissions
> coinciding with 902400 installed seems to be a likely bet.
>
> See if that article I provided helps to change the permissions back.
>
> Ace
>
>
>

Thanks for the reply...

I was very hopeful about this, as I found that the windows\registration
folder wasn't holding the correct permissions, so I've enabled them as
stated. "Everyone" was already bypassing traverse, so no change there.
However, the problem is still not resolved.

There seems to be no logic to this situation. My other three servers which
are running this DCOM based hosting software are all working fine with the
same secondaries, and have the same permissions (and altered persmissions),
as well as the same updates and MSDTC config.

I've also enabled NetworkDTCAccessTIP, but to no avail. I haven't restarted
the servers (I may do tonight out of hours, but I figure this shouldn't be
required).

Incidentally, the altered permissions I'm talking about are just traverse
permissions for Network Service on root and some system/program folders
required for .Net and DotNetNuke, without this .Net Web applications will not
run...

I'm at a loss again now

In news:2ADECC70-FA44-4054-A418-(E-Mail Removed),
The Vogon <(E-Mail Removed)> stated, which I commented on
below:
> Thanks for the reply...
>
> I was very hopeful about this, as I found that the
> windows\registration folder wasn't holding the correct permissions,
> so I've enabled them as stated. "Everyone" was already bypassing
> traverse, so no change there. However, the problem is still not
> resolved.
>
> There seems to be no logic to this situation. My other three servers
> which are running this DCOM based hosting software are all working
> fine with the same secondaries, and have the same permissions (and
> altered persmissions), as well as the same updates and MSDTC config.
>
> I've also enabled NetworkDTCAccessTIP, but to no avail. I haven't
> restarted the servers (I may do tonight out of hours, but I figure
> this shouldn't be required).
>
> Incidentally, the altered permissions I'm talking about are just
> traverse permissions for Network Service on root and some
> system/program folders required for .Net and DotNetNuke, without this
> .Net Web applications will not run...
>
> I'm at a loss again now

Sorry if I'm not much more helpful. From what I've heard and that MSDTC
issue, many folks have wound up reinstalling their systems to clean it up. I
hope that doesn't happen to you and the restart helps.

Ace

"Ace Fekay [MVP]" wrote:

> In news:2ADECC70-FA44-4054-A418-(E-Mail Removed),
> The Vogon <(E-Mail Removed)> stated, which I commented on
> below:
> > Thanks for the reply...
> >
> > I was very hopeful about this, as I found that the
> > windows\registration folder wasn't holding the correct permissions,
> > so I've enabled them as stated. "Everyone" was already bypassing
> > traverse, so no change there. However, the problem is still not
> > resolved.
> >
> > There seems to be no logic to this situation. My other three servers
> > which are running this DCOM based hosting software are all working
> > fine with the same secondaries, and have the same permissions (and
> > altered persmissions), as well as the same updates and MSDTC config.
> >
> > I've also enabled NetworkDTCAccessTIP, but to no avail. I haven't
> > restarted the servers (I may do tonight out of hours, but I figure
> > this shouldn't be required).
> >
> > Incidentally, the altered permissions I'm talking about are just
> > traverse permissions for Network Service on root and some
> > system/program folders required for .Net and DotNetNuke, without this
> > .Net Web applications will not run...
> >
> > I'm at a loss again now
>
> Sorry if I'm not much more helpful. From what I've heard and that MSDTC
> issue, many folks have wound up reinstalling their systems to clean it up. I
> hope that doesn't happen to you and the restart helps.
>
> Ace
>
>

Thanks for all your help Ace, I'm betting the problem is now in the vendor's
application, unfortuantely their support crew isn't great when it comes to
anything other than pushing articles about config at us. The other
administrator here is betting it's a network issue, so we'll put the server
through some tests... although (if I'm not mistaken) mmc works over
MSDTC/DCOM, and this works fine across the network.

Unfortuantely a reinstall for us is not an option... we have some 1500 web
customers on this server, to migrate this lot with no knowledge of passwords,
application requirements etc etc is an enormous task... If we get a
resolution though, I'll let you know...

Thanks again...

In news:71311A3E-2DED-4136-ADDD-(E-Mail Removed),
The Vogon <(E-Mail Removed)> stated, which I commented on
below:
> Thanks for all your help Ace, I'm betting the problem is now in the
> vendor's application, unfortuantely their support crew isn't great
> when it comes to anything other than pushing articles about config at
> us. The other administrator here is betting it's a network issue, so
> we'll put the server through some tests... although (if I'm not
> mistaken) mmc works over MSDTC/DCOM, and this works fine across the
> network.
>
> Unfortuantely a reinstall for us is not an option... we have some
> 1500 web customers on this server, to migrate this lot with no
> knowledge of passwords, application requirements etc etc is an
> enormous task... If we get a resolution though, I'll let you know...
>
> Thanks again...

You are welcome for the try on my part. I hope that you guys can come up
with a solution, and would hate to see you migrating 1500 websites!

Yes, please keep me updated.

Thanks,
Ace