UKGPL Season 20 (2010-2011) Graduates Cup (67) - Mosport - Oct 10

[vosblod]

I have had no problems whatsoever connecting anyplace, day, date or time until the S20 grads thing on Vos's laptop server.

Sorry just to clarify the race was NOT run on UKGPL_6 (ie the laptop server), which as far as I'm aware has had no problems. Well apart from not responding for the race - hence our putting UKGPL_5 on standby in future as a back up.
The event ran off my home PC which is set to 116 (just checked).

Is it possible for you to check your core.ini settings Bernie as I'm now thinking that could be it.
You'll find the core.ini in your GPL folder, just scan down and look for these lines;

net_mdm_client_send_size = 84                ; Client packet size on dialup
net_mdm_server_send_size = 116                ; Server packet size on dialup

I just need your numbers.

[Hristo Itchov]

I use the free version of Avira and it's awesome. Super light and very high protection, so I recommend it thoroughly. It's a stand-alone anti-virus though, so you'd need a separate firewall - I use Comodo.

[bernie]

I have had no problems whatsoever connecting anyplace, day, date or time until the S20 grads thing on Vos's laptop server.

Sorry just to clarify the race was NOT run on UKGPL_6 (ie the laptop server), which as far as I'm aware has had no problems. Well apart from not responding for the race - hence our putting UKGPL_5 on standby in future as a back up.
The event ran off my home PC which is set to 116 (just checked).

Is it possible for you to check your core.ini settings Bernie as I'm now thinking that could be it.
You'll find the core.ini in your GPL folder, just scan down and look for these lines;

net_mdm_client_send_size = 84                ; Client packet size on dialup
net_mdm_server_send_size = 116                ; Server packet size on dialup

I just need your numbers.

Its just called core (without the .ini extension )

net_mdm_client_send_size = 84                ; Client packet size on dialup
net_mdm_server_send_size = 384               ; Server packet size on dialup


I take it these are the ones  ?

Why modem ? thought that was for old 56k telephone line stuff

[vosblod]

Its just called core (without the .ini extension )
net_mdm_server_send_size = 384               ; Server packet size on dialup
Why modem ? thought that was for old 56k telephone line stuff

The .ini bit is probably hidden by Windows. You're set to the maximum then so shouldn't have had mismatch problems with 116. Ignore reference to modems, leftover stuff from earlier days I guess.
I'm afraid the mystery remains then.

Incidentally, I didn't just decide to run it on my home PC on the off chance it would work. I've used it in the past for many online sessions without problems - it's even managed to run the GT mod.

[Hristo Itchov]

I still beileve it could be related to ISP problems (no necessarily your ISP) on that day (and hour). Perhaps in the line between your and Tim's location, Bernie. That error message doesn't appear when you have incorrect BW settings or any other settings.

[happyal]

On the AV Front, I was using AVG but it's not as good as it was. I'm currently using Microsoft Security Essentials, which so far has been great. It's very light weight and can be easily disabled to play online games. Again it's only a stand alone Anti Virus, you'll need a firewall too, I use ZoneAlarm.

[Phil Thornton]

The first thing to do with a repeated timeout is to temporarily change your core.ini to match the server which should solve the problem if it's due to a miss-match. I thought this was common knowledge in the GPL world as anyone who has never had a time-out is very lucky.

I wasn't getting timed out , though that's useful info for the future ( If I can remember)

My problem read ...

OPENING CHANNEL
OPENING NETWORK DEVICE
10054 : ERROR DETECTED ON NETWORK DEVICE
CLOSING ...... bla bla bla

My question is ....

How do I stop this error message from happening next time I want to race ?

 

The error code 10054 is generated by the underlying TCP/IP network that GPL (and everything else network related on your PC) relies on.  As far as I know the formal meaning is "Connection reset by peer. An existing connection was forcibly closed by the remote host."  What that means in reality is that the server and client (your computer) have stopped communicating (or more accurately couldn't establish a connection) for some reason.  The question is why?  It could be a timeout i.e. it has taken so long to establish a connection either the server or the client decided to terminate the connection or it could be that your firewall has decided to close a particular port.

Given that you can connect to servers most of the time then it is probably not your firewall settings.   So it must be something to do with latency causing a timeout.  A virus checker could be introducing latency so switching it off or using a "lighter" virus checker might help.  Shutting down any background tasks would also help.  I think the bandwidth settings in GPL are also a factor.

However I suspect it will boil down to something outside your control like your ISP or the ISP of the server.  So to be honest I'm with Hristo on this one (he also thinks it will be ISP related) but that shouldn't stop us trying everything else first.  Changing ISP is a pain and there is no guarantee another ISP will be any better.  It could simply be down to your local exchange.

[Turkey Machine]

If it helps, the only time I get error 10054 is when my internet connection drops completely.

[bernie]

Dont have any AV or virus checker

Dont have firewall running for gpl

I often get "timed out" message on "some" servers , (maybe be the latency thing ) but clicking the "would you like to try again" button usually gets me in !

can't say i've ever seen the 10054 message before, but it could be I just never notice it 


Thanks for trying to sort it though much appreciated .


 

 

[vosblod]

I often get "timed out" message on "some" servers , (maybe be the latency thing ) but clicking the "would you like to try again" button usually gets me in !

I get it all the time - even on my own server Sometimes it takes three stabs. I think it's just the timing of when you try to touch the lady...

[FullMetalGasket]

I've noted you're more likey to time out when connecting if a horde of drivers have all trie to join at once, if you avoid the rush and go in either late or early you'll go get straight in - this is especially the case with detailed circuits that take a while to load (for instance Monaco is about 300 meg for me!  )

[vosblod]

Moderation completed