I have a question regarding connecting to a race server, via IPX rather than
TCP.
I thought I had this worked out (in N3).....but I have doubts now about how
this works in N4 (guess that gives away my ignorance of more than surface
knowledge of intranet/internet tech).
Here's my equipment config (three stations):
1. N4 Dedicated server > connected to Internet through LAN hub (cable @Home
service).
2. "Race Box" #1 > connected to Internet through LAN hub (same hub as in #1
above).
3. "Race Box" #2 > connected to Internet through separate @Home cable
(separate from #1 and #2 above).
When online racing on RB #2.....I connect via Sierra.com....as a "client"
just like anyone else....although the server is just a few feet away. The
two devices are on separate @Home cable connections (dual cable lines run
into my house).
When online racing on RB #1.....I want to connect to the Server via
IPX.....directly through the LAN hub...so I'm racing as a "client" but not
part of the upside bandwidth. I have both TCP and IPX connections set as
"allowed" on the Dedicated Server. When setting an online race via the
Dedicated Server, I have the choice of "registering" the Dedicated Server
with Sierra.com....or not registering the race at Sierra.com.
***Unregistered race: In RB #1, it shows the race via IPX connection (in
the screen prior to launching on to Sierra.com). I can highlight the IPX
race, and connect directly to the Dedicated Server via the IPX....connected
then, through the LAN that joins the two devices. This race also shows on
Sierra.com (two versions of it...one IPX and the other TCP)....but no one
who has signed on to Sierra.com can join either race...they get the error
message "This server is not registered with Sierra.com......blah, blah,
blah...you must exit Sierra.com to join a race on this server). Unless I've
given somebody the IP address of the server....how would they join the race?
It doesn't show on their "pre-Sierra.com" entry screen?
***Registered race: In RB #1, it still shows the race via IPX connection in
the "pre-screen" as above. It also (obviously) shows up on Sierra.com
(again as two versions IPX and TCP)....anyone on Sierra.com can join as a
"client"......but I can not join the race as in the "unregistered" scenario
in the paragraph directly above....I must also sign on to Sierra.com (if I
attempt to sign onto the race in the pre-screen...then I get the error
message, "This race is registered with Sierra.com and you are not. You must
sign-on to Sierra.com in order to join the race.). Once I sign on to
Sierra.com.....I can join the race in the normal manner.....either one, IPX
or TCP. I was under the assumption if I joined the TCP version....I'd be a
"client" like everyone else....but since my Internet connection would then
be shared with the Internet connection of the Dedicated Server (we are both
connected to the Internet through the same LAN hub)....I'd be part of the
bandwidth. If I connected to the race via the IPX version shown on
Sierra.com.....then I'd be directly connected to the Dedicated server via
the LAN hub....and not part of the upside bandwidth. That was my
assumption....but I am now wondering if that is indeed true!
Could someone who understands the tech side of this stuff tell me: Am I
part of the bandwidth or not....? Someone suggested last night in the chat
room that no matter what method I use to connect to the server....if the
server is registered...and I as the client am registered on
Sierra.com.....my connection to the server is "via the Internet" (when
choosing the IPX version to join) and not directly via the LAN hub between
myself and the server. Which is it?
Thanks in advance for you information,
Tom Pabst
Tom, I think only Eric Busch or Shawn Wise could answer this question
with any kind of certainty/authority. Anyone not directly involved with
writing the source code for NR4 would just be guessing.
It's my *guess* that papy either purposely designed this in, or that
it's a bug. I don't remember if N3 did this, but I seem to remember
that it didn't have this restriction.
In article <9aQz6.2017$[email hidden]>,
[email hidden] says...
--
=========================================================
Redneck Techno-Biker & "programming deity"
http://www.paddedwall.org/john
DeMONS/1 for Nascar Racing 3 & Nascar Legends
http://www.paddedwall.org/demons
DeMONS/2 for Nascar Racing 4 (in development)
http://www.paddedwall.org/demons2
Barbarian Diecast Collector (460+ cars and counting)
http://www.paddedwall.org/diecast
If you want to send me email, go to the first URL shown
above & click "Send Me Mail" in the contents frame.
=========================================================
Quoted text (71 lines)
> I have a question regarding connecting to a race server, via IPX rather than > TCP. > > I thought I had this worked out (in N3).....but I have doubts now about how > this works in N4 (guess that gives away my ignorance of more than surface > knowledge of intranet/internet tech). > > Here's my equipment config (three stations): > > 1. N4 Dedicated server > connected to Internet through LAN hub (cable @Home > service). > > 2. "Race Box" #1 > connected to Internet through LAN hub (same hub as in #1 > above). > > 3. "Race Box" #2 > connected to Internet through separate @Home cable > (separate from #1 and #2 above). > > When online racing on RB #2.....I connect via Sierra.com....as a "client" > just like anyone else....although the server is just a few feet away. The > two devices are on separate @Home cable connections (dual cable lines run > into my house). > > When online racing on RB #1.....I want to connect to the Server via > IPX.....directly through the LAN hub...so I'm racing as a "client" but not > part of the upside bandwidth. I have both TCP and IPX connections set as > "allowed" on the Dedicated Server. When setting an online race via the > Dedicated Server, I have the choice of "registering" the Dedicated Server > with Sierra.com....or not registering the race at Sierra.com. > > ***Unregistered race: In RB #1, it shows the race via IPX connection (in > the screen prior to launching on to Sierra.com). I can highlight the IPX > race, and connect directly to the Dedicated Server via the IPX....connected > then, through the LAN that joins the two devices. This race also shows on > Sierra.com (two versions of it...one IPX and the other TCP)....but no one > who has signed on to Sierra.com can join either race...they get the error > message "This server is not registered with Sierra.com......blah, blah, > blah...you must exit Sierra.com to join a race on this server). Unless I've > given somebody the IP address of the server....how would they join the race? > It doesn't show on their "pre-Sierra.com" entry screen? > > ***Registered race: In RB #1, it still shows the race via IPX connection in > the "pre-screen" as above. It also (obviously) shows up on Sierra.com > (again as two versions IPX and TCP)....anyone on Sierra.com can join as a > "client"......but I can not join the race as in the "unregistered" scenario > in the paragraph directly above....I must also sign on to Sierra.com (if I > attempt to sign onto the race in the pre-screen...then I get the error > message, "This race is registered with Sierra.com and you are not. You must > sign-on to Sierra.com in order to join the race.). Once I sign on to > Sierra.com.....I can join the race in the normal manner.....either one, IPX > or TCP. I was under the assumption if I joined the TCP version....I'd be a > "client" like everyone else....but since my Internet connection would then > be shared with the Internet connection of the Dedicated Server (we are both > connected to the Internet through the same LAN hub)....I'd be part of the > bandwidth. If I connected to the race via the IPX version shown on > Sierra.com.....then I'd be directly connected to the Dedicated server via > the LAN hub....and not part of the upside bandwidth. That was my > assumption....but I am now wondering if that is indeed true! > > Could someone who understands the tech side of this stuff tell me: Am I > part of the bandwidth or not....? Someone suggested last night in the chat > room that no matter what method I use to connect to the server....if the > server is registered...and I as the client am registered on > Sierra.com.....my connection to the server is "via the Internet" (when > choosing the IPX version to join) and not directly via the LAN hub between > myself and the server. Which is it? > > Thanks in advance for you information, > > Tom Pabst >Well John......that's why I posted the question. I do think a few people
outside of Papyrus know the answer(s)......but I'd be glad to hear them from
anyone who knows, Eric?
I'm not trying to find fault with the Papy coding of MP....I just want to
know "the rules" I'm playing by....so I can adjust. I can't be the only
person that has two computers....one used as a Dedicated Server, the other
as a "race box"......connected by LAN. Why be part of the client side
bandwidth when its not necessary? If I have to give out the IP address of
the DS......so I can connect directly to it via LAN IPX.....and the other
via standard TCP...then that's fine with me.....I just want to know one way
or the other?
Tom
I don't quite understand the problem. If a server is registered with
sierra.com, all clients connecting to it must also be logged into sierra.com
(this is to ensure that each client in the race has a unique UserID, which
allows for invite lists, muzzle lists, ratings, etc. to work). Note that
once logged into sierra.com, local clients can still join the server on the
LAN using the separately listed local (X) IPX or (T) TCP/IP connections.
So...
The unregistered race will be broadcast locally such that anyone on your
local LAN will see the (X) IPX and (T) TCP/IP races listed in the available
races table on the main multiplayer screen. Anyone outside your LAN would
obviously need to know your IP address to manually connect to the server.
The registered race will broadcast to sierra.com, such that anyone logged
into sierra.com will see the race posted. Anyone on your local LAN who
wants to join the server will also need to be logged into sierra.com, but
they will see 3 different races in the sierra.com available races table: the
(S) sierra.com race that everyone sees with the addition of the local (X)
IPX and (T) TCP/IP connections. For local clients, the IPX connections will
always be through the internal LAN, and the TCP/IP race most likely would be
via the local LAN as well, but it would depend on how your network's routing
is configured.
--
Eric
"Tom Pabst" <[email hidden]> wrote in message
news:_R0A6.2490$[email hidden]...
> Well John......that's why I posted the question. I do think a few people
> outside of Papyrus know the answer(s)......but I'd be glad to hear them
from
> anyone who knows, Eric?
>
> I'm not trying to find fault with the Papy coding of MP....I just want to
> know "the rules" I'm playing by....so I can adjust. I can't be the only
> person that has two computers....one used as a Dedicated Server, the other
> as a "race box"......connected by LAN. Why be part of the client side
> bandwidth when its not necessary? If I have to give out the IP address of
> the DS......so I can connect directly to it via LAN IPX.....and the other
> via standard TCP...then that's fine with me.....I just want to know one
way
> or the other?
You can't connect via IPX through the Internet.
RB
On Sun, 08 Apr 2001 02:37:57 GMT, "Tom Pabst" <[email hidden]>
wrote:
Quoted text (73 lines)
>I have a question regarding connecting to a race server, via IPX rather than >TCP. > >I thought I had this worked out (in N3).....but I have doubts now about how >this works in N4 (guess that gives away my ignorance of more than surface >knowledge of intranet/internet tech). > >Here's my equipment config (three stations): > >1. N4 Dedicated server > connected to Internet through LAN hub (cable @Home >service). > >2. "Race Box" #1 > connected to Internet through LAN hub (same hub as in #1 >above). > >3. "Race Box" #2 > connected to Internet through separate @Home cable >(separate from #1 and #2 above). > >When online racing on RB #2.....I connect via Sierra.com....as a "client" >just like anyone else....although the server is just a few feet away. The >two devices are on separate @Home cable connections (dual cable lines run >into my house). > >When online racing on RB #1.....I want to connect to the Server via >IPX.....directly through the LAN hub...so I'm racing as a "client" but not >part of the upside bandwidth. I have both TCP and IPX connections set as >"allowed" on the Dedicated Server. When setting an online race via the >Dedicated Server, I have the choice of "registering" the Dedicated Server >with Sierra.com....or not registering the race at Sierra.com. > >***Unregistered race: In RB #1, it shows the race via IPX connection (in >the screen prior to launching on to Sierra.com). I can highlight the IPX >race, and connect directly to the Dedicated Server via the IPX....connected >then, through the LAN that joins the two devices. This race also shows on >Sierra.com (two versions of it...one IPX and the other TCP)....but no one >who has signed on to Sierra.com can join either race...they get the error >message "This server is not registered with Sierra.com......blah, blah, >blah...you must exit Sierra.com to join a race on this server). Unless I've >given somebody the IP address of the server....how would they join the race? >It doesn't show on their "pre-Sierra.com" entry screen? > >***Registered race: In RB #1, it still shows the race via IPX connection in >the "pre-screen" as above. It also (obviously) shows up on Sierra.com >(again as two versions IPX and TCP)....anyone on Sierra.com can join as a >"client"......but I can not join the race as in the "unregistered" scenario >in the paragraph directly above....I must also sign on to Sierra.com (if I >attempt to sign onto the race in the pre-screen...then I get the error >message, "This race is registered with Sierra.com and you are not. You must >sign-on to Sierra.com in order to join the race.). Once I sign on to >Sierra.com.....I can join the race in the normal manner.....either one, IPX >or TCP. I was under the assumption if I joined the TCP version....I'd be a >"client" like everyone else....but since my Internet connection would then >be shared with the Internet connection of the Dedicated Server (we are both >connected to the Internet through the same LAN hub)....I'd be part of the >bandwidth. If I connected to the race via the IPX version shown on >Sierra.com.....then I'd be directly connected to the Dedicated server via >the LAN hub....and not part of the upside bandwidth. That was my >assumption....but I am now wondering if that is indeed true! > >Could someone who understands the tech side of this stuff tell me: Am I >part of the bandwidth or not....? Someone suggested last night in the chat >room that no matter what method I use to connect to the server....if the >server is registered...and I as the client am registered on >Sierra.com.....my connection to the server is "via the Internet" (when >choosing the IPX version to join) and not directly via the LAN hub between >myself and the server. Which is it? > >Thanks in advance for you information, > >Tom Pabst > > >Eric....
I don't have a "problem"....with how this works, its that I don't understand
how it works and was asking for some clarification. If IPX can't be
connected via the Internet to the DS (in this case...the DS on the same
local LAN as myself).....then I'm correct I guess in assuming that my
"client" upside bandwidth load on the DS is dramatically reduced, or only
somewhat reduced (I'm assuming it isn't completely eliminated since my car
position and stats need to be broadcast ....upside....to the other clients)?
I was being further confused by the fact that I am required to be registered
on Sierra.com.......if the DS is registered on Sierra.com.......whether
joining as a IPX LAN client... or a TCP/IP client (for very good reasons).
That's no problem....I just wanted to know if that altered my status as a
"reduced upside bandwidth" client?
Thanks for the info Eric....as always.
Tom
