Problems with other people connecting
Posted by OniPanda
on Wed 15 Sep 2004 10:54 AM
— 15 posts, 42,359 views.
I've searched through the other posts and tried what they said and what I've been told by other friends and it's still not letting people not on my network connect.
I have a d-link di-514 router and I've gone in and forwarded the ports that needed to be forwarded and still nothing. Someone else told me to try a virtual server, still no luck. I also tried port magic just incase I wasn't forwarding the ports right (This whole router thing confuses me, I'll stick to coding) with no success.
Any help would be appreciated.
Can you connect? Who, of others, can connect? What OS and version are you running? Smaug version? What port(s)?
I'm not very familar with routers, but I'm taking a class in Cisco right now, so I could help somewhat.
I'm running a barely modified Smaug 1.4a (wanted to make sure everything was right before I started majorly changing it) on windows 2000 sp4.
I can connect to localhost and to my lan ip, my other computer can connect to my lan ip, but no one outside of my lan can connect. I know for sure it is the router, I hooked the modem directly to my computer and I and other people can connect fine to my ip.
Well, it's possible that although you've set up port forwarding, you haven't actually opened the ports to outside connections?
Also, are you *sure* that you did the port forwarding correctly?
Check if other people can ping your IP used to connect to the MUD, that may be a problem too.
No, I'm not sure that I've forwarded it correctly. Here's what I have:
http://home.earthlink.net/~onipanda/settings.jpg
Also, would eliminating the additional ports in the code have any effect?
I don't know how your router is meant to work, but at first glance I would say you should be editing the firewall section, not the applications section. That's just a guess though.
Well I reread some things and this looks right to me, but it's still not working:
http://home.earthlink.net/~onipanda/firewall.jpg
And Zeno, other people can ping my computer just fine.
Why do you have two ports for the MUD server? One goes from WAN,* --> LAN,192.168.0.100 port 4000, the other goes from WAN,* --> LAN,24.145.183.21 port 6900. Which one of those is the port you're actually using? The second one doesn't look right at all, in any case.
The second one is indeed wrong, I was trying whatever I could think of to get it to work. I had set the mud to port 6900 but changed it back to port 4000 later. The first one is the recent one that was just added.
As I understand it, shouldn't that work? Shouldn't that be taking incomming connections from the internet and forward them to 192.168.0.100, which is my computer's internal ip, on port 4000, which is the port the mud is on?
I would think so, yes. All I can think of at this point is that your router may have additional settings that we don't know about, or that you have your IP address wrong.
Does your router perhaps have a "reload settings" command? Something that would reinitialize it with the settings you've entered.
It has a reboot button, which I did after I changed the settings.
Here's what ipconfig says:
Host Name . . . . . . . . . . . . : jollyrodger
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 3Com 3C920 Integrated Fast Ethernet
Controller (3C905C-TX Compatible)
Physical Address. . . . . . . . . : xx-xx-xx-xx-xx-xx
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : Wednesday, September 15, 2004 2:16:4
9 AM
Lease Expires . . . . . . . . . . : Wednesday, September 22, 2004 2:16:4
9 AM
Well, with more random testing, I got it working.
I thought I tried it earlier, but I guess I was wrong, but I changed it from WAN,* to *,* and it works now. Had a random idea to tell it to forward my friends ip to me, and left it as *,<ip> and that worked, so I tried it with *,* .
Thanks for your help guys, and hey, at least I learned something, I can now work my router >_>
Hmm. I would've thought that that shouldn't have been a problem, but whatever. :-)
Glad to know that it's working for you!
I have the same router. All I did was set the first IP on the router (me) to a DMZ. I have a number of local firewalls anyway, and it's worked fine since.