|[ < ]||[ > ]||[ << ]||[ Up ]||[ >> ]||[Top]||[Contents]||[Index]||[ ? ]|
The best solution for this problem is to recompile Emacs, making sure to either link dynamically (if available on your operating system), or include the `-lresolv'.
If you do not have the disk space or the appropriate permissions to
recompile Emacs, another alternative is using the `nslookup'
program to do hostname resolution. To turn this on, set the variable
url-gateway-broken-resolution in your `~/.emacs' file. This
runs the program specified by
nslookup" to do hostname resolution. This program should
expect a single argument on the command line -- the hostname to resolve,
and should produce output similar to the standard Unix `nslookup'
Name: www.cs.indiana.ed Address: 188.8.131.52
NOTE: XEmacs and Emacs 19.22 or later have patches to enable native
TERM networking. To enable it,
#define TERM in the
appropriate s/*.h file for the operating system, then change the
SYSTEM_LIBS definition to include the `termnet' library that
comes with the latest versions of TERM.
If you run into any problems with the native TERM networking support in Emacs or XEmacs, please let firstname.lastname@example.org know, as he is responsible for the original support.
Emacs/W3 has support for using the gateway mechanism for certain
domains, and directly connecting to others. The variable
url-gateway-local-host-regexp controls this behaviour. This is a
regular expression (4) that matches local hosts that do
not require the use of a gateway. If
nil, then all connections
are made through the gateway.
Emacs/W3 supports several methods of getting around gateways. The
url-gateway-method controls which of these methods is
used. This variable can have several values (use these as symbol names,
not strings), ie: `(setq url-gateway-method 'telnet)'. Possible
telnetmethod, but uses `rlogin' to log into the remote machine without having to send the username and password over the wire every time.
nilthen you will be asked for the passward, otherwise it will be used as the password for authenticating you to the SOCKS server.
socks-network-aliasesand Connection type can be
nilin which case a direct connection is used, or it can be an alias from
socks-server-aliasesin which case that server is used as a proxy.
Emacs/W3 should now be able to get outside the local network. If none of this makes sense, its probably my fault. Please check with the network administrators to see if they have a program that does most of this already, since somebody somewhere at the company has probably been through something similar to this before, and would be much more helpful/knowledgeable about the local setup than I would be. But feel free to mail me as a last resort.
|[ << ]||[ >> ]||[Top]||[Contents]||[Index]||[ ? ]|