Take the 2-minute tour ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free, no registration required.

I retired my old 1998 series Pentium II computer running Ubuntu 7 server and replaced it using Virtual Box on a much faster and newer PC. The only job of this server is to run an old school Mud Server. I ghosted the hard drive and recreated it on the virtual box. Everything is running right, EXCEPT, i cannot access the mud server from the outside internet. If i connect using its internal IP in my lan 192.168.1.13, it works, while if i use my external IP, it does not.

The port forwards are set up correctly.

Netstat shows this

kyle@fyremud:/fyremud/current/log$ sudo netstat -antp
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 0.0.0.0:993             0.0.0.0:*               LISTEN     4126/dovecot
tcp        0      0 0.0.0.0:995             0.0.0.0:*               LISTEN     4126/dovecot
tcp        0      0 0.0.0.0:6666            0.0.0.0:*               LISTEN     4043/fyremud
tcp        0      0 192.168.1.13:6666       192.168.1.201:4286      SYN_RECV   -
tcp        0      0 192.168.1.13:6666       192.168.1.201:4264      SYN_RECV   -
tcp        0      0 192.168.1.13:6666       192.168.1.201:4291      SYN_RECV   -
tcp        0      0 192.168.1.13:6666       192.168.1.201:4280      SYN_RECV   -
tcp        0      0 192.168.1.13:6666       192.168.1.201:4298      SYN_RECV   -
tcp        0      0 192.168.1.13:6666       192.168.1.201:4252      SYN_RECV   -
tcp        0      0 0.0.0.0:110             0.0.0.0:*               LISTEN     4126/dovecot
tcp        0      0 0.0.0.0:143             0.0.0.0:*               LISTEN     4126/dovecot
tcp        0      0 0.0.0.0:8080            0.0.0.0:*               LISTEN     4043/fyremud
tcp        0      0 0.0.0.0:21              0.0.0.0:*               LISTEN     4145/proftpd: (acce
tcp        0      0 127.0.0.1:25            0.0.0.0:*               LISTEN     4104/master
tcp        0      0 0.0.0.0:7001            0.0.0.0:*               LISTEN     4043/fyremud
tcp6       0      0 :::22                   :::*                    LISTEN     4034/sshd
tcp6       0    444 ::ffff:192.168.1.13:22  ::ffff:192.168.1.2:3610 ESTABLISHED4201/sshd: kyle [pr

All of the ones marked SYN_RECV are the connections from my desktop to my server using the Internet IP addy. If i connect through the lan, it'll say ESTABLISHED.

I checked the logs of the mud server, it's not reporting connection attempts. This is leading me to beleive I have a foobarred setting in linux, and not the router, the virtual box software, or mud server.

The other thing to point out is that my ethernet card is listed as eth1 ... i'm assuming from the ghosting that eth0 is still associated with the card in the old computer. Could this be my issue, and what would be the fix?

share|improve this question

closed as too localized by Luis Alvarado Jun 16 '13 at 3:37

This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

    
So the mud server is on 192.168.1.13? What's its host's IP address? How is port forwarding on your router set up? How is Virtual Box's networking set up? I think anything you could mention about your configuration might be helpful here. The SYN_RECV says that the server saw the remote trying to open a connection. The fact that it stays that way while we know that the far computer can reach the near one may tell us that the Ack-SYN packet is being dropped on the way back to the far computer after the SYN is received. –  John S Gruber May 23 '12 at 1:34
    
Have you verified that it's inaccessible via the external IP from a machine that is outside the LAN? Not all routers will forward ports in such a way that the outside forwarded port will forward connections from inside the LAN. –  Eliah Kagan May 24 '12 at 5:22
    
I've assumed the netstat you posted was from the mud server running in the virtual box and that it described the unsuccessful connection attempt from 192.168.1.201. The SYN_RECV says that we saw the first packet from 192.168.201 but hadn't received the next logical one in the sequence. I really don't understand your configuration, I'm afraid. The additional interface shouldn't hurt anything if it is in the down state I would think. If it is up and has an IP address it could complicate matters. I assume that the mud server virtual box system can communicate with external web sites and so on? –  John S Gruber May 24 '12 at 5:34
    
@EliahKagan is also right in that in a lot of cases external addresses won't work internally. It seems as if incoming packets work fine but outgoing packets can't reach the outside host. That sounds like a NAT problem or a problem with port forwarding. –  agc93 May 31 '12 at 14:58
    
This question appears to be abandoned and unanswered. If you solved it, please post an answer explaining how it was solved (answering your own questions is not merely permitted, but encouraged when there is no other answer that does the job). If the question no longer applies you may voluntarily delete/close it. –  Eric Carvalho May 26 '13 at 0:35

Browse other questions tagged or ask your own question.