IP Filtering

  • Thread starter Thread starter pc830
  • Start date Start date
P

pc830

We have a windows 2000 server running IIS for public
access with 10 public IPs. The router is broken. We would
like to enable IP filtering to open the port 80 for the
web, 25 and 110 for the mail, and TCP and UDP 53 for the
DNS (we have only one NIC with all public IPs and use our
ISP DNS) before replacing the router. Every thing looks
good except DNS. We can ping any public Ip but can't ping
the web name llike yahoo.com. Nsllokup gets the time out
too. which ports do we need to open except tcp and udp 53?
Or do we miss some things?
 
Disabe IP Filtering and see if it works.
If it does not, then it might be a problem with the DNS server and/or its
configuration itself.
If it does probably you might want to open TCP port 139.
 
Thank you for the reply. Disabling IP filtering works.
disabling IP filtering and adding TCP 139 don't work. Any
other suggestions?
-----Original Message-----
Disabe IP Filtering and see if it works.
If it does not, then it might be a problem with the DNS server and/or its
configuration itself.
If it does probably you might want to open TCP port 139.


--
Regards,
Rama Krishna Prasad[MS]

--
This posting is provided "AS IS" with no warranties, and confers no rights.
We have a windows 2000 server running IIS for public
access with 10 public IPs. The router is broken. We would
like to enable IP filtering to open the port 80 for the
web, 25 and 110 for the mail, and TCP and UDP 53 for the
DNS (we have only one NIC with all public IPs and use our
ISP DNS) before replacing the router. Every thing looks
good except DNS. We can ping any public Ip but can't ping
the web name llike yahoo.com. Nsllokup gets the time out
too. which ports do we need to open except tcp and udp 53?
Or do we miss some things?
Click to expand...


.
Click to expand...
 
You need to open DNS client lookup ports (TCP and UDP 53 ports ) as well.
Also ensure that you have opened port for both incoming and outgoing
traffic.

--
-Pawan [MSFT]

-------------------------------------------------------------------------
"This posting is provided "AS IS" with no warranties, and confers no
rights."
------------------------------------------------------------------------
Thank you for the reply. Disabling IP filtering works.
disabling IP filtering and adding TCP 139 don't work. Any
other suggestions?
-----Original Message-----
Disabe IP Filtering and see if it works.
If it does not, then it might be a problem with the DNS server and/or its
configuration itself.
If it does probably you might want to open TCP port 139.


--
Regards,
Rama Krishna Prasad[MS]

--
This posting is provided "AS IS" with no warranties, and confers no rights.
We have a windows 2000 server running IIS for public
access with 10 public IPs. The router is broken. We would
like to enable IP filtering to open the port 80 for the
web, 25 and 110 for the mail, and TCP and UDP 53 for the
DNS (we have only one NIC with all public IPs and use our
ISP DNS) before replacing the router. Every thing looks
good except DNS. We can ping any public Ip but can't ping
the web name llike yahoo.com. Nsllokup gets the time out
too. which ports do we need to open except tcp and udp 53?
Or do we miss some things?
Click to expand...


.
Click to expand...
Click to expand...
 
Back
Top