Any ideas??? I install IDS device manager on a Windows 2000 client. I am able to manage the IDS sendor thru IDM without any issues. I download IDS event viewer from IDM onto the same Windows 2000 client and install it. When I add the sensor as a new device into IEV, I get a PostOffice protocol error and it tells me to reboot my client. After a reboot, I right click on the IDS sensor in IEV and try to look at the status and IEV reports it cannot contact the sensor??????
When you say "I install IDS device manager on a Windows 2000 client" what do you mean. The IDS device manager runs on the sensor itself and can be accessed through a web browser so their is nothing to install on a Windows 2000 client.
If instead of IDM you meant that you installed IDS MC (part of the VMS bundle which is an additional purchase), then you can't install IDS MC and IEV on the same machine because it will give you postoffice errors.
What version of IEV and what version of the Sensor are you running?
If you are running Active Directory on your 2000 client then be aware of DDTS Issue CSCdy14263.
Adding or removing sensors will require a reboot of the IEV machine in order to sync configurations because of problems caused by Active Directory.
You will be able to monitor, but will not be able to query postoffice for sensor communication status.
Firewalls between the sensor and IEV are often causes of communication problems.
Try logging into the sensor as user netrangr and executing nrconns. If the connection is not established then it is often because the firewall is blocking UDP port 45000 between the 2 machines. (IDM may be working because it uses TCP on port 80 or 443 so it's port may be open)
If the connection shows Established then look at the end of the status line. Sometimes it will show Established but will also say something like "Syn not received" at the end. This is sometimes seen when the firewall is allowing packets from IEV to the sensor, but not from the sensor to IEV. So in effect only half the connection is established.
You can paste the output from "nrconns" on the sensor into your reply and I can tell if you are maybe in this situation.
On very rare occasions you may even try restarting the services on the sensor (nrstop followed by nrstart).
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...