Sponsored Content
Special Forums IP Networking Using Another Account as Internet Proxy Post 302963764 by hicksd8 on Tuesday 5th of January 2016 04:38:42 PM
Old 01-05-2016
So your local servers are using the bank of purchased static ip's and are effectively directly on the internet?

If when trying to connect locally you are referencing a nodename, then that nodename will need to be resolved to an ip address. If your DNS service is external (and unreliable and perhaps provided by your ISP) then if it becomes unreachable every so often it would affect your local connectivity too. Just a thought at this early stage.

Do you know where your local nodes get their DNS settings from? Are they acquired through DHCP?

If the timeout is caused by DNS failure then setting local resolution through /etc/hosts file entries might help.

What O/S's are we talking about here?

---------- Post updated at 09:30 PM ---------- Previous update was at 09:21 PM ----------

Stating the obvious, LAN connections do not need any ISP or WAN involvement once the connection is established.

I may well be wrong but my experience would tell me to look at the DNS service reliability and/or the actual DNS settings and where they are acquired. This type of timeout connection issue bears all the hallmarks of a DNS screw up.

Let's hope we soon get other input from other forum members. There's probably questions that I've forgotten to ask.

---------- Post updated at 09:35 PM ---------- Previous update was at 09:30 PM ----------

You could configure another system on your LAN as an internet proxy server if you believe for some reason that it won't suffer the same issue. You'd then need to configure all your workstations to use that proxy (or autodetect that proxy).

---------- Post updated at 09:38 PM ---------- Previous update was at 09:35 PM ----------

You could interrogate your systems to see what primary DNS and secondary DNS server ip addresses they are using. Then set up a couple of machines to ping each of these continuously. See if they are still successfully pinging when the problem occurs or whether the DNS servers are unreachable at that time.
 

6 More Discussions You Might Find Interesting

1. IP Networking

Software/tool to route an IP packet to proxy server and capture the Proxy reply as an

Hi, I am involved in a project on Debian. One of my requirement is to route an IP packet in my application to a proxy server and receive the reply from the proxy server as an IP packet. My application handles data at the IP frame level. My application creates an IP packet(with all the necessary... (0 Replies)
Discussion started by: Rajesh_BK
0 Replies

2. Cybersecurity

Setting up an Internet proxy

Setting up an Internet proxy - need help Hi guys In the past I had set a computer to act as an Internet proxy. This would be multihomed, and running dansguardian, tinyproxy and firehol. Then webmin would be used as interface. By time I realised that this system is far from effective.... Is... (0 Replies)
Discussion started by: ramon82
0 Replies

3. UNIX for Dummies Questions & Answers

need a stable proxy server or free ssh account to visit blocked sites, who can help?

In our country, blogspot.com, twitter.com facebook.com....and more excellent sites are blocked by the Goverment FireWall, who can help me ? thanks a lot for your kind. (2 Replies)
Discussion started by: shuke
2 Replies

4. Linux

SFTP an internet address from a system behind an internet proxy

I was wondering if it is possible to setup SFTP to go through the internet proxy while connecting to an internet location. Problem: Client system is behind internet proxy. SFTP to any internet location fails as there is no documented way to configure SFTP to connect to internet locations through... (4 Replies)
Discussion started by: toobrown1
4 Replies

5. UNIX and Linux Applications

SQUID proxy : How do I limit internet connectivity to X hrs/day

Hi Everyone! A friend of mine is looking for a way to limit time his kids spent on the internet. I told him he should try out Squid proxy server. He now tries to find a way to limit total time spend on the internet to "X" hours a day, at any time during the day. I remember there are built-in... (3 Replies)
Discussion started by: togr
3 Replies

6. IP Networking

Connecting via proxy chain to Upstream proxy

I need to configure a proxy on my local machine to use an upstream proxy (installed on another machine). The upstream proxy requires Digest/NTLM authorization. I want the local proxy to deal with the upstream proxy's authorization details and provides authorization free access to users that connect... (0 Replies)
Discussion started by: Russel
0 Replies
Net::Proxy::Connector::connect(3pm)			User Contributed Perl Documentation		       Net::Proxy::Connector::connect(3pm)

NAME
Net::Proxy::Connector::connect - Create CONNECT tunnels through HTTP proxies SYNOPSIS
# sample proxy using Net::Proxy::Connector::tcp # and Net::Proxy::Connector::connect use Net::Proxy; # listen on localhost:6789 # and proxy to remotehost:9876 through proxy.company.com:8080 # using the given credentials my $proxy = Net::Proxy->new( in => { type => 'tcp', port => '6789' }, out => { type => 'connect', host => 'remotehost', port => '9876', proxy_host => 'proxy.company.com', proxy_port => '8080', proxy_user => 'jrandom', proxy_pass => 's3kr3t', proxy_agent => 'Mozilla/4.04 (X11; I; SunOS 5.4 sun4m)', }, ); $proxy->register(); Net::Proxy->mainloop(); DESCRIPTION
"Net::Proxy::Connecter::connect" is a "Net::Proxy::Connector" that uses the HTTP CONNECT method to ask the proxy to create a tunnel to an outside server. Be aware that some proxies are set up to deny the creation of some outside tunnels (either to ports other than 443 or outside a specified set of outside hosts). This connector is only an "out" connector. CONNECTOR OPTIONS
"Net::Proxy::Connector::connect" accepts the following options: "out" o host The destination host. o port The destination port. o proxy_host The web proxy name or address. o proxy_port The web proxy port. o proxy_user The authentication username for the proxy. o proxy_pass The authentication password for the proxy. o proxy_agent The user-agent string to use when connecting to the proxy. AUTHOR
Philippe 'BooK' Bruhat, "<book@cpan.org>". BUGS
All the authentication schemes supported by "LWP::UserAgent" should be supported (we use an "LWP::UserAgent" internally to contact the proxy). This means we should also support NTLM, since it is supported as from "libwww-perl" 5.66. "Net::Proxy::Connector::connect" has not been actually tested with NTLM, though. Any report of success or failure with a NTLM proxy will be appreciated. HISTORY
This module is based on my script "connect-tunnel", that provided a command-line interface to create tunnels though HTTP proxies. It was first published on CPAN on March 2003. A better version of "connect-tunnel" (using "Net::Proxy") is provided this distribution. COPYRIGHT
Copyright 2006 Philippe 'BooK' Bruhat, All Rights Reserved. LICENSE
This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. perl v5.10.1 2009-10-18 Net::Proxy::Connector::connect(3pm)
All times are GMT -4. The time now is 04:11 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy