|
|
![]() |
|
|
Top | #1 |
|
Somewhat eXPerienced
Joined: December 2001
Location: Woodbury, NJ
Posts: 790
Reputation: 50
Power: 131 |
Sorry about the long post here, but I am going to make sure I give you all of the details that I know so we can better resolve this issue. I have been in the process of reinstalling Microsoft Operations Manager 2005. I had to reinstall it because there were severe database issues which were posing a problem from getting alerts. We weren't able to install the agent then either. During this time, I have been able to install the MOM Agent on all servers but 2, and both of them have ISA Server 2004 on them (don't ask why, they both have a different purpose! ![]() The servers are named Gateway1, and Gateway2. I get the following error messages on them respectively when I try to install the agent:
Originally Posted by Gateway1
Originally Posted by Gateway2
After researching everything that was going on, I have come across two Microsoft KB Articles. The first one (909031) explains how to enable "EnablePMTUDiscover" in the registry. Following the instructions in this guide yielded no results. The second one (933989) explains how to make sure RPC is not enforced, how to setup the proper rules to get everything going, etc. This also yielded no results.
When going over both of the KB articles had failed, I began to try other ways. I found a utility for MOM in the resource kit that will scan a remote computer's ports and will pass or fail what it can and can't do for the agent install. That log is as follows: Code:
*****************************************************
Scan started at: 10/26/2007 13:24:38
Scan ended at: 10/26/2007 13:26:48
Errors: 10 - Warnings 0 - Successes: 4
Scanned 1 machine(s).
Machine: Gateway1
Rules to scan: 14
------------------------------------------
Item: Windows Installer Service
Status: Error
Enabled: True
Scanned: True
Could not determine service state and status.
Reason: The RPC server is unavailable.
------------------------------------------
Item: MOM Channel-TCP
Status: Error
Enabled: True
Scanned: True
Description: MOM Channel
Port number: 1270
Protocol: TCP
Error code: 10060
Reason: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
------------------------------------------
Item: Ping-ICMP
Status: Success
Enabled: True
Scanned: True
Description: Ping
Protocol: ICMP
Pinging Gateway1.DTPD1.COM [10.0.1.6] with 32 bytes of data:
Reply from 10.0.1.6: bytes=32 time<1ms TTL=128
Reply from 10.0.1.6: bytes=32 time<1ms TTL=128
Reply from 10.0.1.6: bytes=32 time<1ms TTL=128
Reply from 10.0.1.6: bytes=32 time<1ms TTL=128
Ping statistics for 10.0.1.6:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
------------------------------------------
Item: RPC endpoint mapper-TCP
Status: Success
Enabled: True
Scanned: True
Description: RPC endpoint mapper
Port number: 135
Protocol: TCP
Successfully verified.
------------------------------------------
Item: NetBIOS session service-TCP
Status: Success
Enabled: True
Scanned: True
Description: NetBIOS session service
Port number: 139
Protocol: TCP
Successfully verified.
------------------------------------------
Item: OLE DB Port 1434-TCP
Status: Error
Enabled: True
Scanned: True
Description: OLE DB Port 1434
Port number: 1434
Protocol: TCP
Error code: 10060
Reason: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
------------------------------------------
Item: SMB over IP-TCP
Status: Success
Enabled: True
Scanned: True
Description: SMB over IP
Port number: 445
Protocol: TCP
Successfully verified.
------------------------------------------
Item: OLE DB Port 1433-TCP
Status: Error
Enabled: True
Scanned: True
Description: OLE DB Port 1433
Port number: 1433
Protocol: TCP
Error code: 10060
Reason: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
------------------------------------------
Item: Web Console-TCP
Status: Error
Enabled: True
Scanned: True
Description: Web Console
Port number: 1272
Protocol: TCP
Error code: 10060
Reason: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
------------------------------------------
Item: Remote Registry Service
Status: Error
Enabled: True
Scanned: True
Could not determine service state and status.
Reason: The RPC server is unavailable.
------------------------------------------
Item: Machine Discovery
Status: Error
Enabled: True
Scanned: True
Machine Name: Gateway1
IP Address: 10.0.1.6
DNS machine name: 'Gateway1.DTPD1.COM'
Could not get domain name.
Reason: The RPC server is unavailable.
------------------------------------------
Item: NetBIOS name service-TCP
Status: Error
Enabled: True
Scanned: True
Description: NetBIOS name service
Port number: 137
Protocol: TCP
Error code: 10060
Reason: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
------------------------------------------
Item: Net Logon Service
Status: Error
Enabled: True
Scanned: True
Could not determine service state and status.
Reason: The RPC server is unavailable.
------------------------------------------
Item: MCF-TCP
Status: Error
Enabled: True
Scanned: True
Description: MCF
Port number: 1271
Protocol: TCP
Error code: 10060
Reason: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Again, sorry for the long post! |
|
|
|
![]() |
| Bookmarks |
| Thread Tools | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| ISA Server 2004: SSL Port 44300 Error | Punkrulz | Windows Desktop Systems | 5 | August 16th, 2007 7:02pm |
| ISA Server 2004, Timeout on connection? | Punkrulz | Windows Desktop Systems | 1 | August 31st, 2006 9:56pm |
| UEFA Champions League 2004 - 2005 | luish | PC Gaming | 0 | February 21st, 2005 7:31pm |
| [Football]Who will win premiership 2004/2005? | Lee | Green Room | 19 | August 11th, 2004 6:36pm |
| UT 2004 listen server problems! | Sexo um Pato | PC Gaming | 17 | May 10th, 2004 6:23am |