Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Linux, Unix › [Solved] Server won't connect to network
New Posts  All Forums:Forum Nav:

[Solved] Server won't connect to network - Page 3

post #21 of 28
Quote:
Originally Posted by thestraw0039 View Post

I am assuming its the three DNS IPs correct so it would be:

nameserver 111.111.111.111
nameserver 222.222.222.222
nameserver 333.333.333.333

Correct.

iptables default settings should not affect this at all, so unless you have done something to iptables, they should be all fine.

To request a IP from the router using DHCP you need to issue the command: sudo dhclient eth0

If you can ping the router successfully, that means that the connection to the router works fine, but the connection further than that don't seem to work then.

If you can ping 8.8.8.8 but can't ping google.com that means that the connection to the internet works fine, but DNS don't, most probably due to misconfiguration, in which case you should try adding to /etc/resolv.conf the three ip's you mentioned above. If that wont work, try using following ips: 8.8.8.8 and 8.8.4.4 (those are googles public DNS ips which are known to work, I am using them right now)

If you can't ping even 8.8.8.8 but can ping your router, that means that your router refuses to route your connection to the internet. This could be caused because you use a static ip, instead of requesting one from the router using dhcp.
Minimachine
(9 items)
 
  
CPUMotherboardGraphicsRAM
i7-5775C Asus Maximus VII Impact EVGA GTX1080 Founders edition 2x8GB Kingston HyperX 1600Mhz 
Hard DriveMonitorPowerCase
Samsung 950 PRO 512GB M.2 NVMe 3x Asus PB287Q 4k Silverstone 600W Strider SFX NCASE M1 Rev 2 
  hide details  
Reply
Minimachine
(9 items)
 
  
CPUMotherboardGraphicsRAM
i7-5775C Asus Maximus VII Impact EVGA GTX1080 Founders edition 2x8GB Kingston HyperX 1600Mhz 
Hard DriveMonitorPowerCase
Samsung 950 PRO 512GB M.2 NVMe 3x Asus PB287Q 4k Silverstone 600W Strider SFX NCASE M1 Rev 2 
  hide details  
Reply
post #22 of 28
Quote:
Originally Posted by thestraw0039 View Post

I noticed that after I enter the commands
Code:
sudo ifconfig eth0 down
sudo ip addr add 192.168.1.1/24 dev eth0
sudo ifconfig eth0 up

I can ping the router, but I never get an IP from the router, even after the sudo ip route add default via 192.168.1.1.

I know why when you do that, you can ping 192.168.1.1, and that's because you just assigned your computer to BE 192.168.1.1 so it is just pinging itself.

It looks like you have some other problems with your network setup (or possibly a faulty network card).
Router
(12 items)
 
  
Reply
Router
(12 items)
 
  
Reply
post #23 of 28
Thread Starter 
Thanks for all the help guys, I was able to get Linux Mint to load on a Live CD and that connects to the network no problem. One thing I notice though is that the color on the network card is orange and not green, I'm not sure if that is normal or not because I hadn't taken notice of it before. I guess at this point I'll back up the server and re-install. Other weird thing I noticed is that in the Live CD the router still gave the IP address as 192.168.1.100, a rule I deleted, or I thought I did. I may try a router complete reset and see if it helps. Thanks again for all the help +rep to you guys.
post #24 of 28
Thread Starter 
OK, just as I am about to give up, I logged back into my server and just entered sudo dhclient eth0 and it logs onto the network and I have internet. Is there a way to get this to do it automatically?
post #25 of 28
Quote:
Originally Posted by thestraw0039 View Post

OK, just as I am about to give up, I logged back into my server and just entered sudo dhclient eth0 and it logs onto the network and I have internet. Is there a way to get this to do it automatically?

sudo nano /etc/network/interfaces

and add/change:

iface eth0 inet dhcp


example:
Code:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
iface eth0 inet dhcp
Minimachine
(9 items)
 
  
CPUMotherboardGraphicsRAM
i7-5775C Asus Maximus VII Impact EVGA GTX1080 Founders edition 2x8GB Kingston HyperX 1600Mhz 
Hard DriveMonitorPowerCase
Samsung 950 PRO 512GB M.2 NVMe 3x Asus PB287Q 4k Silverstone 600W Strider SFX NCASE M1 Rev 2 
  hide details  
Reply
Minimachine
(9 items)
 
  
CPUMotherboardGraphicsRAM
i7-5775C Asus Maximus VII Impact EVGA GTX1080 Founders edition 2x8GB Kingston HyperX 1600Mhz 
Hard DriveMonitorPowerCase
Samsung 950 PRO 512GB M.2 NVMe 3x Asus PB287Q 4k Silverstone 600W Strider SFX NCASE M1 Rev 2 
  hide details  
Reply
post #26 of 28
Thread Starter 
OMG, I had "iface etho0" in /etc/network/interfaces, I am such a moron. Thank you guys sooooo much for your help, I can't believe I wasted so much of your guys time. I can't give you enough rep. Still doesn't explain what started this problem (I only edited /etc/network/interfaces after this started), but its fixed and its all I care about.
post #27 of 28
It's always the simplest of problem that give us the most trouble tongue.gif
post #28 of 28
Quote:
Originally Posted by thestraw0039 View Post

... "iface etho0" in /etc/network/interfaces ...

I've done this more times than I care to admit... (or spelled auto incorrectly)
Router
(12 items)
 
  
Reply
Router
(12 items)
 
  
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Linux, Unix
Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Linux, Unix › [Solved] Server won't connect to network