I recently replaced a Linksys E900 router with a m0n0wall router distribution, and on my local LAN or external WAN I can not open custom ports. I need to open the following for active directory/dns/etc.. to authorize, sync, and update.
RPC endpoint mapper: 135/tcp, 135/udp Network basic input/output system (NetBIOS) name service: 137/tcp, 137/udp NetBIOS datagram service: 138/udp NetBIOS session service: 139/tcp RPC dynamic assignment: Win 2k/2003:1024-65535/tcp Win 2008+:49152-65535/tcp Server message block (SMB) over IP (Microsoft-DS): 445/tcp, 445/udp Lightweight Directory Access Protocol (LDAP): 389/tcp LDAP ping: 389/udp LDAP over SSL: 636/tcp Global catalog LDAP: 3268/tcp Global catalog LDAP over SSL: 3269/tcp Kerberos: 88/tcp, 88/udp Domain Name Service (DNS): 53/tcp1, 53/udp
I have a default LAN rule of:
Proto: * / Source: Lan Net / Port: * / Destination: * / Description: Default LAN -> any
So ANY traffic should be able to flow freely, yet I am getting error messages such as:
The DNS server could not open socket for address 192.168.1.1. Verify that this is a valid IP address for the server computer. If it is NOT valid use the Interfaces dialog under Server Properties in the DNS Manager to remove it from the list of IP interfaces. Then stop and restart the DNS server. (If this was the only IP interface on this machine and the DNS server may not have started as a result of this error. In that case remove the DNS\Parameters\ ListenAddress value in the services section of the registry and restart.) If this is a valid IP address for this machine, make sure that no other application (e.g. another DNS server) is running that would attempt to use the DNS port. For more information, see "DNS server log reference" in the online Help.
The DNS server could not bind a Transmission Control Protocol (TCP) socket to address 192.168.1.1. The event data is the error code. An IP address of 0.0.0.0 can indicate a valid "any address" configuration in which all configured IP addresses on the computer are available for use. Restart the DNS server or reboot the computer.
I've researched on m0n0walls forums and have had no luck, is this a bug with the distro?
Best Answer +BudMan , 11 January 2014 - 13:29
If m0n0wall is actually on 192.168.1.2 and your dns server is on 192.168.1.1, and your seeing this error on your dns server.
WTF can that have to do with m0n0wall? There is NOTHING that m0n0wall could be doing that would effect anything your dns server on a different IP address does - nothing!!
So we are missing something here.. But I assure you if what your saying is correct m0n0wall is not part of the puzzle. Go to the full post