Page 1 of 1

Error C10: Two computers under one wireless router.

Posted: Wed Jul 25, 2007 6:12 pm
by Tumultus
I'm trying to play SRO with my brother, and we are under a wireless router (2 laptops) but the game doesn't let us play at the same time...

Is there ANYTHING at all I can do about this?

Posted: Wed Jul 25, 2007 8:39 pm
by phulshof
Sure, buy a router with a proper NAT implementation. :) Which brand and type of router do you have?

Posted: Thu Jul 26, 2007 1:12 am
by xzaz
C10 was, unable to connect to master server? So Firewall, and because you and your brother cant play. Maby a software build-in firewall in your router?

Posted: Thu Jul 26, 2007 3:53 am
by Tumultus
I actually have to spend money on this? Sigh.

I have a D-Link 624

Posted: Thu Jul 26, 2007 5:09 am
by phulshof
Hmm, and how is that D-link connected to the internet? Is there another router or modem in between before you go to your ISP? If so, you could try using your D-link as an access point rather than a router.

In general though, the D-link 624 is known to have certain NAT problems. Perhaps you could borrow someone else's wireless router for a moment to see if that solves your problem?

Posted: Thu Jul 26, 2007 9:05 pm
by Tumultus
Well I have a computer that has a modem, and it goes to the wireless router so that both of our laptops can receive the signal.

Posted: Thu Jul 26, 2007 9:12 pm
by phulshof
Sounds to me like you could safely set up your router as an access point then, and hope that the next router in line will perform NAT properly for you. It's at least worth a try.

Posted: Thu Jul 26, 2007 9:30 pm
by Tumultus
How exactly do you do that anyways?

Posted: Fri Jul 27, 2007 5:03 am
by phulshof

Posted: Fri Jul 27, 2007 2:54 pm
by robert_utk
each computer is not getting a unique ip address from the router or the router is not using dhcp to route the internet to both computers. This will cause either computer to not connect when the other is already running. Basically your router has only one ip address and its not set up correctly to get more than one computer online. Also, make sure its a router and not a hub. Hubs require all the services to be done by the first computer in line.

Posted: Sat Jul 28, 2007 12:19 pm
by Tumultus
Well then how do I set it correctly?

Both computers can get on the internet, by the way, they just can't play SRO at the same time.

Posted: Sat Jul 28, 2007 4:00 pm
by phulshof
Read the article on the link I provided. It holds a step by step answer. Basically it comes down to not using the WAN port on your router, and thus use the wireless router as a wireless switch (access point).

Posted: Sat Jul 28, 2007 11:01 pm
by xzaz
robert_utk wrote:each computer is not getting a unique ip address from the router or the router is not using dhcp to route the internet to both computers. This will cause either computer to not connect when the other is already running. Basically your router has only one ip address and its not set up correctly to get more than one computer online. Also, make sure its a router and not a hub. Hubs require all the services to be done by the first computer in line.

Both computers have internet, so TCP/IP settings are good.

Posted: Sat Jul 28, 2007 11:49 pm
by Majorharper
D-link aint the best try going for belkin, if you are going to change router

Posted: Sun Jul 29, 2007 12:37 pm
by Fat_Smurf
i have a similar problem


Im using dlink wbr-1310 with one wireless and one wired


I'm also getting c10 error when i try to log my other comp on sro as this one is already on.


I've been told it was cause dmz was enable is it true?

Posted: Sun Jul 29, 2007 2:17 pm
by Majorharper
dmz
specify please?

Posted: Sun Jul 29, 2007 2:58 pm
by phulshof
DMZ = Demilitarized Zone, Google is your friend

I doubt DMZ is the problem, tho you should really wonder why on Earth you'd want to activate DMZ to begin with.

Just for clarification: C10 is caused if a person attempts to log in with the same source IP address and source TCP port. This usually happens if you have a router with a bad NAT implementation. D-link is notorious for this.

