How to use NXHost over dynamic slip?
Michael Pizolato
:I have a slip connection which gets assigned an IP address on the
:fly when I make contact with my host site. It works fine for Pop,
:rlogin, and even X windowing (with co-Xist). But when I try to
:launch a NeXT app remotely and display back to my machine using
:NXHost, I can't do it. Here's an example...
:
:whimsy:/Users/paul> who am i whimsy!paul ttyp0 Mar 21 10:45
:(umslts1_20.umsl.edu) whimsy:/Users/paul> open -a
/NextApps/Edit.app/Edit
:-NXHost umslts1_20.umsl.edu open: can't open connection to Workspace
:on umslts1_20.umsl.edu
:
:Both machines are running 3.3. I've set the security options in
:Preferences for public window server, and I can't think of what
:else would be the problem.
:
:This isn't critical, but it would be nice to get it working. Any
:ideas?
Since the address is dynamic, the network is not able to resolve
your host name into an IP address. If you know what address you
have been assigned in each session, you might be able to use the
address instead of the host name as the argument to -NXHost. Or
you can "steal" a permanent IP address, which won't solve the name
translation problem but will let you write scripts and stuff with
constant IP addresses in them. Here's how:
I have a slip account for my home computer, a PC running Windoze
(ack! poo!). Don't bug me about it - until I can afford more
memory NS would kill the poor thing. Anyway, once I've connected
to my provider, I issue a SLIP (actually CSLIP) command to their
router. The command allows me to specify an IP address as a command
line parameter. So, one day I figured out the highest-numbered IP
address my provider uses in the address pool, and I use that address
every time I connect.
Since the pool is allocated from the bottom, empty slots are always
filled, and the entire pool is never in use at once (and if it
were, I couldn't use _any_ of the addresses anyway), I have a
kinda-permanent IP address for my machine (at least until somebody
else figures out the same trick :-). It's cheating, but it works
for me, and it beats paying the extra $20/month a real permanent
IP address would cost.
Hope this is helpful.
Thanx,
Michael
--
Anderson Financial Systems Inc. Michael_...@afs.com
Suite 106 Vox: 215/653-0911
909 Sumneytown Pike
Springhouse, PA 19477
Paul J. Sanchez
when I make contact with my host site. It works fine for Pop, rlogin,
and even X windowing (with co-Xist). But when I try to launch a NeXT
app remotely and display back to my machine using NXHost, I can't do
it. Here's an example...
whimsy:/Users/paul> who am i
whimsy!paul ttyp0 Mar 21 10:45 (umslts1_20.umsl.edu)
whimsy:/Users/paul> open -a /NextApps/Edit.app/Edit -NXHost umslts1_20.umsl.edu
open: can't open connection to Workspace on umslts1_20.umsl.edu
Both machines are running 3.3. I've set the security options in
Preferences for public window server, and I can't think of what else
would be the problem.
This isn't critical, but it would be nice to get it working. Any
ideas?
--
--paul pa...@whimsy.umsl.edu
=================================================================
The Law, in its majestic equality, forbids the rich, as well
as the poor, to sleep under the bridges, to beg in the streets,
and to steal bread.
-- Anatole France
=================================================================
Stephen J. Perkins
(Jerry Weiss) writes:
> In article <3kndfr$2...@shelob.afs.com>,
> Michael Pizolato <mic...@afs.com> wrote:
> >Paul J. Sanchez writes
> >:I have a slip connection which gets assigned an IP address on the
> >:fly when I make contact with my host site. It works fine for Pop,
> >:rlogin, and even X windowing (with co-Xist). But when I try to
> >:launch a NeXT app remotely and display back to my machine using
> >:NXHost, I can't do it. Here's an example...
> >
> [munch]
>
> I think Micheal is on the right track. The Dynamic Slip line has
> an IP address and in the above case a Hostname (umslts1_20.umsl.edu)
> but the problem lies with the machine where the window server runs.
> It understands what it's IP address is, but it doesn't recognize
> the dynamic hostname as being itself. It probably has the hostname
> built from /etc/hostconfig and /etc/resolv.conf, and perhaps
> something in Netinfo. Neither is likely to be the dynamic hostname.
>
A long time ago it was posted that:
===============================================================
# Let the nmserver know the fruits of our network configuration
# endeavor. This allows NXHost connections.
pid=`ps cax | egrep nmserver | awk '{print $1;}'`
if [ -n "$pid" ]; then
echo "Reinitializing nmserver's network portion" > /dev/console
kill -USR2 $pid
fi
=================================================================
would do the trick. Good luck!
- Steve
P.S. Credit goes to Glenn Brown for this.
---
==============================================================
Stephen J. Perkins | per...@cps.msu.edu
Dept. of Comp. Science | NeXT, MIME, finger for PGP
Michigan State University | NeXT OS 3.2 using PPP-2.2
Jerry Weiss
I think Micheal is on the right track. The Dynamic Slip line has
an IP address and in the above case a Hostname (umslts1_20.umsl.edu)
but the problem lies with the machine where the window server runs.
It understands what it's IP address is, but it doesn't recognize
the dynamic hostname as being itself. It probably has the hostname
built from /etc/hostconfig and /etc/resolv.conf, and perhaps
something in Netinfo. Neither is likely to be the dynamic hostname.
This is also the root of the problem as to why recieving mail on
a dynamic slip line requires PopOver or its kin. [Not that you'd
really want direct mail delivery on sporadically connected host.
As far as I recall, open requires a Hostname. An IP address
cannot be used.
There's probably a way to make things work, but I lack the
necessary level of Unix Hackdom to achieve this.
--
Jerry S. Weiss
j-w...@nwu.edu
Dept. Medicine, Northwestern Univ. Medical School, Chicago, Illinois
%SYSTEM-S-PHALOKTARG, Phasers Locked on Target, Ready to Fire
GH Chinoy
I tool Steve's advice and executed the nmserver reinitialization
apres establishing PPP and telnet'd over to our servers and tried:
/LocalApps/OmniWeb.app/OmniWeb -NXHost dialin-89
and /LocalApps/OmniWeb.app/OmniWeb -NXHost dialin-89.wustl.edu
No luck.
This was the error I got back:
DPS client library error: Could not form connection, host dialin-89
What's this mean? Is this a confirmation that my machine doesn't
recognize the dynamically assigned symbolic name (dialin-89.wustl.edu)
and therefore NXHost isn't going to work?
Both machines (mine-ppp & remote) are NeXTstation turbos running
3.2.
___ __________________________________________________________
/\__\ G. Hussain Chinoy
\/__/
NEXTSTEP, hus...@artsci.wustl.edu
baby http://www.artsci.wustl.edu/~hussain/
On 22 Mar 1995, Stephen J. Perkins wrote:
> In article jwe...@casbah.acns.nwu.edu
Bruce Gingery
J. Perkins) writes:
}~ In article <3knmlr$c...@news.acns.nwu.edu> jwe...@casbah.acns.nwu.edu
}~ (Jerry Weiss) writes:
}~ > In article <3kndfr$2...@shelob.afs.com>,
}~ > Michael Pizolato <mic...@afs.com> wrote:
}~ > >Paul J. Sanchez writes
}~ > >: I have a slip connection which gets assigned an IP address on
}~ > >: the fly when I make contact with my host site. It works fine
}~ > >: for Pop,rlogin, and even X windowing (with co-Xist). But when
}~ > >: I try to launch a NeXT app remotely and display back to my
}~ > > : machine using NXHost, I can't do it. Here's an example...
}~ > [munch]
}~ >
}~ > I think Micheal is on the right track. The Dynamic Slip line has
}~ > an IP address and in the above case a Hostname
}~ > (umslts1_20.umsl.edu)
}~ > but the problem lies with the machine where the window server runs.
}~ > It understands what it's IP address is, but it doesn't recognize
}~ > the dynamic hostname as being itself. It probably has the hostname
}~ > built from /etc/hostconfig and /etc/resolv.conf, and perhaps
}~ > something in Netinfo. Neither is likely to be the dynamic
}~ > hostname.
}~ A long time ago it was posted that:
}~ ===============================================================
}~ # Let the nmserver know the fruits of our network configuration
}~ # endeavor. This allows NXHost connections.
}~
}~ pid=`ps cax | egrep nmserver | awk '{print $1;}'`
}~ if [ -n "$pid" ]; then
}~ echo "Reinitializing nmserver's network portion" > /dev/console
}~ kill -USR2 $pid
}~ fi
}~ =================================================================
}~
}~ would do the trick. Good luck!
}~.... Credit goes to Glenn Brown for this.
ALSO...
If you want hostname *only* resolution, you might wish
to create .:/machines entries for the dial-up 'machines'
in NetInfo, especially if your machine does not establish
or recognize a domain name which would be auto appended
with a 'domain' entry in /etc/resolv.conf
+-+
Bruce Gingery Total System Software Cheyenne, WY USA
We do consulting over Internet. E-Mail
t...@TotSysSoft.com for quotes or more info.
Homepage under construction <URL:http://turnpike.net/metro/bagingry/>
NEXT IN LINE magazine staff technical writer
Bruce Gingery <bgin...@Wyoming.COM> OR <br...@TotSysSoft.com>
Multimedia: NeXTmail(tm) preferred MIME-mail welcome
Paul J. Sanchez
remain unable to use NS apps remotely. I must have some other oddity
in my configuration.
Thanks anyway.