View Full Version : Help with server
rumduck
03-28-2004, 03:55 AM
I make it but my friends cant see it, ive opened ports 28960,20500,20510 on both tcp and udp.
Resolving codmaster.activision.com
codmaster.activision.com resolved to 63.146.124.59:20510
Sending heartbeat to codmaster.activision.com
Hitch warning: 6102 msec frame time
Resolving codauthorize.activision.com
codauthorize.activision.com resolved to 63.146.124.59:20500
Hitch warning: 686 msec frame time
Sending heartbeat to codmaster.activision.com
this got nething to do with it?
or this
Winsock Initialized
Opening IP socket: localhost:28960
Hostname: master
IP: 192.168.1.4
--- Common Initialization Complete ---
execing sconfig.cfg
net_ip will be changed upon restarting.
map_rotate...
(net ip i typed in is my IP, not network ip)
Please help
snafu
03-28-2004, 03:57 AM
looks like you have your box behind a router.
if so u can but your box in the DMZ just put a good firewall on if you do so or you can setup portforwading to allow user to connect to you. Im not to good with portforwarding but there are great guides to help you with it.
rumduck
03-28-2004, 03:59 AM
ive done the port fowarding, the ports i mentioned are fowared to 192.168.1.4 (the comp with the server).
and what is DMZ
snafu
03-28-2004, 04:02 AM
dang that was fast. DMZ is demiliterized zone. pretty much most routers have it. its where you put the ip for your box only one can go and its on the net 24-7 and can be accessed from anyone.
thats why you have to change policies and put up firewalls.
rumduck
03-28-2004, 04:07 AM
no idea what u just said but heres a pic... and also i got zonealarm but that isnt interfering cos i shut it down :)
http://users.tpg.com.au/tsimberis/portcrap.jpg
rumduck
03-28-2004, 04:25 AM
is the ip people should join the ip from www.whatismyip.com?
when i give em that followed by :28960 they cant see it? a computer on my network can see the game under local but not internet, whats going on, ive got set dedicated 2 in the shortcut thing so its dedicated interenet
snafu
03-28-2004, 04:46 AM
hmm, i just checked my server and its doing the same thing as yours is. let me research some more and see what is going on.
sounds like alot of people are having the same problem. hopefully we can get this resolved and soon.
wish i could be more of help to u man.
rumduck
03-29-2004, 04:02 AM
k, now i get this
Winsock Initialized
Opening IP socket: 203.113.219.93:28960
WARNING: UDP_OpenSocket: bind: WSAEADDRNOTAVAIL
Opening IP socket: 203.113.219.93:28961
WARNING: UDP_OpenSocket: bind: WSAEADDRNOTAVAIL
Opening IP socket: 203.113.219.93:28962
WARNING: UDP_OpenSocket: bind: WSAEADDRNOTAVAIL
Opening IP socket: 203.113.219.93:28963
WARNING: UDP_OpenSocket: bind: WSAEADDRNOTAVAIL
Opening IP socket: 203.113.219.93:28964
WARNING: UDP_OpenSocket: bind: WSAEADDRNOTAVAIL
Opening IP socket: 203.113.219.93:28965
WARNING: UDP_OpenSocket: bind: WSAEADDRNOTAVAIL
Opening IP socket: 203.113.219.93:28966
WARNING: UDP_OpenSocket: bind: WSAEADDRNOTAVAIL
Opening IP socket: 203.113.219.93:28967
WARNING: UDP_OpenSocket: bind: WSAEADDRNOTAVAIL
Opening IP socket: 203.113.219.93:28968
WARNING: UDP_OpenSocket: bind: WSAEADDRNOTAVAIL
Opening IP socket: 203.113.219.93:28969
WARNING: UDP_OpenSocket: bind: WSAEADDRNOTAVAIL
WARNING: Couldn't allocate IP port
vBulletin® v3.8.7, Copyright ©2000-2012, vBulletin Solutions, Inc.