Search results for query: *

Thanks for reply and links, I'll give 'em a read... I would be fine with the functionality of the inherent firewall. However, I have one other thread here: http://www.tek-tips.com/viewthread.cfm?qid=957474&page=1 It describes the limitation I'm running into in more detail. I wrote it in...

Thanks for your responses. That is what I would prefer to do and I have considered that. However, I pay for space at a co-location facility (per U). So even though the device is inexpensive up front, I believe it would incur more monthly fees (forever). Although, I haven't asked them, so...

I'm looking for an application Firewall for Windows 2003 Server with the following criteria: 1) Windows 2003 compatible. 2) Installs as a service. 3) Supports multiple IP Addresses (this is the reason I can't use the inherent Windows firewall) 4) Doesn't cost a fortune. I mainly concerned with...

I figured it out. In our case, there was another service running that was conflicting with the ports that IBM Director uses. You can use netstat (or TCPView from SysInternals) to find the conflicting service and stop it. Hope this can save someone time in the future.

The TWGServer.err log shows this: Application Error: Time: Thu Mar 09 11:28:15 PST 2006 Application: TWGServer (TWGVersion 4.20 2004-10-05 build id 538) Op Sys: Windows 2003 Error Code: 17 Error Message: SLP init error Stack Trace: com.tivoli.twg.engine.slp.ServiceLocationException: network...

Did you ever figure this out? We are having the same issue and there appears to be very little info regarding it. We are running the same build too. Thanks.

I'm trying to setup Windows 2003 Server Firewall on a 2003 Server hosting more than one ip address. The firewall rules(i.e. open ports, exceptions) seem to only support one ip address (if just the name is specified in the service settings). The rest of the ip addresses are completely blocked...

That M$ script also manipulates IIS badmail too. So be careful. My IIS badmail content is a LOT more valuable to me than my Exchange badmail content. Remember keep it simple, bigger isn't always better.

Hi zoeythecat, I'm glad I could help. Believe me, I've learned the hard way with the net stop command on other issues. Since exchange doesn't lock these files, they are easily deleted. The line in the batch file is nothing more than a delete command from DOS. If you do del /? at a command...

Lander215 is right. You do not need to stop the smtp service and rename directories, etc. Here is my batch file for the exact same goal: del /Q /F "D:\ExchSrvr\Mailroot\vsi 1\badmail\*" It works like a champ and my smtp server is down for 0 seconds. Can anyone beat that? The more...