Posted: Sun Jul 29, 2007 3:54 pm
by Fat_Smurf
phulshof wrote:DMZ = Demilitarized Zone, Google is your friend

I doubt DMZ is the problem, tho you should really wonder why on Earth you'd want to activate DMZ to begin with.

Just for clarification: C10 is caused if a person attempts to log in with the same source IP address and source TCP port. This usually happens if you have a router with a bad NAT implementation. D-link is notorious for this.



it was working fine before but now it wont work since I've resetted the router :S dunno what I didn't do the same way :S

Posted: Sun Jul 29, 2007 4:14 pm
by phulshof
Fat_Smurf wrote:
phulshof wrote:DMZ = Demilitarized Zone, Google is your friend

I doubt DMZ is the problem, tho you should really wonder why on Earth you'd want to activate DMZ to begin with.

Just for clarification: C10 is caused if a person attempts to log in with the same source IP address and source TCP port. This usually happens if you have a router with a bad NAT implementation. D-link is notorious for this.



it was working fine before but now it wont work since I've resetted the router :S dunno what I didn't do the same way :S


Well, I guess as a test you could put up DMZ to one computer, and leave the other to still run through NAT, and see if that solves your issue. If it works, just don't try to add a third computer. :) Which revision do you use? I could have a look at the manual for you.

Posted: Thu Aug 02, 2007 7:42 pm
by Tumultus
Would making the router an access point hurt connection strength/range?

Posted: Thu Aug 02, 2007 7:57 pm
by phulshof
No, it just influences if it acts as a level 3 protocol handler (router) or a level 2 (switch).

Posted: Thu Aug 02, 2007 9:52 pm
by Tumultus
I hope this works.

EDIT: Now that I look at it, I have NO idea how to do this. This is what it says:

"Connect to a LAN port (not the WAN port).

Change the 'LAN IP address' to an unused IP address on your LAN.

On Home | DHCP:
Disable the DHCP server.

On Home | WAN:
Set the WAN port to Static IP and then
configure the Static IP address to bogus values:
IP address = 99.99.99.99
Netmask = 255.255.255.0
Gateway = 99.99.99.100
DNS = 99.99.99.100

Reboot the DI-624."

Posted: Thu Aug 09, 2007 9:36 am
by phulshof
Tumultus wrote:"Connect to a LAN port (not the WAN port).
Change the 'LAN IP address' to an unused IP address on your LAN.
On Home | DHCP:
Disable the DHCP server.
On Home | WAN:
Set the WAN port to Static IP and then
configure the Static IP address to bogus values:
IP address = 99.99.99.99
Netmask = 255.255.255.0
Gateway = 99.99.99.100
DNS = 99.99.99.100
Reboot the DI-624."


Ok, let's take this one step at a time then:

- "Connect to a LAN port (not the WAN port).

On most routers you will find 5 ports, 1 Wide Area Network port (which is connected to the outside world), and 4 Local Area Network ports (which are connected to your internal network or directly to your computers). In your current setup you probably have your LAN ports connected to your computers and your WAN port connected to the DSL modem or to another router. Disconnect your WAN port, and connect your DSL modem/router to one of the LAN ports.

- Change the 'LAN IP address' to an unused IP address on your LAN.

Your DSL modem probably uses DHCP already, so you will have to set the LAN IP address to "get address automatically". If your DSL modem does not use DHCP, then just chose an unused IP address on your LAN (often 10.0.0.* or 192.168.1.*).

- On Home | DHCP: Disable the DHCP server.

Since your DHCP will now be handled by the DSL modem, your D-Link no longer needs to run a DHCP server, so you must disable it.

- On Home | WAN:
- Set the WAN port to Static IP and then
- configure the Static IP address to bogus values:
- IP address = 99.99.99.99
- Netmask = 255.255.255.0
- Gateway = 99.99.99.100
- DNS = 99.99.99.100

Since you no longer use your WAN port, just set the IP information to the above values so your router does not waste time trying to get an IP address.

- Reboot the DI-624."

I am sure you can manage this. :)