Two squids don't want to connect :((

Two squids don't want to connect :((

Post by Pelex Y » Sat, 04 Jul 1998 04:00:00



Hi all.
One question.
Got a problem to connect two squids.
There are two hosts. One has connection to Internet, second in local
(10.x.x.x) net.
I tried several configurations, any way second doesn't see first and
can't connect to it.

Can anybody advice smth.,  or tell the simplest configurations.

--
Best wishes.
------------
Pelex

 
 
 

Two squids don't want to connect :((

Post by David Malo » Sat, 04 Jul 1998 04:00:00



>There are two hosts. One has connection to Internet, second in local
>(10.x.x.x) net.
>I tried several configurations, any way second doesn't see first and
>can't connect to it.
>Can anybody advice smth.,  or tell the simplest configurations.

Can you ping the 10.x.x.x one from the other? I prseume you've
checked this, but just to be certain.

        David.

 
 
 

Two squids don't want to connect :((

Post by David Malo » Sat, 25 Jul 1998 04:00:00



>Hi all.
>One question.
>Got a problem to connect two squids.
>There are two hosts. One has connection to Internet, second in local
>(10.x.x.x) net.
>I tried several configurations, any way second doesn't see first and
>can't connect to it.

Have you checked the following from both machines:

        1) You can ping the other using the IP address.
        2) You can ping the other using the hostname.
        3) You can telnet to the port squid is supposed to
                be running on using the hostname (eg. telnet machine.net 8080)

If you get stuck at stage 1 it is probably a routing problem.
Check the output of netstat -nr. At stage 2 is is probably a
DNS problem - check you /etc/host.conf and /etc/resolv.conf.
At stage 3, it means squid isn't running in the correct place.
If all of there work you've probably got a squid problem, so
you should probably check the squid docs, web pages and mailing
list.

        David.

 
 
 

1. Talk refused to talk:(:(:(:(

Hello there people:)...
  I had linux kernel 1.2.8 installed in my system. I have a SLIP/PPP
connection using either dip (for SLIP) or pppd/chat (for PPP).
  Now, Most of my network stuff are working fine without any problem at all
except talk. Talk works fine for local chatting. No problem at all. The
problem is when ever I call out to other machine (using the SLIP/PPP line),
nothing has ever happen. It got as far as Checking invitation stuff. Never
more.
  Just out of curiosity I ran netstate to check the udp connection whenever
I have talk running. Running locally (talk that is) I got output as follow:

Active Internet connections
Proto Recv-Q Send-Q Local Address          Foreign Address        (State)
User
udp        0      0 lucifer.newpaltz.:1328 *:*                    

Which I presumed opened by talk (only one here because the other side hadn't
responded to the call yet).  I also get the same thing whenever I call
someone outside my system to talk. Of course, it never got to the other
system (I was waiting on the other system using telnet for the talk request,
never got there. And I had made sure that mesg was y).

Now when I call *IN* from other system (telnet to another system and run
talk over there to my system), I have (on my system) output as follow:

Active Internet connections
Proto Recv-Q Send-Q Local Address          Foreign Address        (State)
User

And also from netstat -a, I could find talk/ntalk were still listening.
Seems to me the call from outside didn't get through.

Now, since I haven't done anything to configure talk specifically, is there
anything I have to do to make this connection possible. Since I can't talk
to outside nor can I receive talk request from other hosts, I'm under the
assumption that my talk program somehow is not configured properly.

Any configuration file I have to check?
man, faq, howto, etc to refer to this kind of error?
May be replace my talk/ntalk/talkd/ntalkd with something else and where to
find it/them?
Does it depend on something in the kernel that I have to enable during the
compile time?
Wrong version altogether with the kernel?
Is it possible that talk needs long time to make the connection? (None of my
other stuff that I know of behave like this).
May be my inetd is broken?
If so, how do I check for it?
And where to find the latest version of it?

And while I'm at it, what's the latest version of talk?
Where to find it?
Is there a better chatting program that's backward compatible with talk?
Meaning that the program has more features than talk but at the same time
can be used to communicate with other regular talk program whenever the
program is not available on the other host.

--
Send comment and reply to:



2. help: IBM PCI/SCSI II

3. Squid does not work :('

4. Win95 Router ?

5. ATI Radeon 9200SE - X don't works :(

6. Intel EtherExpress problem

7. ELF binaries sometimes don't run :(

8. Archive FT-60 supported?

9. Emacs don't want to run under XWindows :(

10. Setup and pkgtool don't work no more :(

11. I don't understand disks. :( HELP!

12. Austin + Linux + X : don't work :(

13. :( Don't know how to install NE2000 in Linux