Nope, I've just ended up adding it to individual machines as an additional address book.
But if you do find a solution, I would sure appreciate you letting me know.
When I telnet to port 25 on my exchange server from somewhere outside my network I get:
220 ***********************************************************0****0*2*********
***************200************0*00
If I do it from within my network I get:
220 mail.server.name Microsoft ESMTP MAIL...
Look at the message headers and see if the messages originate externally. Usually these spoofs will come from an IP that is not within your organization. The only way to kill these is with some type of filter / RDNS lookup.
GFI has worked well for us.
I know that individual users can add an ldap address book in outlook. But can I do this at the exchange system level for the entire organization?
We work closely with another entity that is not part of our network (physically or logically) and many of our users need to be able to look up...
Is there any methodologies anyone can recommend for encorporating dual authentication for remote terminal services connections?
The RSA dongles are way expensive. I am currently using biometric fingerprint devices on-site, is there a way that I could require a fingerprint scan from remote...
My log is filling up with the following error:
The service threw an unexpected exception which was caught at f:\titanium\dsa\src\lra\abv_dg\lservagent.cpp(4511)
Also I created some new user accounts and their exchange mailboxes are not being created.
Any ideas?
Adam
Does anyone have suggestions for tracking which users access files and when.
For certain directories I would like to be able to access who accesses files and when. If possible it would be great to store the information in a database, but just a txt logfile would be fine.
Thanks
From the 132.2.50.x hosts I can now ping all the 10.20.4.x, but I can't ping anything but 10.20.4.x, like 10.1.1.17. Is it something on my end (Pix) or is it something on the othern end of things (Return route)?
OK I tried the above, but still can't get to any of the 10.x.x.x hosts from the .50.x machines.
I opened all traffice between the DMZ and the internal interface. I tried pinging 10.20.4.1 as well as going to it's webserver and share with no luck.
Do I need to remove the static route I added...
I added the route dmz 10.0.0.0 255.0.0.0 10.20.4.1 now I can ping all the 10.x.x.x machines ie. 10.1.1.17 from the firewall without any problems, but I'm still working on getting the .50.x machines to be able to ping the 10.x.x.x network. I imagine it is something with the NAT I need to do.
I tried inputing the command the nat (inside,dmz) 0 132.2.50.0 255.255.255.0 10.x.x.x 255.x.x.x
I got the error message: invalid number of interfaces specified. So I tried it via the web interface, and got some other error.
I'll give it a shot.
Also do I need to configure a gateway for the DMZ interface. Everything in this building is using 10.20.4.1 as the default gateway. The DMZ interface IP is 10.20.4.76.
OK, I thougt I would ask the experts first before I delve into this.
Currently in my building there are 2 separate networks. 132.5.50.x public address space (all behind the PIX) and a 10.x.x.x network. The 10.x.x.x network is connected to another business' network via a T1. Currently the...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.