D2: Hints for TCP/IP game please
David Hagstrom
Not open Bnet, just a plain simple TCP/IP game.
This SHOULD be easy, but we have had quite a bit of trouble with it.
1. I cannot host the game, if I do, I can see in D2 that he connects,
and then he drops due to time out.
2. If he hosts the game, I can connect, but only after ~5 tries, and
when I connects, I'll drop out after just a couple of minutes.
We have played of LAN before, and that was working just great, no matter
if I or he was hosting.
Both of us have valid dynamic IPs, and shouldn't be behind a unfriendly
proxy/firewall (One could never be too sure tough...)
I use W2K, and he have W98SE, no portblocking software or
blocking/filetering in the OS.
I have a cable connection with 64Kb Ul and 512Kb Dl, he has ISDN one
channel 64/64Kb.
Any ideas, hints or solutions?
/David
--
/* Here is my CD Key, feel free to use it: C764-OEV6-WRT7-DBL0
Brian Keener
Exact same problem here, also with W2k and W98se, but it's just over a
LAN, never hitting the internet at all.
Brian K
Satan
crack which screwed multiplayer up.
--
Satan
"Another school shooting leaves 1 person dead and 2 injured."
Pft sounds like the shooter had bad aim.
Go to hell, ask me how.
"David Hagstrom" <david.h...@mbox301.swipnet.se> wrote in message
news:MPG.140cd2898...@nntpserver.swip.net...
David Hagstrom
s4...@earthlink.net says..
> A friend of mine had that problem, turns out it was caused he used the no cd
> crack which screwed multiplayer up.
Both of us have bought the game, so this shouldn't be the case for us.
Satan
cd so he used the no cd patch to play it off his HD. If you or the person
you are trying to play with uses it then that might be your problem.
--
Satan
"Another school shooting leaves 1 person dead and 2 injured."
Pft sounds like the shooter had bad aim.
Go to hell, ask me how.
"David Hagstrom" <david.h...@mbox301.swipnet.se> wrote in message
news:MPG.140cf1292...@nntpserver.swip.net...
Brother
"Satan" <s4...@earthlink.net> wrote in message
news:w7Eo5.258$IL5....@newsread1.prod.itd.earthlink.net...
paul
wrote:
>
>
>David Hagstrom wrote:
>>
>> A friend of mine and I have tried to set up a TCP/IP game for ourselfs.
>> Not open Bnet, just a plain simple TCP/IP game.
>>
>> This SHOULD be easy, but we have had quite a bit of trouble with it.
>>
>> 1. I cannot host the game, if I do, I can see in D2 that he connects,
>> and then he drops due to time out.
>> 2. If he hosts the game, I can connect, but only after ~5 tries, and
>> when I connects, I'll drop out after just a couple of minutes.
>>
>> We have played of LAN before, and that was working just great, no matter
>> if I or he was hosting.
>>
>> Both of us have valid dynamic IPs, and shouldn't be behind a unfriendly
>> proxy/firewall (One could never be too sure tough...)
>>
>> I use W2K, and he have W98SE, no portblocking software or
>> blocking/filetering in the OS.
>>
>> I have a cable connection with 64Kb Ul and 512Kb Dl, he has ISDN one
>> channel 64/64Kb.
>>
>> Any ideas, hints or solutions?
>>
>> /David
>>
>> --
I've found that on TCP/IP you have to have the first three groups of
numbers on the IP address the same on each machine, and the fourth
different. That means u need to set the address manually on one of the
machines.
So if the machine your starting the game on gives an IP address of
201.153.69.56 for instance, you would manually set the other
machines's IP to 201.153.69.xx (xx is a number between 0 and 255 but
NOT 56). The subnet mask should be set to 255.255.255.0.
I find this works for me (I run W2K on one machine as well- you can
change the IP address without rebooting), even though it means I have
to change IP addresses frequently. This is on a small home network of
2-3 machines connected to cable internet.
If one of the machines doesn't connect to the net, that is the one to
change, but if both do, and especially if you connect to the net, you
might have to change it back after you've finished.
paul x is the spam filter
paul
Jaz
@newsserver1.intergate.ca>:
<snip>
>> >
>> > Both of us have bought the game, so this shouldn't be the case for us.
>> >
>> > /David
>> >
>> >
>> >
>> >
>> > --
>> > /* Here is my CD Key, feel free to use it: C764-OEV6-WRT7-DBL0
>>
>>
>
>
>
A friend of mine and I play regularly on TCPIP. We both play on Win98 I
think, I'm on cable and he's on dial up. I run the server.
We quite often strike difficulties similar to that which you mention. He
finds that he cannot join my game, and times out. The solution to our probs
mostly is for him to start a single player game, unequip his stuff (ie take
it off and jam it in his backpack/stash), then save/exit. He can then
usually join my game. Once in the game he can then re-equip his gear and
play normally.
However, if he dies it becomes difficult again. For some reason he cannot
loot his own corpse. Not sure what happens exactly - he may get timed out
of the game if he tries. In any case, our way around that is for me to
clear all monsters out of the immediate vicinity (not always easy) and loot
his corpse for him, immediately dropping his gear on the ground for him to
pick up and equip. Tedious, but workable. Mostly. Basically good motivation
for him to stay alive.
I think these difficulties stem from some kind of item combination problem
- like maybe he has a unique or something which my server has difficulty
with (we don't have any cheated items though). Anyway, give this a go.
Jazz.
(Sir Grogg, lvl34 Barbarian)
Markus
David Hagstrom
s4...@earthlink.net says...
Ok, but none of us are using any no-cd crack or similar. We both have
the full install (Multiplayer) and so on :)
> My friend bought the game too. But his cd-rom drive wouldn't recognize the
> cd so he used the no cd patch to play it off his HD. If you or the person
> you are trying to play with uses it then that might be your problem.
> >
> > > A friend of mine had that problem, turns out it was caused he used the
> no cd
> > > crack which screwed multiplayer up.
> >
> >
David Hagstrom
> >
> >David Hagstrom wrote:
> >>
> >> A friend of mine and I have tried to set up a TCP/IP game for ourselfs.
> >> Not open Bnet, just a plain simple TCP/IP game.
> >>
> >> This SHOULD be easy, but we have had quite a bit of trouble with it.
> I've found that on TCP/IP you have to have the first three groups of
> numbers on the IP address the same on each machine, and the fourth
> different. That means u need to set the address manually on one of the
> machines.
>
> So if the machine your starting the game on gives an IP address of
> 201.153.69.56 for instance, you would manually set the other
> machines's IP to 201.153.69.xx (xx is a number between 0 and 255 but
> NOT 56). The subnet mask should be set to 255.255.255.0.
>
> I find this works for me (I run W2K on one machine as well- you can
> change the IP address without rebooting), even though it means I have
> to change IP addresses frequently. This is on a small home network of
> 2-3 machines connected to cable internet.
>
> If one of the machines doesn't connect to the net, that is the one to
I'm not skilled in TCP so you have to excuse me if I'm way off here...
But if it's true of what you say, both machines must be located within
the same sub-net. If it's true, it shouldn't be called TCP/IP game, it
should be called "crippled-lan-game" or something similar.
And if it's true what you say (I really hope not!), what the f**k did
the coders of D2 doing when coding the multiplayer part???
Both of us have diffrent ISPs, so testing with home made IPs is not a
option.
Anyhow, thanks for sharing your experiences!
David Hagstrom
Jason...@removethis.cit.com.au says...
>
> >> >
> >> > Both of us have bought the game, so this shouldn't be the case for us.
> >> >
>
> think, I'm on cable and he's on dial up. I run the server.
>
> We quite often strike difficulties similar to that which you mention. He
> finds that he cannot join my game, and times out. The solution to our probs
> mostly is for him to start a single player game, unequip his stuff (ie take
> it off and jam it in his backpack/stash), then save/exit. He can then
> usually join my game. Once in the game he can then re-equip his gear and
> play normally.
>
> However, if he dies it becomes difficult again. For some reason he cannot
> loot his own corpse. Not sure what happens exactly - he may get timed out
> of the game if he tries. In any case, our way around that is for me to
> clear all monsters out of the immediate vicinity (not always easy) and loot
> his corpse for him, immediately dropping his gear on the ground for him to
> pick up and equip. Tedious, but workable. Mostly. Basically good motivation
> for him to stay alive.
>
> I think these difficulties stem from some kind of item combination problem
> - like maybe he has a unique or something which my server has difficulty
> with (we don't have any cheated items though). Anyway, give this a go.
>
Odd, but woth a try :)
David Hagstrom
Is this a "known" bug listed somewhere? At Blizzard?
If it's so, I'd like to have the URL to it.
Thx.
/David
> If I recall correctly, it's due to +x skill points items equipped.
> > A friend of mine and I play regularly on TCPIP. We both play on Win98 I
Handy Solo
> In article <39a34122.7412969@news>, paul...@xoptushome.com.au says...
> > >
> > >David Hagstrom wrote:
> > >>
> > >> A friend of mine and I have tried to set up a TCP/IP game for ourselfs.
> > >> Not open Bnet, just a plain simple TCP/IP game.
> > >>
> > >> This SHOULD be easy, but we have had quite a bit of trouble with it.
How do you and your friend connect to the internet?
Either of you running any firewalls?
NAT servers?
Cable routers?
>
<snip>
>
> I'm not skilled in TCP so you have to excuse me if I'm way off here...
>
> But if it's true of what you say, both machines must be located within
> the same sub-net. If it's true, it shouldn't be called TCP/IP game, it
> should be called "crippled-lan-game" or something similar.
Calm down, You know that's not the case. I think he was talking
about lan gaming - where, indeed, you want the machines to see each
other (typically no routers at home!) and making sure they're in the
same sub-net is an easy way to accomplish that.
>
> And if it's true what you say (I really hope not!), what the f**k did
> the coders of D2 doing when coding the multiplayer part???
Again, it's not true - and most likely somewhere deep down inside you
already knew this.
>
> Both of us have diffrent ISPs, so testing with home made IPs is not a
> option.
>
> Anyhow, thanks for sharing your experiences!
>
> /David
--
Handy Solo
icq# 76zero39three6
I am dyslexic of Borg. Your ass will be laminated.
Handy Solo
> In article <39A393CC...@hotmail.com>, Mar...@hotmail.com says...
>
> Is this a "known" bug listed somewhere? At Blizzard?
Check out the readme that came with patch 1.03?
What version are you and your chum using?
>
> If it's so, I'd like to have the URL to it.
>
> Thx.
>
> /David
>
>
>
> > If I recall correctly, it's due to +x skill points items equipped.
>
> > > A friend of mine and I play regularly on TCPIP. We both play on Win98 I
> > > think, I'm on cable and he's on dial up. I run the server.
> > >
> > > We quite often strike difficulties similar to that which you mention. He
> > > finds that he cannot join my game, and times out. The solution to our probs
> > > mostly is for him to start a single player game, unequip his stuff (ie take
> > > it off and jam it in his backpack/stash), then save/exit. He can then
> > > usually join my game. Once in the game he can then re-equip his gear and
> > > play normally.
> > >
> > > However, if he dies it becomes difficult again. For some reason he cannot
> > > loot his own corpse. Not sure what happens exactly - he may get timed out
> > > of the game if he tries. In any case, our way around that is for me to
> > > clear all monsters out of the immediate vicinity (not always easy) and loot
> > > his corpse for him, immediately dropping his gear on the ground for him to
> > > pick up and equip. Tedious, but workable. Mostly. Basically good motivation
> > > for him to stay alive.
> > >
> > > I think these difficulties stem from some kind of item combination problem
> > > - like maybe he has a unique or something which my server has difficulty
> > > with (we don't have any cheated items though). Anyway, give this a go.
> > >
--
Handy Solo
icq# 76zero39three6
If you drink, don't park; accidents cause people
Mark
if so, take it off and put it in your stash.
if that doesn't work, try making 2 brand new chars and see if that will work.
the IP addy's don't make any difference whatsoever btw.
also, whoever is hosting should have at LEAST 128 meg ram
preferably more. (more if the host is using D3D)
Handy Solo wrote:
> david.h...@mbox301.swipnet.se (David Hagstrom) allegedly wrote:
>
> > In article <39a34122.7412969@news>, paul...@xoptushome.com.au says...
> > > >
> > > >David Hagstrom wrote:
> > > >>
> > > >> A friend of mine and I have tried to set up a TCP/IP game for ourselfs.
> > > >> Not open Bnet, just a plain simple TCP/IP game.
> > > >>
> > > >> This SHOULD be easy, but we have had quite a bit of trouble with it.
>
> How do you and your friend connect to the internet?
> Either of you running any firewalls?
> NAT servers?
> Cable routers?
>
> >
> <snip>
>
> >
> > I'm not skilled in TCP so you have to excuse me if I'm way off here...
> >
> > But if it's true of what you say, both machines must be located within
> > the same sub-net. If it's true, it shouldn't be called TCP/IP game, it
> > should be called "crippled-lan-game" or something similar.
>
> Calm down, You know that's not the case. I think he was talking
> about lan gaming - where, indeed, you want the machines to see each
> other (typically no routers at home!) and making sure they're in the
> same sub-net is an easy way to accomplish that.
>
> >
> > And if it's true what you say (I really hope not!), what the f**k did
> > the coders of D2 doing when coding the multiplayer part???
>
> Again, it's not true - and most likely somewhere deep down inside you
> already knew this.
>
> >
> > Both of us have diffrent ISPs, so testing with home made IPs is not a
> > option.
> >
> > Anyhow, thanks for sharing your experiences!
> >
> > /David
>
> --
> Handy Solo
> icq# 76zero39three6
>
Charles Hargrave
installed under your Diablo 2 directory. Check the 'IPX/SPX Compatible'
protocol installed for your networking (I'm assuming you're running Windows)
and check that both computers are using the same frame type.
We did this at my brother's house where he had an extra PC running DHCP to
assign IP addresses to each PC, but we found that we also needed to put a
checkmark in the the 'I want to enable NetBIOS over IPX/SPX' option to every
PC to connect to the host PC. Seems strange but it may work for you. Your
mileage may vary.
Charles
Mark <haw...@nospam.home.com> wrote in message
news:39A54E8A...@nospam.home.com...
> check to see if either one of you is wearing plus to skills items.
> if so, take it off and put it in your stash.
> if that doesn't work, try making 2 brand new chars and see if that will
work.
>
> the IP addy's don't make any difference whatsoever btw.
>
> also, whoever is hosting should have at LEAST 128 meg ram
> preferably more. (more if the host is using D3D)
>
>
> Handy Solo wrote:
>
> > david.h...@mbox301.swipnet.se (David Hagstrom) allegedly wrote:
> >
> > > In article <39a34122.7412969@news>, paul...@xoptushome.com.au
says...
> > > > >
> > > > >David Hagstrom wrote:
> > > > >>
> > > > >> A friend of mine and I have tried to set up a TCP/IP game for
ourselfs.
> > > > >> Not open Bnet, just a plain simple TCP/IP game.
> > > > >>
> > > > >> This SHOULD be easy, but we have had quite a bit of trouble with
it.
> >