d3server
d3server
im having trouble joining my own servers on pxo. got the servers running on a different pc. i can see the games on the pxo list, but when i try to join it says "no response from server"... any help would be appreciated.
I don't know if any of what I'm gonna say is factual, but I'll throw it out there. If you forward port 2092 to your server, any packets going to that port will go to your server, rather than your other computer. Therefore, when you try to play d3 on port 2092, the packets from the server to you are getting routed back to the server. Does that make any sense?
Something you might want to try is looking under Direct TCP/IP and scan the local network. I seem to remember some of the Asylum PXO servers showing up on the LAN.
Something you might want to try is looking under Direct TCP/IP and scan the local network. I seem to remember some of the Asylum PXO servers showing up on the LAN.
- Krom
- DBB Database Master
- Posts: 16135
- Joined: Sun Nov 29, 1998 3:01 am
- Location: Camping the energy center. BTW, did you know you can have up to 100 characters in this location box?
- Contact:
It doesnt work that way Vander & DCrazy, you forward those ports and anything that comes into the router from outside the LAN on those ports gets forwarded to the server, it has no effect on the computers inside the LAN.
If that were true, then he wouldnt be able to join (or even list for that matter) ANY PXO games, not just his own.
My guess is his router is handleing it wrong. When I connect to a game on my network via the external IP my router properly forwards to the server computer.
For another example, I actually run an apache web server and forward HTTP port 80 to that server computer. Yet all 5 of the other computers on the network are able to browse websites even tho all the websites use HTTP port 80 (acedumbass' port 88 server excluded). This isnt in theory, this is relaity, I actually do that, so what you guys are saying makes no sense at all or I would'nt be able to post here.
If that were true, then he wouldnt be able to join (or even list for that matter) ANY PXO games, not just his own.
My guess is his router is handleing it wrong. When I connect to a game on my network via the external IP my router properly forwards to the server computer.
For another example, I actually run an apache web server and forward HTTP port 80 to that server computer. Yet all 5 of the other computers on the network are able to browse websites even tho all the websites use HTTP port 80 (acedumbass' port 88 server excluded). This isnt in theory, this is relaity, I actually do that, so what you guys are saying makes no sense at all or I would'nt be able to post here.
- BUBBALOU
- DBB Benefactor
- Posts: 4198
- Joined: Tue Aug 24, 1999 2:01 am
- Location: Dallas Texas USA
- Contact:
you should be able to connect to a server if you host it direct tcp/ip if you can then the server settings is not an issue. you should be able to connect both ways TOO via Broadband ip xxx.xxx.xxx.xxx:2093 and via LAN ip 192.168.1.10x:2093
it's your servers/clients firewall that is an issue and it relates to PXO only. If you disable the Firewall and you can connect VIA PXO ( like you should be able to ) then you need to do some adjustments to the Rules of the Firewall
it's your servers/clients firewall that is an issue and it relates to PXO only. If you disable the Firewall and you can connect VIA PXO ( like you should be able to ) then you need to do some adjustments to the Rules of the Firewall
you know what. i tried joining a direct tcp/ip game just this second. one of the servers was set to host direct tcp/ip when pxo goes down. so i type in the ip and see the game on the list. same error "no response from server"
what's weird to me is how i can telnet in as remote admin but not play direct tcp/ip or pxo.
what's weird to me is how i can telnet in as remote admin but not play direct tcp/ip or pxo.
you know what. i tried joining a direct tcp/ip game just this second. one of the servers was set to host direct tcp/ip when pxo goes down. so i type in the ip and see the game on the list. same error "no response from server"
what's weird to me is how i can telnet in as remote admin but not play direct tcp/ip or pxo.
what's weird to me is how i can telnet in as remote admin but not play direct tcp/ip or pxo.
you know what. i tried joining a direct tcp/ip game just this second. one of the servers was set to host direct tcp/ip when pxo goes down. so i type in the ip and see the game on the list. same error "no response from server"
what's weird to me is how i can telnet in as remote admin but not play direct tcp/ip or pxo.
what's weird to me is how i can telnet in as remote admin but not play direct tcp/ip or pxo.
- Krom
- DBB Database Master
- Posts: 16135
- Joined: Sun Nov 29, 1998 3:01 am
- Location: Camping the energy center. BTW, did you know you can have up to 100 characters in this location box?
- Contact:
I can still play PXO games and games on my own server, actually, I have never seen nettest pass the test.Testing Game port...
The firewall/proxy is not correctly configured for port 2092.
NOTE: It is also possible that the echo server is down, or there is an internet
related problem.
Checking PXO...
Network initted successfully!
Looking up hostname: gt.parallaxonline.com.
Looking up hostname: ut.parallaxonline.com.
Your firewall is setup correctly for the PXO user tracker (UDP port 2092).
Your firewall is setup correctly for the PXO game tracker (UDP port 3445).
Summary:
Warning!
Not everything work correctly while testing your network and firewall/proxy!
Please refer to the information printed above for more details.
Probably because those port 80 connections are initialized from inside the NAT, so the router knows not to forward the packets to a certain machine. Unsolicited packets on a certain port WILL be forwarded to a specific IP address, that's the principle behind port forwarding.
For specifics, see this page and scroll down to "How does it work?". Exactly as I stated above: checks the masquerading table to see if the router has instantiated an outgoing connection on this port; if so, it routes all traffic over that port from the external IP back to the machine that started the "conversation".
For specifics, see this page and scroll down to "How does it work?". Exactly as I stated above: checks the masquerading table to see if the router has instantiated an outgoing connection on this port; if so, it routes all traffic over that port from the external IP back to the machine that started the "conversation".
Even though UDP is connectionless, I'd assume that NAT boxes usually use a masquerading table also for UDP packets - if an UDP packet is coming from the outside from an address where you just sent an UDP packet, or something along those lines, it's considered related to the traffic that originated outbound. I don't know the specifics but that's the idea. Thus, such packets are not unsolicited.
That's how my NAT box works. I have no experience from other ones, though, but if they didn't work that way, you couldn't even play UDP-utilizing games without using port forwarding, or watch video streams transported over UDP.
Which one is given higher preference, the 'stateful matching' (maybe not the same thing, but you get the idea) of UDP packets according to the masquerading table or the port forwarding table might be a bit questionable, but I would be surprised if it weren't the former one.
Anyway, good that you got it working. Would you care to share what the problem was and how you got it fixed?
That's how my NAT box works. I have no experience from other ones, though, but if they didn't work that way, you couldn't even play UDP-utilizing games without using port forwarding, or watch video streams transported over UDP.
Which one is given higher preference, the 'stateful matching' (maybe not the same thing, but you get the idea) of UDP packets according to the masquerading table or the port forwarding table might be a bit questionable, but I would be surprised if it weren't the former one.
Anyway, good that you got it working. Would you care to share what the problem was and how you got it fixed?
problem was that i couldn't join the games i was hosting on the same lan.
i could join direct tcp/ip games if i scanned the internal ip for games but not when i typed in the external ip, even though it showed up on the list.
i could also see the games on the pxo list but not join. every time i would get the error "no response from server"
so i gave all the machines static ips instead of dynamic. the linksys website said i had to use the ip range 192.168.1.1-100 for static ips so i manually set the ip/dns/gateway in the tcp/ip config from windows.
then i added "-pxo 192.168.1.50:209x" in the command line arguments. im not sure if i tried the internal ip with that argument before i changed the ips to static but it works now.
i could join direct tcp/ip games if i scanned the internal ip for games but not when i typed in the external ip, even though it showed up on the list.
i could also see the games on the pxo list but not join. every time i would get the error "no response from server"
so i gave all the machines static ips instead of dynamic. the linksys website said i had to use the ip range 192.168.1.1-100 for static ips so i manually set the ip/dns/gateway in the tcp/ip config from windows.
then i added "-pxo 192.168.1.50:209x" in the command line arguments. im not sure if i tried the internal ip with that argument before i changed the ips to static but it works now.