C
Clementius
Hi,
I am configuring an access-list for traffic from a dmz server to an internal
server. The dmz server is a 2003 domain member server. The internal server
is a 2003 AD controller and file server. The plan is to allow file access
from the dmz server to the internal server. Eventually, the dmz server will
be a front-end to the internal server from the Internet through SSH or
Terminal Server sessions. So far I opened the following ports to the
internal server (from the dmz) on the firewall:
TCP domain
UDP domain
tcp 88
udp 88
tcp 135
udp 389
tcp 389
tcp 445
udp netbios-ns
udp netbios-dgm
tcp netbios-ssn
I am able to perform nslookup from the dmz server using the internal server
for DNS and NAT seems to work fine. But when I try to map a drive from the
dmz server to a share on the internal server I get: "The drive could not be
mapped because no network was found".
Am I missing something? Thanks for your help. C
I am configuring an access-list for traffic from a dmz server to an internal
server. The dmz server is a 2003 domain member server. The internal server
is a 2003 AD controller and file server. The plan is to allow file access
from the dmz server to the internal server. Eventually, the dmz server will
be a front-end to the internal server from the Internet through SSH or
Terminal Server sessions. So far I opened the following ports to the
internal server (from the dmz) on the firewall:
TCP domain
UDP domain
tcp 88
udp 88
tcp 135
udp 389
tcp 389
tcp 445
udp netbios-ns
udp netbios-dgm
tcp netbios-ssn
I am able to perform nslookup from the dmz server using the internal server
for DNS and NAT seems to work fine. But when I try to map a drive from the
dmz server to a share on the internal server I get: "The drive could not be
mapped because no network was found".
Am I missing something? Thanks for your help. C