I can ping my gateway but I can't access internet and LAN
up vote
-1
down vote
favorite
I was trying to make my server IP static so I changed my /etc/network/interfaces to this:
auto lo eth0
iface lo inet loopback
iface eth0 inet static
address 10.1.1.10
netmask 255.0.0.0
gateway 10.1.1.1
Now I can't access my LAN. My Samba server was working fine before this change and now nobody in LAN can see it. I can ping my gateway (10.1.1.1) but I can't access internet.
Route command: route -n
Destination Gateway Genmask Flags Metric Ref Use Iface
default 10.1.1.1 0.0.0.0 UG 0 0 0 eth0
10.0.0.0 * 25.0.0.0 U 0 0 0 eth0
link-local * 255.255.0.0 U 1000 0 0 eth0
UPDATE:
After restarting my server I can see my samba folders from other computers. Now the only problem that remains is that I can't access internet from it.
networking server
migrated from serverfault.com Jun 2 '14 at 13:19
This question came from our site for system and network administrators.
|
show 4 more comments
up vote
-1
down vote
favorite
I was trying to make my server IP static so I changed my /etc/network/interfaces to this:
auto lo eth0
iface lo inet loopback
iface eth0 inet static
address 10.1.1.10
netmask 255.0.0.0
gateway 10.1.1.1
Now I can't access my LAN. My Samba server was working fine before this change and now nobody in LAN can see it. I can ping my gateway (10.1.1.1) but I can't access internet.
Route command: route -n
Destination Gateway Genmask Flags Metric Ref Use Iface
default 10.1.1.1 0.0.0.0 UG 0 0 0 eth0
10.0.0.0 * 25.0.0.0 U 0 0 0 eth0
link-local * 255.255.0.0 U 1000 0 0 eth0
UPDATE:
After restarting my server I can see my samba folders from other computers. Now the only problem that remains is that I can't access internet from it.
networking server
migrated from serverfault.com Jun 2 '14 at 13:19
This question came from our site for system and network administrators.
what does the commandroute
in the command line tell you?
– mcantsin
Jun 2 '14 at 13:22
Your dns are?smbd
is up,nmbd
is up?
– 2707974
Jun 2 '14 at 13:24
First line: default 10.1.1.1 0.0.0.0 UG 0 0 0 eth0 Second line: 10.0.0.0 * 255.0.0.0 U 0 0 0 eth0 Third line: link-local * 255.255.0.0 U 1000 0 0 eth0 My DNS: 200.175.189.139 and smbd and nmbd are running
– user250327
Jun 2 '14 at 13:24
Hi! Correct me if I'm wrong.. Why is your IP address and gateway the same?? You can't have same IP addresses on two different devices under the same LAN/Subnet. Please clarify on that and about the network a bit. BTW, add the output forroute -n
by editing your question. Its quiet difficult to read when you add as a comment. :)
– AzkerM
Jun 2 '14 at 13:29
Ops it was a mistype in my discription. Sorry, my IP is 10.1.1.10 and the gateway is 10.1.1.1.
– user250327
Jun 2 '14 at 13:30
|
show 4 more comments
up vote
-1
down vote
favorite
up vote
-1
down vote
favorite
I was trying to make my server IP static so I changed my /etc/network/interfaces to this:
auto lo eth0
iface lo inet loopback
iface eth0 inet static
address 10.1.1.10
netmask 255.0.0.0
gateway 10.1.1.1
Now I can't access my LAN. My Samba server was working fine before this change and now nobody in LAN can see it. I can ping my gateway (10.1.1.1) but I can't access internet.
Route command: route -n
Destination Gateway Genmask Flags Metric Ref Use Iface
default 10.1.1.1 0.0.0.0 UG 0 0 0 eth0
10.0.0.0 * 25.0.0.0 U 0 0 0 eth0
link-local * 255.255.0.0 U 1000 0 0 eth0
UPDATE:
After restarting my server I can see my samba folders from other computers. Now the only problem that remains is that I can't access internet from it.
networking server
I was trying to make my server IP static so I changed my /etc/network/interfaces to this:
auto lo eth0
iface lo inet loopback
iface eth0 inet static
address 10.1.1.10
netmask 255.0.0.0
gateway 10.1.1.1
Now I can't access my LAN. My Samba server was working fine before this change and now nobody in LAN can see it. I can ping my gateway (10.1.1.1) but I can't access internet.
Route command: route -n
Destination Gateway Genmask Flags Metric Ref Use Iface
default 10.1.1.1 0.0.0.0 UG 0 0 0 eth0
10.0.0.0 * 25.0.0.0 U 0 0 0 eth0
link-local * 255.255.0.0 U 1000 0 0 eth0
UPDATE:
After restarting my server I can see my samba folders from other computers. Now the only problem that remains is that I can't access internet from it.
networking server
networking server
edited Jun 2 '14 at 14:01
AzkerM
7,76242044
7,76242044
asked Jun 2 '14 at 13:17
user250327
11127
11127
migrated from serverfault.com Jun 2 '14 at 13:19
This question came from our site for system and network administrators.
migrated from serverfault.com Jun 2 '14 at 13:19
This question came from our site for system and network administrators.
what does the commandroute
in the command line tell you?
– mcantsin
Jun 2 '14 at 13:22
Your dns are?smbd
is up,nmbd
is up?
– 2707974
Jun 2 '14 at 13:24
First line: default 10.1.1.1 0.0.0.0 UG 0 0 0 eth0 Second line: 10.0.0.0 * 255.0.0.0 U 0 0 0 eth0 Third line: link-local * 255.255.0.0 U 1000 0 0 eth0 My DNS: 200.175.189.139 and smbd and nmbd are running
– user250327
Jun 2 '14 at 13:24
Hi! Correct me if I'm wrong.. Why is your IP address and gateway the same?? You can't have same IP addresses on two different devices under the same LAN/Subnet. Please clarify on that and about the network a bit. BTW, add the output forroute -n
by editing your question. Its quiet difficult to read when you add as a comment. :)
– AzkerM
Jun 2 '14 at 13:29
Ops it was a mistype in my discription. Sorry, my IP is 10.1.1.10 and the gateway is 10.1.1.1.
– user250327
Jun 2 '14 at 13:30
|
show 4 more comments
what does the commandroute
in the command line tell you?
– mcantsin
Jun 2 '14 at 13:22
Your dns are?smbd
is up,nmbd
is up?
– 2707974
Jun 2 '14 at 13:24
First line: default 10.1.1.1 0.0.0.0 UG 0 0 0 eth0 Second line: 10.0.0.0 * 255.0.0.0 U 0 0 0 eth0 Third line: link-local * 255.255.0.0 U 1000 0 0 eth0 My DNS: 200.175.189.139 and smbd and nmbd are running
– user250327
Jun 2 '14 at 13:24
Hi! Correct me if I'm wrong.. Why is your IP address and gateway the same?? You can't have same IP addresses on two different devices under the same LAN/Subnet. Please clarify on that and about the network a bit. BTW, add the output forroute -n
by editing your question. Its quiet difficult to read when you add as a comment. :)
– AzkerM
Jun 2 '14 at 13:29
Ops it was a mistype in my discription. Sorry, my IP is 10.1.1.10 and the gateway is 10.1.1.1.
– user250327
Jun 2 '14 at 13:30
what does the command
route
in the command line tell you?– mcantsin
Jun 2 '14 at 13:22
what does the command
route
in the command line tell you?– mcantsin
Jun 2 '14 at 13:22
Your dns are?
smbd
is up, nmbd
is up?– 2707974
Jun 2 '14 at 13:24
Your dns are?
smbd
is up, nmbd
is up?– 2707974
Jun 2 '14 at 13:24
First line: default 10.1.1.1 0.0.0.0 UG 0 0 0 eth0 Second line: 10.0.0.0 * 255.0.0.0 U 0 0 0 eth0 Third line: link-local * 255.255.0.0 U 1000 0 0 eth0 My DNS: 200.175.189.139 and smbd and nmbd are running
– user250327
Jun 2 '14 at 13:24
First line: default 10.1.1.1 0.0.0.0 UG 0 0 0 eth0 Second line: 10.0.0.0 * 255.0.0.0 U 0 0 0 eth0 Third line: link-local * 255.255.0.0 U 1000 0 0 eth0 My DNS: 200.175.189.139 and smbd and nmbd are running
– user250327
Jun 2 '14 at 13:24
Hi! Correct me if I'm wrong.. Why is your IP address and gateway the same?? You can't have same IP addresses on two different devices under the same LAN/Subnet. Please clarify on that and about the network a bit. BTW, add the output for
route -n
by editing your question. Its quiet difficult to read when you add as a comment. :)– AzkerM
Jun 2 '14 at 13:29
Hi! Correct me if I'm wrong.. Why is your IP address and gateway the same?? You can't have same IP addresses on two different devices under the same LAN/Subnet. Please clarify on that and about the network a bit. BTW, add the output for
route -n
by editing your question. Its quiet difficult to read when you add as a comment. :)– AzkerM
Jun 2 '14 at 13:29
Ops it was a mistype in my discription. Sorry, my IP is 10.1.1.10 and the gateway is 10.1.1.1.
– user250327
Jun 2 '14 at 13:30
Ops it was a mistype in my discription. Sorry, my IP is 10.1.1.10 and the gateway is 10.1.1.1.
– user250327
Jun 2 '14 at 13:30
|
show 4 more comments
2 Answers
2
active
oldest
votes
up vote
-1
down vote
accepted
You entered the same IP address as the server's address and your gateway. That's probably wrong and if your router's/gateway's IP address is really 10.1.1.1 you now have two devices with the same IP address in your net segment.
I suppose you want to change the server's IP to 10.1.1.2 or 10.1.1.10, depending on your network plan, leaving the address of the gateway to 10.1.1.1
Also, a subnet mask of 255.0.0.0 seems to be horribly, unnecessary big. It's not really a problem, but in the long run you can run into problems with that setting, e.g. if you want to set up some kind of routed VPN. You probably want it to be 255.255.255.0. Check the subnet mast settings on your gateway and set the same on your server.
It was a mistype in my description. Sorry for that. The way it is in my interface file is address 10.1.1.10 and gateway 10.1.1.1. I fixed my description.
– user250327
Jun 2 '14 at 13:32
oh, okay. Can you ping an IP address outside your network? E.g.8.8.8.8
(Google Public DNS)? Just to rule out DNS problems.
– Thomas
Jun 2 '14 at 13:39
Hi! Subnet is always a subnet and it won't make any issues at all though the IP's are too much for a smaller network. VPN won't make any change to the subnet as that is why there're plenty of techniques which can be applied. :)
– AzkerM
Jun 2 '14 at 13:42
I marked this as the correct answer because it was thanks to the 8.8.8.8 ping that made me see why it was not working.
– user250327
Jun 2 '14 at 13:46
Good to hear! May I ask, what the problem was? For future reference... @Subnet: It's not a problem, that's right. But for instance if you try to connect to a routed OpenVPN tunnel, chances are, that either the network subnet or the VPN tunnel net lies in the 10.0.0.0/8 range and then you have a problem :) But you're right, it's not related to the problem at hand.
– Thomas
Jun 2 '14 at 14:25
add a comment |
up vote
0
down vote
I had the same problem with my ubuntu server, i can ping the gateway but not internet.
I solved the problem like this:
-sudo systemctl restart networking
New contributor
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
-1
down vote
accepted
You entered the same IP address as the server's address and your gateway. That's probably wrong and if your router's/gateway's IP address is really 10.1.1.1 you now have two devices with the same IP address in your net segment.
I suppose you want to change the server's IP to 10.1.1.2 or 10.1.1.10, depending on your network plan, leaving the address of the gateway to 10.1.1.1
Also, a subnet mask of 255.0.0.0 seems to be horribly, unnecessary big. It's not really a problem, but in the long run you can run into problems with that setting, e.g. if you want to set up some kind of routed VPN. You probably want it to be 255.255.255.0. Check the subnet mast settings on your gateway and set the same on your server.
It was a mistype in my description. Sorry for that. The way it is in my interface file is address 10.1.1.10 and gateway 10.1.1.1. I fixed my description.
– user250327
Jun 2 '14 at 13:32
oh, okay. Can you ping an IP address outside your network? E.g.8.8.8.8
(Google Public DNS)? Just to rule out DNS problems.
– Thomas
Jun 2 '14 at 13:39
Hi! Subnet is always a subnet and it won't make any issues at all though the IP's are too much for a smaller network. VPN won't make any change to the subnet as that is why there're plenty of techniques which can be applied. :)
– AzkerM
Jun 2 '14 at 13:42
I marked this as the correct answer because it was thanks to the 8.8.8.8 ping that made me see why it was not working.
– user250327
Jun 2 '14 at 13:46
Good to hear! May I ask, what the problem was? For future reference... @Subnet: It's not a problem, that's right. But for instance if you try to connect to a routed OpenVPN tunnel, chances are, that either the network subnet or the VPN tunnel net lies in the 10.0.0.0/8 range and then you have a problem :) But you're right, it's not related to the problem at hand.
– Thomas
Jun 2 '14 at 14:25
add a comment |
up vote
-1
down vote
accepted
You entered the same IP address as the server's address and your gateway. That's probably wrong and if your router's/gateway's IP address is really 10.1.1.1 you now have two devices with the same IP address in your net segment.
I suppose you want to change the server's IP to 10.1.1.2 or 10.1.1.10, depending on your network plan, leaving the address of the gateway to 10.1.1.1
Also, a subnet mask of 255.0.0.0 seems to be horribly, unnecessary big. It's not really a problem, but in the long run you can run into problems with that setting, e.g. if you want to set up some kind of routed VPN. You probably want it to be 255.255.255.0. Check the subnet mast settings on your gateway and set the same on your server.
It was a mistype in my description. Sorry for that. The way it is in my interface file is address 10.1.1.10 and gateway 10.1.1.1. I fixed my description.
– user250327
Jun 2 '14 at 13:32
oh, okay. Can you ping an IP address outside your network? E.g.8.8.8.8
(Google Public DNS)? Just to rule out DNS problems.
– Thomas
Jun 2 '14 at 13:39
Hi! Subnet is always a subnet and it won't make any issues at all though the IP's are too much for a smaller network. VPN won't make any change to the subnet as that is why there're plenty of techniques which can be applied. :)
– AzkerM
Jun 2 '14 at 13:42
I marked this as the correct answer because it was thanks to the 8.8.8.8 ping that made me see why it was not working.
– user250327
Jun 2 '14 at 13:46
Good to hear! May I ask, what the problem was? For future reference... @Subnet: It's not a problem, that's right. But for instance if you try to connect to a routed OpenVPN tunnel, chances are, that either the network subnet or the VPN tunnel net lies in the 10.0.0.0/8 range and then you have a problem :) But you're right, it's not related to the problem at hand.
– Thomas
Jun 2 '14 at 14:25
add a comment |
up vote
-1
down vote
accepted
up vote
-1
down vote
accepted
You entered the same IP address as the server's address and your gateway. That's probably wrong and if your router's/gateway's IP address is really 10.1.1.1 you now have two devices with the same IP address in your net segment.
I suppose you want to change the server's IP to 10.1.1.2 or 10.1.1.10, depending on your network plan, leaving the address of the gateway to 10.1.1.1
Also, a subnet mask of 255.0.0.0 seems to be horribly, unnecessary big. It's not really a problem, but in the long run you can run into problems with that setting, e.g. if you want to set up some kind of routed VPN. You probably want it to be 255.255.255.0. Check the subnet mast settings on your gateway and set the same on your server.
You entered the same IP address as the server's address and your gateway. That's probably wrong and if your router's/gateway's IP address is really 10.1.1.1 you now have two devices with the same IP address in your net segment.
I suppose you want to change the server's IP to 10.1.1.2 or 10.1.1.10, depending on your network plan, leaving the address of the gateway to 10.1.1.1
Also, a subnet mask of 255.0.0.0 seems to be horribly, unnecessary big. It's not really a problem, but in the long run you can run into problems with that setting, e.g. if you want to set up some kind of routed VPN. You probably want it to be 255.255.255.0. Check the subnet mast settings on your gateway and set the same on your server.
answered Jun 2 '14 at 13:30
Thomas
14
14
It was a mistype in my description. Sorry for that. The way it is in my interface file is address 10.1.1.10 and gateway 10.1.1.1. I fixed my description.
– user250327
Jun 2 '14 at 13:32
oh, okay. Can you ping an IP address outside your network? E.g.8.8.8.8
(Google Public DNS)? Just to rule out DNS problems.
– Thomas
Jun 2 '14 at 13:39
Hi! Subnet is always a subnet and it won't make any issues at all though the IP's are too much for a smaller network. VPN won't make any change to the subnet as that is why there're plenty of techniques which can be applied. :)
– AzkerM
Jun 2 '14 at 13:42
I marked this as the correct answer because it was thanks to the 8.8.8.8 ping that made me see why it was not working.
– user250327
Jun 2 '14 at 13:46
Good to hear! May I ask, what the problem was? For future reference... @Subnet: It's not a problem, that's right. But for instance if you try to connect to a routed OpenVPN tunnel, chances are, that either the network subnet or the VPN tunnel net lies in the 10.0.0.0/8 range and then you have a problem :) But you're right, it's not related to the problem at hand.
– Thomas
Jun 2 '14 at 14:25
add a comment |
It was a mistype in my description. Sorry for that. The way it is in my interface file is address 10.1.1.10 and gateway 10.1.1.1. I fixed my description.
– user250327
Jun 2 '14 at 13:32
oh, okay. Can you ping an IP address outside your network? E.g.8.8.8.8
(Google Public DNS)? Just to rule out DNS problems.
– Thomas
Jun 2 '14 at 13:39
Hi! Subnet is always a subnet and it won't make any issues at all though the IP's are too much for a smaller network. VPN won't make any change to the subnet as that is why there're plenty of techniques which can be applied. :)
– AzkerM
Jun 2 '14 at 13:42
I marked this as the correct answer because it was thanks to the 8.8.8.8 ping that made me see why it was not working.
– user250327
Jun 2 '14 at 13:46
Good to hear! May I ask, what the problem was? For future reference... @Subnet: It's not a problem, that's right. But for instance if you try to connect to a routed OpenVPN tunnel, chances are, that either the network subnet or the VPN tunnel net lies in the 10.0.0.0/8 range and then you have a problem :) But you're right, it's not related to the problem at hand.
– Thomas
Jun 2 '14 at 14:25
It was a mistype in my description. Sorry for that. The way it is in my interface file is address 10.1.1.10 and gateway 10.1.1.1. I fixed my description.
– user250327
Jun 2 '14 at 13:32
It was a mistype in my description. Sorry for that. The way it is in my interface file is address 10.1.1.10 and gateway 10.1.1.1. I fixed my description.
– user250327
Jun 2 '14 at 13:32
oh, okay. Can you ping an IP address outside your network? E.g.
8.8.8.8
(Google Public DNS)? Just to rule out DNS problems.– Thomas
Jun 2 '14 at 13:39
oh, okay. Can you ping an IP address outside your network? E.g.
8.8.8.8
(Google Public DNS)? Just to rule out DNS problems.– Thomas
Jun 2 '14 at 13:39
Hi! Subnet is always a subnet and it won't make any issues at all though the IP's are too much for a smaller network. VPN won't make any change to the subnet as that is why there're plenty of techniques which can be applied. :)
– AzkerM
Jun 2 '14 at 13:42
Hi! Subnet is always a subnet and it won't make any issues at all though the IP's are too much for a smaller network. VPN won't make any change to the subnet as that is why there're plenty of techniques which can be applied. :)
– AzkerM
Jun 2 '14 at 13:42
I marked this as the correct answer because it was thanks to the 8.8.8.8 ping that made me see why it was not working.
– user250327
Jun 2 '14 at 13:46
I marked this as the correct answer because it was thanks to the 8.8.8.8 ping that made me see why it was not working.
– user250327
Jun 2 '14 at 13:46
Good to hear! May I ask, what the problem was? For future reference... @Subnet: It's not a problem, that's right. But for instance if you try to connect to a routed OpenVPN tunnel, chances are, that either the network subnet or the VPN tunnel net lies in the 10.0.0.0/8 range and then you have a problem :) But you're right, it's not related to the problem at hand.
– Thomas
Jun 2 '14 at 14:25
Good to hear! May I ask, what the problem was? For future reference... @Subnet: It's not a problem, that's right. But for instance if you try to connect to a routed OpenVPN tunnel, chances are, that either the network subnet or the VPN tunnel net lies in the 10.0.0.0/8 range and then you have a problem :) But you're right, it's not related to the problem at hand.
– Thomas
Jun 2 '14 at 14:25
add a comment |
up vote
0
down vote
I had the same problem with my ubuntu server, i can ping the gateway but not internet.
I solved the problem like this:
-sudo systemctl restart networking
New contributor
add a comment |
up vote
0
down vote
I had the same problem with my ubuntu server, i can ping the gateway but not internet.
I solved the problem like this:
-sudo systemctl restart networking
New contributor
add a comment |
up vote
0
down vote
up vote
0
down vote
I had the same problem with my ubuntu server, i can ping the gateway but not internet.
I solved the problem like this:
-sudo systemctl restart networking
New contributor
I had the same problem with my ubuntu server, i can ping the gateway but not internet.
I solved the problem like this:
-sudo systemctl restart networking
New contributor
New contributor
answered Dec 5 at 1:59
mostafa maoui
1
1
New contributor
New contributor
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f475742%2fi-can-ping-my-gateway-but-i-cant-access-internet-and-lan%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
what does the command
route
in the command line tell you?– mcantsin
Jun 2 '14 at 13:22
Your dns are?
smbd
is up,nmbd
is up?– 2707974
Jun 2 '14 at 13:24
First line: default 10.1.1.1 0.0.0.0 UG 0 0 0 eth0 Second line: 10.0.0.0 * 255.0.0.0 U 0 0 0 eth0 Third line: link-local * 255.255.0.0 U 1000 0 0 eth0 My DNS: 200.175.189.139 and smbd and nmbd are running
– user250327
Jun 2 '14 at 13:24
Hi! Correct me if I'm wrong.. Why is your IP address and gateway the same?? You can't have same IP addresses on two different devices under the same LAN/Subnet. Please clarify on that and about the network a bit. BTW, add the output for
route -n
by editing your question. Its quiet difficult to read when you add as a comment. :)– AzkerM
Jun 2 '14 at 13:29
Ops it was a mistype in my discription. Sorry, my IP is 10.1.1.10 and the gateway is 10.1.1.1.
– user250327
Jun 2 '14 at 13:30