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
patchsvr(1M)						  System Administration Commands					      patchsvr(1M)

NAME
patchsvr - set up a Sun Update Connection Proxy SYNOPSIS
/usr/sbin/patchsvr setup [-c cache-location] [-d] [-h] [-l] [-p update-source-url] [-s pw-file-location] [-u user-name] [-x web-proxy- host:port] /usr/sbin/patchsvr start /usr/sbin/patchsvr stop /usr/sbin/patchsvr enable /usr/sbin/patchsvr disable DESCRIPTION
The patchsvr command enables you to set up a Sun Update Connection Proxy on your intranet. The setup subcommand configures the Sun Update Connection Proxy. The start and stop subcommands start and stop the Sun Update Connection Proxy. Finally, the enable and disable subcom- mands permit you to start up and prevent startup of the Sun Update Connection Proxy at boot time. The Sun Update Connection Proxy was previously called local patch server. Note - The Sun Update Connection Proxy supports client systems that use the Sun Update Connection, System Edition software and the Sun Patch Manager 2.0 software. A Sun Update Connection client system is not compatible with the older local patch server feature asso- ciated with the Sun Patch Manager 2.0 software. Configuring Your Sun Update Connection Proxy By default, Update Manager expects that your local systems are connected, via the Internet, to the Sun update server to be analyzed and to receive updates. By using a Sun Update Connection Proxy instead, you can minimize the Internet traffic and serve your local systems from a update server on your intranet. The system you choose to act as the Sun Update Connection Proxy must be running at least the Developer Solaris Software Group of the Solaris 10 Operating System. You must also install the Sun Update Manager 1.0 software and the Sun Update Connection Proxy software. The use of a Sun Update Connection Proxy addresses security concerns and reduces the amount Internet traffic between the Sun update server and your client systems. For instance, instead of having to download updates and metadata from the Sun update server to each of your systems, the data is downloaded to the Sun Update Connection Proxy the first time that a client system requests an update. After the update data is stored on your Sun Update Connection Proxy, the transfer of update data to your system for analysis is done over your intranet instead of over the Internet. You can configure a chain of update servers on your intranet. The last link in the chain of local servers can point to the Sun update server or to a local collection of updates. By using this chain of servers, an update download request from your system to its primary update server can be forwarded to other servers in the chain in an attempt to fulfill the request. So, if your system's primary server can- not locate an update, the server makes the same request of the next server in the chain to see if the update is stored there. If the update is found, it is downloaded to the system. If the update is not found, the request continues along the chain until the update is found or the terminal point in the chain is reached. Each server in the chain stores the updates found on another server in the chain based on the download request. So, an update that is not initially found on your local server will be downloaded to your local server and stored before being downloaded to the client system. Your Sun Update Connection Proxy must specify the source of updates to use. By default, the server obtains updates from the Sun update server, but it can also obtain updates from another update server in the chain or from a collection of updates on your system. You must specify the URL that points to the collection of updates. By default, the Sun update server is the source of updates. The URL is: https://getupdates.sun.com/solaris/ Note that this URL must appear as a single line. This URL must point to another server in the chain or to a collection of updates on the local system. This URL cannot be null. Starting and Stopping Your Sun Update Connection Proxy The patchsvr start command starts the Sun Update Connection Proxy. You can also enable the boot-time startup of the Sun Update Connection Proxy by running patchsvr enable. The patchsvr stop command stops the Sun Update Connection Proxy. You can also disable the boot-time startup of the Sun Update Connection Proxy by running patchsvr disable. Before you use your Sun Update Connection Proxy for the first time, you must run the patchsvr start command. Use these commands when you want to change the configuration of your Sun Update Connection Proxy. Before you use the patchsvr setup command to change the configuration parameter values, you must stop your Sun Update Connection Proxy. Then, you can update the configuration val- ues. Finally, you must restart the Sun Update Connection Proxy. OPTIONS
The following options are supported for the patchsvr setup command: -c cache-location Specifies the location of the server's cache, also known as the update repository. This is the directory in which downloaded updates are stored on the Sun Update Connection Proxy. You must specify a full path to the cache loca- tion. By default, the cache location is file:/var/sadm/spool/patchsvr. Ensure that this update repository has 2 Gbytes of free disk space available to store downloaded updates. -d Resets the Sun Update Connection Proxy configuration settings to the default values. -h Displays information about the command-line options. -l Lists the configuration settings for the update server. -p update-source-url Specifies the URL that points to the collection of updates. By default, the URL points to the Sun update server: https://getupdates.sun.com/solaris/ Note that this URL must appear as a single line. -s pw-file-location Specifies the path of the proxy password file in which you have stored your proxy password. You must put the password in a file rather than specifying it on the command line because command-line information is visible via the ps command. -u user-name Specifies the user name required for web proxy authentication. -x web-proxy-host:port Specifies the local web proxy. If the Sun Update Connection Proxy is behind a firewall, use this option to specify the web proxy that accesses the Internet. Get the name of the web proxy, web-proxy-host, and its port, port, from your system administrator or network administrator. The default port value is 8080. Do not use this option if you are accessing update data from a collection of updates on the Sun Update Connection Proxy. EXAMPLES
Example 1: Changing the Cache Location # patchsvr setup -c /var/update/cache Example 2: Specifying the Sun Update Server as the Source of Updates # patchsvr setup -p https://getupdates.sun.com/solaris/ The Sun update server is the default source of updates. Example 3: Specifying a Sun Update Connection Proxy as the Source of Updates # patchsvr setup -p http://updatesvr1:3816/solaris/ Specifies the system called updatesvr1, a Sun Update Connection Proxy, as the source of updates. Example 4: Specifying a CD as the Source of Updates # patchsvr setup -p file:/cdrom/cdrom0 Specifies the CD mounted from the first CD-ROM drive of the local system as the update source. Example 5: Specifying a Web Proxy # patchsvr setup -x webproxy:8080 Specifies the host name, webproxy, and port, 8080, of the web proxy that your Sun Update Connection Proxy uses to connect to the Internet. Example 6: Specifying a User Name and Password for Web Proxy Authentication # (umask 77 ; vi /tmp/password) # patchsvr setup -u terry -s /tmp/password # rm /tmp/password While in a subshell, you create a temporary file that is not readable by others and put the password in that file. Next, you specify the user name, terry, and location of the password file, /tmp/password, used to authenticate the web proxy that your Sun Update Connection Proxy uses to connect to the Internet. Then, you delete the temporary file now that the web proxy authentication is specified. Example 7: Resetting the Configuration Settings to the Default Values # patchsvr setup -d Example 8: Listing the Configuration Settings for Your Sun Update Connection Proxy # patchsvr setup -l Patch source URL: https://getupdates.sun.com/solaris/ Cache location: /var/sadm/spool/patchsvr Web proxy host name: mars Web proxy port number: 8080 Shows the configuration settings, which include information about the source of updates, the location of the cache directory, and, if needed, a web proxy and port. Example 9: Starting the Sun Update Connection Proxy # patchsvr start Example 10: Stopping the Sun Update Connection Proxy # patchsvr stop Stops your Sun Update Connection Proxy. While the update server is stopped, you can change the configuration settings for your Sun Update Connection Proxy, then restart it. Example 11: Enabling the Boot-Time Startup of the Sun Update Connection Proxy # patchsvr enable Example 12: Disabling the Boot-Time Startup of the Sun Update Connection Proxy # patchsvr disable ATTRIBUTES
See the attributes(5) man page for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWpsvru | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
smpatch(1M), attributes(5) Sun Update Manager 1.0 Administration Guide SunOS 5.10 12 May 2005 patchsvr(1M)
All times are GMT -4. The time now is 05:20 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy