<div>
What Linksys ? Router, AP, other ?<br />
<br />
Anyway check if linksys DNS config points to the dns of your internal network.<br />
<br />
<br />

</div>


<div>
In linksys you need to configure DNS server IP.Can you post IP's /subnet assigned to interfaces, and 'ipconfig /all&quot; from CMD of PC behind linksys ?
</div>


<div>
Linksys router model BEFSR11.<br />
Want to use it as a router and not a gateway.<br />
The DNS configution on the Linksys matches the one on the internal network.<br />
<br />
Linksys configuration is as follow :<br />
Wan IP : 192.168.0.247<br />
Subnet : 255.255.255.0<br />
Gateway : 192.168.0.1<br />
DNS : 192.168.0.8 / 192.168.0.15 / 192.168.0.9<br />
<br />
Lan IP : 192.168.7.1<br />
Subnet : 255.255.255.0<br />
<br />
DHCP on Linksys :<br />
Starting at 192.168.7.10<br />
DNS : 192.168.0.8 / 192.168.0.15 / 192.168.0.9<br />
<br />
<br />
Configuration on PC behind linksys :<br />
IP : 192.168.7.10<br />
Subnet : 255.255.255.0<br />
Gateway : 192.168.7.1<br />
DNS : 192.168.0.8 / 192.168.0.15 / 192.168.0.9<br />
<br />
<br />
Do i need to add a static route to my ISA server?<br />
<br />
Thank you
</div>


<div>
If you want to use it as a router (i.e. NAT disabled) &nbsp;than you have to add a static route on every pc that need to communicate from isa lan to linksys lan. Dns resolution problem will be avoided.<br />
To see if it is right launch this command on the DNS server and on ISA<br />
<br />
In a command prompt write:<br />
route add 192.168.7.0 mask 255.255.255.0 192.168.0.247<br />
<br />
Now try dns resolution.<br />
If it is ok and you don't want to use NAT on the linksys lan than you have to add this route to all pc and make it persistent through the switch:<br />
<br />
route -p add 192.168.7.0 mask 255.255.255.0 192.168.0.247<br />
<br />
<br />
<br />
<br />

</div>


<div>
Ok, you got half of the solution :)<br />
<br />
In my 1st post, i said that computer behind linksys were able to ping computer behind ISA, but it wasnt true.<br />
The linksys was set to NAT when i was doing those tests.<br />
<br />
While the linksys was set to Router, even ping didnt work.<br />
I added the route on all 3 DNS and the ISA computer and now I can ping, but still cannot resolve DNS names.<br />
<br />
Do you think this is something with the ISA server?<br />
<br />
Thank you
</div>


<div>
Isa is the dns ?<br />
If yes than you have to create rules to allow dns queries from linksys lan<br />
<br />
If not chechk the routing table on dns server and try to ping and tracert a client on linksys lan<br />

</div>


<div>
Can we take a step back here?<br />
<br />
ISA is not a router so adding the internal subnet to the ISA internal network adaptor only tells ISA to expect traffic from that new subnet to originate on its internal nic. if you have a router on the inside of ISA then you will need to add static routes on the ISA server (at the OS level) as well as adding them to the ISA config. Have you done this already?<br />

</div>


<div>
No, the DNS is on another computers (Domain controllers).<br />
<br />
I can ping and tracert from the DNS server to a client on the linksys LAN.<br />
Here is the result of the tracert : <br />
192.168.0.247<br />
192.168.7.10<br />
Trace complete.<br />
<br />
So only two hop. &nbsp;Can ping but still cannot resolve DNS names...
</div>


<div>
what do you see in the isa realtime log when you try to call something by its dns name?
</div>


<div>
Initiated Connection<br />
Log type: Firewall service <br />
Status: The operation completed successfully. &nbsp;<br />
Rule: Allow DNS from ISA Server to selected servers <br />
Source: Local Host ( 192.168.0.1:1381) <br />
Destination: Internal ( 192.168.0.8:53) <br />
Protocol: DNS <br />
<br />
<br />
Closed Connection <br />
Log type: Firewall service <br />
Status: A connection was abortively closed after one of the peers sent a RST segment. <br />
Rule: &nbsp;<br />
Source: Local Host ( 192.168.0.1:59991) <br />
Destination: Internal ( 192.168.0.8:53) <br />
Protocol: DNS <br />
<br />
Thats the only thing i saw. &nbsp;Not much.<br />
<br />

</div>


