jhdjbutler
asked on
Verify firewall ports in logon script
I am looking to write a bat file to use as part of a logon script to verify that users have proper port opened for SMS. If a port isn't open, the batch file should open it. I have already created a batchfile that will open the ports. The enviroment has 2k3 domain controlers and file servers, along with some 2k file server. Al workstaions are XP pro.
ASKER
Thanks for the info but I have already created the batch file to open necessary ports. I am looking to create a logon script that will check to see if every port is open, and if not, it will open it. I am looking primarly for a way to verify one port at a time.
I really don't think that can be done with DOS. VB code, or c++ is a more likely solution.
Why would you need to "check/verify" , if they are open ?? ....instead of just making sure they are always open anytime someone logs on ?
If you just want to check if they are open...why not just use a scanner against the whole subnet from a single workstation ?
Why would you need to "check/verify" , if they are open ?? ....instead of just making sure they are always open anytime someone logs on ?
If you just want to check if they are open...why not just use a scanner against the whole subnet from a single workstation ?
ASKER
I have thought about using a port scanner to verify, the only problem is about 60% of my 200 users are sales engineers who can go long periods of time with out ever connecting to the network. I can run reports from the sms server to show who has been connecting properly, but again somtimes it is a week or two between when the users vpn in so its hard to tell who actually working properly. The sales staff uses their laptops to do alot of sales demos so they tinker with their windows firewall frequently in order to demo certain apps (i.e. other firewalls).
When you say:
"Why would you need to "check/verify" , if they are open ?? ....instead of just making sure they are always open anytime someone logs on ?"
that is what I am looking to do, make sure that they are always open anytime somone logs in. Corprate (the power over all 2500 users) is requiring all of our users to comply with this firewall policy. They told me to just incorperate the port open netsh commands into the logon script. The only problem I have with doing that is that it takes time (and sales engineers are not the most patient people I've met). If the only answer is to open them each time, I guess I will have to live with it. I was just hoping that there was a way to do a quick check before "wasting" their time.
When you say:
"Why would you need to "check/verify" , if they are open ?? ....instead of just making sure they are always open anytime someone logs on ?"
that is what I am looking to do, make sure that they are always open anytime somone logs in. Corprate (the power over all 2500 users) is requiring all of our users to comply with this firewall policy. They told me to just incorperate the port open netsh commands into the logon script. The only problem I have with doing that is that it takes time (and sales engineers are not the most patient people I've met). If the only answer is to open them each time, I guess I will have to live with it. I was just hoping that there was a way to do a quick check before "wasting" their time.
I understand now....
Ok...there are only two ways I can think to do this, one would be to create your own group policy administrative template...(assuming that the firewall configuration can be modified via the registry.) This will take a bit of research and practice on your part. I haven't yet had to create my own gp template, but I know where the information is on how to do it.
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/management/gp/admtgp.mspx
Two, create an .msi file which essentially would do the same thing but it is more user friendly, and it costs . ....using WINSTALL LE. < I use this to create small .msi files to modify registry settings, or install programs through group policy/logon script.
www.ondemandsoftware.com
Ok...there are only two ways I can think to do this, one would be to create your own group policy administrative template...(assuming that the firewall configuration can be modified via the registry.) This will take a bit of research and practice on your part. I haven't yet had to create my own gp template, but I know where the information is on how to do it.
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/management/gp/admtgp.mspx
Two, create an .msi file which essentially would do the same thing but it is more user friendly, and it costs . ....using WINSTALL LE. < I use this to create small .msi files to modify registry settings, or install programs through group policy/logon script.
www.ondemandsoftware.com
ASKER
Thanks for the info. Unfortunately the network heads do not let lower level network admins push GPO's. They make us responsible for enforcing policies, but the limit our ability to do so (corporate America for ya). What I ended up doing is having the logon script create a file containing info from the "netsh.exe firewall show portopening". Then I do a string search in the file to verify the ports are opened. This takes about 1/4 the time it took to open the ports, so I figure it will have to do. The script looks like this:
@ECHO OFF
IF EXIST C:\FWSTATS.TXT del c:\fwstats.txt
netsh.exe firewall show portopening > c:\fwstats.txt
findstr SMS389 c:\fwstats.txt
findstr SMS636 c:\fwstats.txt
findstr SMS3268 c:\fwstats.txt
findstr SMS2703 c:\fwstats.txt
findstr SMS2701 c:\fwstats.txt
findstr SMS2702 c:\fwstats.txt
findstr SMS2704 c:\fwstats.txt
if not %errorlevel% equ 1 goto end
ECHO. ENABLING FILE AND PRINTER PORT...
netsh.exe firewall set service type = FILEANDPRINT mode = ENABLE Profile=ALL Scope=Custom addresses=139.126.12.106,1
ECHO. ENABLING VARIOUS PORTS FOR THE SMS CLIENT...
netsh.exe firewall add portopening protocol=all port=389 name=SMS389=enable profile=all scope=custom addresses=139.126.12.106,1
netsh.exe firewall add portopening protocol=tcp port=636 name=SMS636=enable profile=all scope=custom addresses=139.126.12.106,1
netsh.exe firewall add portopening protocol=all port=3268 name=SMS3268=enable profile=all scope=custom addresses=139.126.12.106,1
netsh.exe firewall add portopening protocol=all port=2703 name=SMS2703=enable profile=all scope=custom addresses=139.126.12.106,1
netsh.exe firewall add portopening protocol=all port=2701 name=SMS2701=enable profile=all scope=custom addresses=139.126.12.106,1
netsh.exe firewall add portopening protocol=all port=2702 name=SMS2702=enable profile=all scope=custom addresses=139.126.12.106,1
netsh.exe firewall add portopening protocol=all port=2704 name=SMS2704=enable profile=all scope=custom addresses=139.126.12.106,1
ECHO. ***** FIREWALL PORTS WERE SUCCESSFULLY OPENED! *****
ECHO.
ECHO.
:end
ECHO.
ECHO.
ECHO.
ECHO. ****** SMS CLIENT FIREWALL PORTS HAVE BEEN VERIFIED. ******
del c:\fwstats.txt
It ends up workin’ pretty slick. I still wish there was a simpler way to do this though.
@ECHO OFF
IF EXIST C:\FWSTATS.TXT del c:\fwstats.txt
netsh.exe firewall show portopening > c:\fwstats.txt
findstr SMS389 c:\fwstats.txt
findstr SMS636 c:\fwstats.txt
findstr SMS3268 c:\fwstats.txt
findstr SMS2703 c:\fwstats.txt
findstr SMS2701 c:\fwstats.txt
findstr SMS2702 c:\fwstats.txt
findstr SMS2704 c:\fwstats.txt
if not %errorlevel% equ 1 goto end
ECHO. ENABLING FILE AND PRINTER PORT...
netsh.exe firewall set service type = FILEANDPRINT mode = ENABLE Profile=ALL Scope=Custom addresses=139.126.12.106,1
ECHO. ENABLING VARIOUS PORTS FOR THE SMS CLIENT...
netsh.exe firewall add portopening protocol=all port=389 name=SMS389=enable profile=all scope=custom addresses=139.126.12.106,1
netsh.exe firewall add portopening protocol=tcp port=636 name=SMS636=enable profile=all scope=custom addresses=139.126.12.106,1
netsh.exe firewall add portopening protocol=all port=3268 name=SMS3268=enable profile=all scope=custom addresses=139.126.12.106,1
netsh.exe firewall add portopening protocol=all port=2703 name=SMS2703=enable profile=all scope=custom addresses=139.126.12.106,1
netsh.exe firewall add portopening protocol=all port=2701 name=SMS2701=enable profile=all scope=custom addresses=139.126.12.106,1
netsh.exe firewall add portopening protocol=all port=2702 name=SMS2702=enable profile=all scope=custom addresses=139.126.12.106,1
netsh.exe firewall add portopening protocol=all port=2704 name=SMS2704=enable profile=all scope=custom addresses=139.126.12.106,1
ECHO. ***** FIREWALL PORTS WERE SUCCESSFULLY OPENED! *****
ECHO.
ECHO.
:end
ECHO.
ECHO.
ECHO.
ECHO. ****** SMS CLIENT FIREWALL PORTS HAVE BEEN VERIFIED. ******
del c:\fwstats.txt
It ends up workin’ pretty slick. I still wish there was a simpler way to do this though.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
http://support.microsoft.com/kb/826852
So you would use the NETSH command. (net shell)
netsh firewall set portopening TCP 139 SMS ENABLE ALL
netsh firewall set portopening TCP 445 SMB ENABLE ALL
Example of Netsh | Firewall usage:
set portopening
[ protocol = ] TCP|UDP|ALL
[ port = ] 1-65535
[ [ name = ] name
[ mode = ] ENABLE|DISABLE
[ scope = ] ALL|SUBNET|CUSTOM
[ addresses = ] addresses
[ profile = ] CURRENT|DOMAIN|STANDARD|AL
[ interface = ] name ]
Sets firewall port configuration.
Parameters:
protocol - Port protocol.
TCP - Transmission Control Protocol (TCP).
UDP - User Datagram Protocol (UDP).
ALL - All protocols.
port - Port number.
name - Port name (optional).
mode - Port mode (optional).
ENABLE - Allow through firewall (default).
DISABLE - Do not allow through firewall.
scope - Port scope (optional).
ALL - Allow all traffic through firewall (default).
SUBNET - Allow only local network (subnet) traffic through firewall.
CUSTOM - Allow only specified traffic through firewall.
addresses - Custom scope addresses (optional).
profile - Configuration profile (optional).
CURRENT - Current profile (default).
DOMAIN - Domain profile.
STANDARD - Standard profile.
ALL - All profiles.
interface - Interface name (optional).
Remarks: 'profile' and 'interface' may not be specified together.
'scope' and 'interface' may not be specified together.
'scope' must be 'CUSTOM' to specify 'addresses'.
Examples:
set portopening TCP 80 MyWebPort
set portopening UDP 500 IKE ENABLE ALL
set portopening ALL 53 DNS ENABLE CUSTOM
157.60.0.1,172.16.0.0/16,1
set portopening protocol = TCP port = 80 name = MyWebPort
set portopening protocol = UDP port = 500 name = IKE mode = ENABLE scope =
ALL
set portopening protocol = ALL port = 53 name = DNS mode = ENABLE
scope = CUSTOM addresses =
157.60.0.1,172.16.0.0/16,1