1 Attachment(s)
Client not connect to server :(
Client not logging :(
http://i46.tinypic.com/10oikx3.jpg
and no match more.
Client - GP.
log's in attached file.
Server - cabal-repack-2.8, on vmware - CentOSv4.8
ip for mssql - 192.168.1.3
ip for server - 192.168.1.18
What i'm doing nothing?
help please.
And sorry for my bad english.
Re: Client not connect to server :(
Try to ping your IP addresses make sure there is a connection.
Also, double check make sure your firewall and ports are not disabled and blocked.
Re: Client not connect to server :(
Quote:
Originally Posted by
Daman2009
Also, double check make sure your firewall and ports are not disabled and blocked.
i think he want to say Firewall must be Disabled...so you have to get sure,your firewall is DISABLED and your Ports are Forwarded on your Router...
Regards...
Re: Client not connect to server :(
The firewall is disabled or else...it wouldnt connect to sql,you didn't open the ports,or you didn't forward,or in internal.txt doesn't listen the right ports
Re: Client not connect to server :(
firewall - off, 100%
ping 192.168.1.3->192.168.1.18 - OK
ping 192.168.1.18->192.168.1.3 - OK
PORT=38101 - open
CHAT_PORT=38121 - open
Same idea's?
And qustion - how i can check from 192.168.1.3 my cabal-server(192.168.1.18)? ping bla.bla.bla. or how? :)
Re: Client not connect to server :(
from CentOS:
ping -c4 WINDOWS IP..
ping -c4 www.google.com (to check if its online)
from Windows:
ping CentOS IP...
thats it...
if all gives you a good ping,there is no Problem in Firewall...
then check your Router config,if you Ports are Forwarded,as Emi said...
2 Attachment(s)
Re: Client not connect to server :(
i'm reinstall CentOS, MSSQL.
ping centos(192.168.1.18)->mssql(192.168.1.3) - very good
ping mssql->centos - good to
In log's all ok, but gameclient don't connect to the server :(
What i'm doing wrong?
p.s. server's status is ok. (use this - Server status web page)
Re: Client not connect to server :(
in internal.txt what ip did u put?the centos ip or your WAN ip?I think this is the problem
Re: Client not connect to server :(
Quote:
Originally Posted by
emi5893
in internal.txt what ip did u put?the centos ip or your WAN ip?I think this is the problem
CentOS - 192.168.1.18
Re: Client not connect to server :(
I can see login attempts in the loginsvr so it's getting that far. The worldsvr is on the correct IP for an offline server (lan-only) too. Not one single "database connect success!" in the logs though so my guess is a firewall is blocking access to mssql or it is refusing remote connections (check remote connections in the "surface area config" tool in the start menu).
Re: Client not connect to server :(
i see there are database connect succes in the logs:
[Sat Dec 26 2009 10:13:59.625984 3064933280]: Database Connect success!
[Sat Dec 26 2009 10:13:59.644073 3054443424]: Database Connect success!
[Sat Dec 26 2009 10:13:59.649196 3043953568]: Database Connect success!
[Sat Dec 26 2009 10:13:59.663894 3054443424]: sock 10=> sendBuf is growed (size:32768). len(657), 17000, 131072
[Sat Dec 26 2009 10:14:55.255688 3085912992]: Database Connect success!
Re: Client not connect to server :(
I'm realy don't now wath happend :(
What more information can help?
Re: Client not connect to server :(
Not for other logs there should be connection successes in emi.
Is your windows a 64 bit version? If so and you use 2005 you _must_ have the 64-bit version.
Re: Client not connect to server :(
Quote:
Originally Posted by
chumpywumpy
Not for other logs there should be connection successes in emi.
Is your windows a 64 bit version? If so and you use 2005 you _must_ have the 64-bit version.
My windows a 32 bit version :( Wath can i do?
Re: Client not connect to server :(
Run this query on any db and post the results. This will tell me if sql is correctly configured.
Quote:
Declare @insname varchar(25)
if convert(varchar(25),serverproperty('instancename')) is null
set @insname='MSSQLSERVER'
else
set @insname=convert(varchar(25),serverproperty('instancename'))
select @insname as 'Instance',
serverproperty('productversion') as 'Ver', serverproperty('productlevel') as 'SP',
serverproperty('edition') as 'Edition'
if @insname<>'MSSQLSERVER'
begin
select 'THIS IS BAD! You must reinstall MSSQL. Please follow the guides next time.' as 'MSSQL is a named instance!'
end
begin
Declare @inspath varchar(10),@reg varchar(100),@tcpremote as int
EXEC master.dbo.xp_regread @rootkey='HKEY_LOCAL_MACHINE',
@key='Software\Microsoft\Microsoft SQL Server\Instance Names\SQL\',
@value_name=@insname,
@value=@inspath OUTPUT
set @reg='Software\Microsoft\Microsoft SQL Server\' + @inspath + '\MSSQLSERVER\SuperSocketNetLib\tcp\'
EXEC master.dbo.xp_regread @rootkey='HKEY_LOCAL_MACHINE',
@key=@reg,
@value_name='Enabled',
@value=@tcpremote OUTPUT
select @inspath as 'Instance path',@tcpremote as 'Remote connections enabled?'
if @tcpremote='0'
begin
EXEC master.dbo.xp_regwrite @rootkey='HKEY_LOCAL_MACHINE',
@key=@reg, @value_name='Enabled', @type='REG_DWORD',@value=1
select 'I enabled remote connections ! Please reboot !' as 'Remote connections checker'
end
else
begin
select 'This is good! I have nothing to do :(' as 'Remote connections checker'
end
select account.dbo.fn_md5('test') as 'xp_md5.dll check'
end