Server works on wireless, not when plugged in
- Thread starter Zixxter
- Start date
-
The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord
- Status
I don't want to say how your providers equipment works, but
in every modem/router that I have ever worked on the assigned IP is based on the MAC address of the equipment connecting.
If it's handing out internal network address's (ie 192.168.1.xxx) its may have 192.168.1.101 on a wired connection but will get 192.168.1.105 wirlessly.
This is still the same if your modem is handing out external public IPs.
The MAC ID's of your ethernet card and wirless card are different and from all normal networking protocols it should be impossible for your computer to have the same IP when connected via 2 different mediums.
Try connecting both ways, verify that you have an interconnection by going to google and do an IPCONFIG and verify your IP address.
in every modem/router that I have ever worked on the assigned IP is based on the MAC address of the equipment connecting.
If it's handing out internal network address's (ie 192.168.1.xxx) its may have 192.168.1.101 on a wired connection but will get 192.168.1.105 wirlessly.
This is still the same if your modem is handing out external public IPs.
The MAC ID's of your ethernet card and wirless card are different and from all normal networking protocols it should be impossible for your computer to have the same IP when connected via 2 different mediums.
Try connecting both ways, verify that you have an interconnection by going to google and do an IPCONFIG and verify your IP address.
Ok. I know the server does not use the mac. And yes people connect to your modems externmal (public) IP address. Which you need to port forward to the INTERNAL IP address your router is assigning your computer.
It WILL be giving 2 different IP's to your computer when it connects via 2 different devices.
Just humour me.
Connect wirelessly to the internet.
Open a command prompt. Type in ipconfig /all
Take a screen shot of the IP address for the wireless adapter and post it here. You may need to scroll the screen to find the wireless adpater.
Then turn off your wireless. connect hard wired.
open a command prompt.Type in ipconfig /all
Take a screenshot of the IP address for your wired ethernet connection and post it here.
It WILL be giving 2 different IP's to your computer when it connects via 2 different devices.
Just humour me.
Connect wirelessly to the internet.
Open a command prompt. Type in ipconfig /all
Take a screen shot of the IP address for the wireless adapter and post it here. You may need to scroll the screen to find the wireless adpater.
Then turn off your wireless. connect hard wired.
open a command prompt.Type in ipconfig /all
Take a screenshot of the IP address for your wired ethernet connection and post it here.
, and people are on the server right now so I'm not booting them to test things. I will take a look tomorrow.Alright, you don't need to post them. Just take a look at them and I'm sure you will see they are different.
You probably have your public IP say its 70.70.64.1 port forwarding port 22565 to the internal Pp 192.168.1.101 for example.
But when you switch to hard wired your computer now gets an internal IP of 192.168.1.102 for example, BUT your external IP always stays 70.70.64.1
That is why when you switch to the hardwired people cant see your server and you can't connect. Your router is still forwarding the external IP and port to the wireless IP.
Hope that makes sense.
You probably have your public IP say its 70.70.64.1 port forwarding port 22565 to the internal Pp 192.168.1.101 for example.
But when you switch to hard wired your computer now gets an internal IP of 192.168.1.102 for example, BUT your external IP always stays 70.70.64.1
That is why when you switch to the hardwired people cant see your server and you can't connect. Your router is still forwarding the external IP and port to the wireless IP.
Hope that makes sense.
- Status