Happymanny1986
Dabbler
- Joined
- Jul 16, 2015
- Messages
- 16
Hello everyone, I recently reinstalled FreeNAS from scratch after my motherboard failed. I'm sure there were better options, but there wasn't much on the server other than my teamspeak server.
While I was waiting for a replacement motherboard to show up I installed TS server on my Windows desktop and changed my port forwarding settings to accommodate.
The new motherboard came in and after installing Freenas 9.3 (same version as before) I created a jail and gave it an IP (xxx.30) on my network, and installed a Teamspeak Server in that jail, like I had done previously on my original FreeNAS installation. Everything seemed to be running smoothly. I was able to connect to and configure my TS server within my network from my windows client. I changed my port forwarding settings to point back to my jail thinking that the job was done, which is where my problems start - I can no longer connect to my TeamSpeak server from the internet. Everything still works within my LAN it is just not accessable over the net.
Troubleshooting steps taken:
Disabled firewall on router - Unsuccessful
Disabled firewall on client PC - Unsuccessful
Double checked port forwarding settings - Set Correctly
Ping my public IP address from within the jail - Successful
Ping internet from within the jail - Successful (pinged google.com)
Ping my client from within jail - Successful
Ping jail from within client - Successful
Checked Default Gateway for jail - points at router xxx.1
Ping my web address to check DDNS function - ping returns my public IP properly
Try to access TS server using DDNS address - Unsuccessful
Try to access TS server using static IP - Unsuccessful
One test that I found strange is I used advanced IP scanner to see if my jail would show up on the network, which it does, but instead of the hostname being "Teamspeak" (which is the name of the jail) the hostname is "NAS" which is the hostname of the FreeNAS install. In fact I can access the FreeNAS gui by navigating to the jail IP address. I can also access my windows share through the jail IP address, which seems really fishy to me especially considering it's in a completely different dataset. My jail used to show up with the name Teamspeak on the network, and it was never browseable through windows file sharing before. I was under the impression that jails are supposed to be independent of the rest of the OS normally, so I think the problem is related to this.
Does anyone have any ideas of what is going on here? Any help would be greatly appreciated, I'd like to have this server back up and running by this afternoon if at possible.
While I was waiting for a replacement motherboard to show up I installed TS server on my Windows desktop and changed my port forwarding settings to accommodate.
The new motherboard came in and after installing Freenas 9.3 (same version as before) I created a jail and gave it an IP (xxx.30) on my network, and installed a Teamspeak Server in that jail, like I had done previously on my original FreeNAS installation. Everything seemed to be running smoothly. I was able to connect to and configure my TS server within my network from my windows client. I changed my port forwarding settings to point back to my jail thinking that the job was done, which is where my problems start - I can no longer connect to my TeamSpeak server from the internet. Everything still works within my LAN it is just not accessable over the net.
Troubleshooting steps taken:
Disabled firewall on router - Unsuccessful
Disabled firewall on client PC - Unsuccessful
Double checked port forwarding settings - Set Correctly
Ping my public IP address from within the jail - Successful
Ping internet from within the jail - Successful (pinged google.com)
Ping my client from within jail - Successful
Ping jail from within client - Successful
Checked Default Gateway for jail - points at router xxx.1
Ping my web address to check DDNS function - ping returns my public IP properly
Try to access TS server using DDNS address - Unsuccessful
Try to access TS server using static IP - Unsuccessful
One test that I found strange is I used advanced IP scanner to see if my jail would show up on the network, which it does, but instead of the hostname being "Teamspeak" (which is the name of the jail) the hostname is "NAS" which is the hostname of the FreeNAS install. In fact I can access the FreeNAS gui by navigating to the jail IP address. I can also access my windows share through the jail IP address, which seems really fishy to me especially considering it's in a completely different dataset. My jail used to show up with the name Teamspeak on the network, and it was never browseable through windows file sharing before. I was under the impression that jails are supposed to be independent of the rest of the OS normally, so I think the problem is related to this.
Does anyone have any ideas of what is going on here? Any help would be greatly appreciated, I'd like to have this server back up and running by this afternoon if at possible.
Last edited: