Solved

DLINK DNS-323 NAS drive not detected.  Firewall issue.

Posted on 2008-10-30
6
1,161 Views
Last Modified: 2012-05-05
If I disable Microsoft Firewall, I can connect to the \\ip\volume address manually to this NAS drive.  But I must have Microsoft Firewall on in order for ISA server 2004 to do its job and provide other essential services.  What rule can I add to ISA server 2004 to allow the server to conect to this network resource?
0
Comment
Question by:RadRichie
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
6 Comments
 
LVL 19

Expert Comment

by:Stephen Manderson
ID: 22843932
Just to clear a few things up, you are disabling windows firewall on the internal client that is trying to connect to the NAS inside the network on the same subnet?

ISA has windows firewall disabled as default on the ISA server machine and as such doesnt compromise the security of the web facing ISA server if the local client firewall is disabled. (However still recommend to keep it turned on)

Is there any error logs relating to the traffic to/from the NAS on the ISA logging?

Regards
Steve
0
 
LVL 1

Author Comment

by:RadRichie
ID: 22846032
Yes, router = 10.0.0.1, server with ISA nic is 10.0.0.251 (other NiC (192.168.16.2)), NAS is 10.0.0.252.  If I turn off Windows Firewall then a terminal server (192.168.16.5) connected via a crossover cable to the other NiC (192.168.16.2) can't connect to the SQL or other services on the main server.  So its a catch-22 until I find the path (rule) through ISA to enable both objectives.

Thx, Rich
0
 
LVL 1

Author Comment

by:RadRichie
ID: 22884077
Still looking for how to enable access to the NAS from the server.
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
LVL 1

Author Comment

by:RadRichie
ID: 22939556
Points increased folks :)
0
 
LVL 1

Author Comment

by:RadRichie
ID: 22939574
Note its Microsoft Firewall, not Windows Firewall that is the key to this problem.  Disabling Microsoft Firewall service kills external RDP access to the server, but enables connection to the NAS, and vice versa.
0
 
LVL 1

Accepted Solution

by:
RadRichie earned 0 total points
ID: 22968180
Disregard this question.  I'll put the NAS on the internal network so I don't have to go through ISA.
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

There are three types of ISA client that can be configured - these can be individual clients or multiples of a client on each PC or server SecureNAT. A SecureNAT client for ISA server is a client machine, work station or server, that has its defa…
In Africa (and potentially where you live…), reliability of ISPs is questionable.  With the increased reliance on e-mail as one of the primary forms of communication, the costs to business are significant based on interuption of ISP Connectivity.  T…
Michael from AdRem Software explains how to view the most utilized and worst performing nodes in your network, by accessing the Top Charts view in NetCrunch network monitor (https://www.adremsoft.com/). Top Charts is a view in which you can set seve…
This is my first video review of Microsoft Bookings, I will be doing a part two with a bit more information, but wanted to get this out to you folks.

623 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question