Re: EUServe
Hi,
Thanks for the help but i have allready prepared my network (I use wingate
on it).
Sorry I should have given you more info.
The problem I am having is the euserve won't start up without a connection
to the net, it gives a winsock error.
--PatRat (Thomas Parslow)
-- ()___()
-- (o o)
-- =\O/=
-- Rat Software
-- http://free.prohosting.com/~rats/ratsoft/
-----Original Message-----
From: Hawke' <mdeland at GEOCITIES.COM>
To: EUPHORIA at LISTSERV.MUOHIO.EDU <EUPHORIA at LISTSERV.MUOHIO.EDU>
Date: 09 December 1998 01:08
Subject: Re: EUServe
>Thomas Parslow wrote:
>> Just downloaded EUserve and it looks interesting.
>thanx!
>
>> I was wondering if it is possible to use it without connecting to the
>> internet, so that I could use it on my TCP/IP LAN without connecting to
the
>> internet all the time.
>> Whenever I try this it gives an error.
>it should work fine.
>i am running a gateway/tcpIP/ipx network here myself...
>i can telnet to any of the machines on the lan, get outbound telnet
>through the gateway server, and transfer files/play games using
>either tcpip or ipx.
>it works fine for me. and it should for you as well.
>what you need to have setup tho, is a unique IP address
>for each machine on the lan.
>generally, internal IP addresses are allocated with the
>prefix 192.168.0.??? and in my case, the server gets the 1.
>ie: the gateway machine is 192.168.0.1 and if i telnet to
>that address, while the EUServ is running on port 9000,
>it logs me into the EUServ. if i telnet to 192.168.0.1
>on port 23, then i can leapfrog from there to any other
>telnet address, thusly escaping the internal lan and reaching
>the internet if the gateway server is 'online'.
>
>once you have assigned unique IP addresses to the rest of
>the machines on the lan, like the machine i am actually
>typing this email in is 192.168.0.2, you then need to
>enter those IP addresses into your Hosts file.
>
>it also helps to give each machine on the lan a name
>and enter that into the Hosts file as well.
>
>this machine is called Blarg (ya gotta luv dat name :).
>so in the Hosts file on *all* of the machines on the lan
>i have the following entries:
>
>127.0.0.1 localhost
>192.168.0.1 gateway
>192.168.0.2 Blarg
>etc...
>
>then, once u do that, you can do things like:
>telnet localhost 9000
>telnet blarg 9000
>telnet gateway 9000
>
>all of course, depending on where i am running the server.
>
>if the gateway server machine is running the EUServ program
>AND it's connected to the internet, then what happens is,
>anyone INSIDE the localnetwork would type:
>telnet gateway 9000
>BUT, anyone from the internet trying to reach the same
>EUServ would need to type in the dynamic IP given to us
>by our ISP (an example might be 4.38.162.139) and use
>the following line:
>telnet 4.38.162.139 9000
>
>then, we have people from the network logged in AS WELL AS
>people from the internet can be logged in.
>
>the first experiment you need to try is the following:
>boot up EUServer, using the run.bat file is generally easiest.
>then open a dosbox window and type in:
>telnet 127.0.0.1 9000
>and see if that connects to the server.
>
>if it doesn't work, i would have to assume that something in
>your network control panel tab is awfully askew, and i, without
>having a second cup o'joe in me right now, would not be
>real sure of the steps you would need to take to fix that *without*
>breaking any other settings in there you would need to connect
>to the internet.
>
>if that does work, then logout that character (quit) and try:
>telnet localhost 9000
>
>if the first step worked and the second did not work, then
>go into the \windows directory and find a file called "Hosts".
>it does NOT have an extension. it's just "Hosts".
>(or sometimes "hosts")
>edit that file with notepad,edit, whatever and add the line:
>127.0.0.1 localhost
>near the bottom of the file, after all the comments...
>
>if that line isn't there, already, it tells me that someone
>has been monkeying around, as that line is DEFAULT when you
>install win9x, and for that matter, it's usually there when
>you install win4wrkgrps and likely NT as well...
>
>save the file and (since the server should still be running)
>retry the:
>telnet localhost 9000
>command from that dos box...
>it should crank and slap you right into EUServ.
>
>once you get those two things working, we can move on
>to getting other machines, on the internal lan, to connect.
>if you cannot get either of those things to work, then stop
>here, and lemme/us know... we'll havta do sum t'inkin :)
>
>continuing...
>in that same dos box, type:
>winipcfg <enter>
>now at this point, 99% of you are going to say:
>"but that will give him his dynamic IP from his ISP and he
>won't want that!"
>ummmmmm.... no.
>once again, we are still assuming he is on a machine, that
>is INSIDE his local network, and the local network is
>NOT connected to the internet. under that condition,
>winipcfg will give him his LOCAL IP address that is
>unique to his INTERNAL network.
>
>if i run winipcfg on Blarg, for example, would I get
>192.168.0.2 or 4.38.162.139, no matter what my
>gateway machine's connectedness is?
>i would get 192.168.0.2 spit out by winipcfg, and this
>is what *he* will get as well. he will get the number
>that we need at this point, his local ip address for
>his local lan, and it really shouldn't matter if
>his gateway server is connected or not either.
>
>once you get your local IP address with winipcfg,
>which, if the lan was set up according to 'standards' of
>ip naming conventions, should begin with 192.168.0.???,
>you can then try the next test:
>
>telnet {the ip winipcfg gave you} 9000
>for me that would be telnet 192.168.0.2 9000
>
>now, this is nothing more that a bizarro loopback that is
>a kissing cousin to telnetting to localhost, BUT, it
>provides valueable information regarding the status
>of your network control panel tab, and the status
>of your internal lan and how the sysadmin set it up.
>
>once you know that number, and once that last line
>works, you can now attempt to goto the other machines
>on the lan, one at a time, and use that exact same
>line from a dos box on each of those machines, to
>gain entry to the EUServer.
>on machine #2 type:telnet {whatever} 9000
>on machine #3 type:telnet {whatever} 9000
>etc etc etc
>testing each machine to see if it can hit the server.
>
>once you determine that all is working, i strongly
>suggest that you give each machine a name, and
>update your hosts file to reflect all the names of
>all machines on the local lan. you only need to type
>all that once, and just copy the file to each machine.
>
>it's alot easier to type and remember which machine
>is which if you name them.
>
>i'll be happy to work with you further, as best i can,
>to resolve this, k patrat?
>
>if i've lost you anywhere, or you need more information
>that i have given at some particular point in the
>troubleshooting process above... by all means, we'll
>go over that...
>
>hopefully, you will be able to read/print this email,
>follow it along and everything will crankNrun :)
>
>it *should*...in theory :)
>
>take care--Hawke'
>
|
Not Categorized, Please Help
|
|
