[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference noted::seal

Title:SEAL
Moderator:GALVIA::SMITH
Created:Mon Mar 21 1994
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1989
Total number of notes:8209

1803.0. "Telnet very, very slow" by LISVAX::CORREIA_C (CELIA CORREIA @XIP) Mon Feb 17 1997 16:31

 
 When I try to telnet to internal interface of the alta vista firewall 
I receive a very, very slow answer. The same happens if I try to telnet 
to any machine on the external (red) network.

 Does anyone know why this happens ?

 This happens with Digital UNIX V4.0A and Alta Vista Firewall for UNIX V2.1.
 It also happens with Digital UNIX V3.2C and AVFU V2.0.

 Many thanks in advance.

 Celia  
T.RTitleUserPersonal
Name
DateLines
1803.1BIGUN::nessus.cao.dec.com::MayneWake up, time to dieMon Feb 17 1997 17:003
Your DNS is misconfigured.

PJDM
1803.2Telneting IP addressLISVAX::CORREIA_CCELIA CORREIA @XIPTue Feb 18 1997 14:0810
    > your DNS is misconfigured
    
    Even if I'm just telneting the ip address (instead of the fully
    qualified name) ?
    
    Thanks in advance 
    C�lia
    
    
    
1803.3Telnet ok, but ...LISVAX::CORREIA_CCELIA CORREIA @XIPTue Feb 18 1997 15:3312
    
     After setting up DNS everything worked well.
    Thank you.
    
    Still, I don't understand the relation between DNS and telnet,
    when I use IP addresses (telnet x.y.z.c) instead of DNS names.
    
    Is DNS always necessary for the telnet proxy ? Or is it necessary for
    screend ?
    
    C�lia
             
1803.4BIGUN::nessus.cao.dec.com::MayneWake up, time to dieTue Feb 18 1997 17:234
Even if you telnet using the numbers, the system will try and do a reverse 
lookup on the address. If DNS isn't set up properly...

PJDM
1803.5Telnet very slowLISVAX::CORREIA_CCELIA CORREIA @XIPThu Feb 20 1997 05:3545
And what he does when the address is outside his domain ??, he will ask the 
secondary external server ?? I'm making this question for one reason, this 
particular configuration in one  client , for intalling the firewall :

	Node1						node2
	-------
	!     !WWW server		    Internet  ------- 		
	!     !DNS Primary server	     router   !      ! 
	-------					      ------
	   !						!
	------------------------------------------------------
				!  node3
			     --------	
			     !      !Firewall
			     !      !
			      -------	
				!	
	------------------------------------------------------
		!node4					!node5
	     --------				     --------
	     !	    !DNS server Internal	     !       !
	     !	    !mailhub internal		     ! PC    !
	      -------				      --------



Now I can telnet ftp the internal firewall interface, but when the pc asks 
for an external internet address it can't solve and becames very slow.

In the firewall configuration I put the secondary external server as the node 1 
(as in the picture). I have the internal dns server properly (with forwarder
pointing to the firewall , the slave is in the named.boot )

Is somthing missing ?? from the pc I even can't telnet the node2 (the internet
router ) but the response is imediate if I trie from the firewall ....



Many thanks in advance for you replies,

C�lia




1803.6red hosts in your domainNETRIX::"[email protected]"Sebastian L�lsdorfThu Feb 20 1997 09:3414
Hello Celia!

If I'm understanding you right, the problems only occur when you are trying
to telnet from the bluenet to systems on your rednet?

I assume your rednet has the same DNS domain name as the bluenet? In this
case, your internal DNS server will not make any use of its forwarders line,
since it feels authoritative for the domain! Therefore you must enter all your

red hosts of your domain into the internal DNS database files too.

Does that help?
Sebastian
[Posted by WWW Notes gateway]
1803.7Telnet very,very slowLISVAX::CORREIA_CCELIA CORREIA @XIPThu Feb 20 1997 11:0013
Hi Sebastian, 

You are rigth,  and I've donne that, but my problem was that I could'nt 
resolve any dns address outside my domain, and finally I find out the real 
cause on this was that one router :-( didn't allow queries from the firewall,
only from other previous dns server machine.

Finaly everything works now .....   ;-)

Many thanks to  all , for your most precious help
C�lia