<div>
Try to do so:<br />
<br />
1) on linksys set the dns address (it should be configurable) to the isa lan dns address. ( 192.169.0.8 ?).<br />
To be sure repeat this AFTER point 2 with the second Dns (0.9 or 0.15)<br />
<br />
2) Set on one computer in the linksys lan the address of the linksys as Dns server (192.168.7.1)<br />
In this way you sholud be able to ping from that client to any client on the isa lan by using the name.<br />
Try to ping first the only hostname and then the FQDN (e.g. hostname.domainname.suffx)<wbr /> where domainname.suffix is the Active Directory domain name<br />
<br />

</div>


<div>
Keith : I created a rule FROM internal &amp;&nbsp;localhost TO internal &amp;&nbsp;localhost allowing all outbound traffic.<br />
I can now ping the FQDN! but not the simple hostname.<br />
<br />
Point-In-Cyberspace : DNS is already configured on the linksys to 192.168.0.8 (the isa LAN dns address).<br />
I tried with the dns server 192.168.7.1 on computer behind linksys but same result (can ping FQDN but not the simple hostname).<br />
<br />
I think we are coming closer to a solution. &nbsp;Is there a way to make it ping without the domain name?<br />

</div>


img2.JPG

img1.JPG

<div>
If you can ping the fqdn (looked up by DNS) but not the simple name it may be a netbios problem.<br />
<br />
From a cmd prompt, can you type in 'nslookup simple_server_name' - what is returned? The IP address?<br />
Open the ISA GUI - select monitoring - logging - start query. Now try the ping simple-hostname - what do you see in the ISA log?
</div>


<div>
Also, you may need to enable RPC within the ISA System Policy.
</div>


<div>
Thank you guys!<br />
It works with the DNS suffixes.<br />
But instead, i added the computer to the domain and now i can ping with the simple DNS name.<br />
<br />
Now, must find a way to make my linux work with that!<br />
Linux is on a 255.255.252.0 network while the computer behind linksys is in a 255.255.255.0 network.<br />
I can't ping it, and i see on the linux the following :<br />
martian destination 0.0.0.0 from 192.168.0.247, dev eth0.<br />
<br />
But that might need to create another topic for that.<br />
<br />
Thank you again!
</div>


<div>
Linux? - wasn't he in Peanuts with a blanket?
</div>


<div>
I think that i'll search this other question too ;)<br />

</div>


<div>
<div class="content wysiwyg-content">
Hi,<br />
<br />
I want to add a new subnet to our internal network. &nbsp;I have an ISA firewall in front of all. &nbsp;I installed a linksys inside the ISA network.<br />
The topology is the following : Internet - ISA - linksys<br />
<br />
Computer behind linksys are able to ping computer behind ISA with the IP but NOT with the DNS names.<br />
Computer behind linksys are able to go on the internet since ISA is forwarding them correctly to the external DNS.<br />
<br />
In ISA, i added the new subnet network addresses to the Internal Network. &nbsp;Is there something else i should configure?<br />
<br />

</div>
</div>


Hi,

I want to add a new subnet to our internal network.  I have an ISA firewall in front of all.  I installed a linksys inside the ISA network.
The topology is the following : Internet - ISA - linksys

Computer behind linksys are able to ping computer behind ISA with the IP but NOT with the DNS names.
Computer behind linksys are able to go on the internet since ISA is forwarding them correctly to the external DNS.

In ISA, i added the new subnet network addresses to the Internal Network.  Is there something else i should configure?



Routing inside ISA network

Microsoft Forefront, formerly known as Internet Security and Acceleration Server (ISA Server), is a network router, firewall, antivirus program, VPN server and web cache that runs on Windows servers. It includes identity management and protection systems, and discontinued systems for threat management and network protection, along with protection for Sharepoint and Exchange. The scope of discussions includes forward and reverse proxy, application and service publishing, virtual private networks (VPNs), outbound access rules, SSL certificates and network routing within either a single node or an highly-available array pairing.

Microsoft Forefront ISA Server

Networking is the process of connecting computing devices, peripherals and terminals together through a system that uses wiring, cabling or radio waves that enable their users to communicate, share information and interact over distances. Often associated are issues regarding operating systems, hardware and equipment, cloud and virtual networking, protocols, architecture, storage and management.

Networking

A router is a networking device that forwards data packets between computer networks. Routers perform the "traffic directing" functions on the Internet. The most familiar type of routers are home and small office cable or DSL routers that simply pass data, such as web pages, email, IM, and videos between computers and the Internet. More sophisticated routers, such as enterprise routers, connect large business or ISP networks up to the powerful core routers that forward data at high speed along the optical fiber lines of the Internet backbone. Though routers are typically dedicated hardware devices, use of software-based routers has grown increasingly common.