Search:

I don't think that disabling ipv6 is a good idea. The central pool of ipv4 addresses officially ran dry (one week ago) after the Internet Assigned Numbers Authority (IANA) allocated the last...

Install nmap and run:

$ sudo nmap -PO 192.168.1.0/24

Note the nmap option -PO (Papa Oscar) and not P zero

I would not recommend to disable ipv6. You might need it in the very near future.
http://tech.slashdot.org/story/11/02/01/0036227/Last-Available-IPv4-Blocks-Allocated

And if you do, make a note...

First possible fix: add this line in /etc/resolv.conf and tell us if it works faster:

options single-request

That's because gnome network manager changes the default gateway. If you do a

$ ip route ls
I bet that the default gateway is routed through the tun0 interface.

To change this,...

There is nothing wrong in the way Ubuntu (and Debian BTW) format their DNS requests. But there is definitely something wrong the way some nameservers discard the quad-A request without sending a...

Can you post the result of the ipconfig --all command on the windows machine.

May be you have a ill-conceived firewall on the Ubuntu box? What's the output of:

$ sudo iptables-save

Strange, your Ubuntu box seems to be blocked out. Can you check what the other computers have as network setup?

If they are windows I think that the command is ipconfig -all

Simply nmap.

$ nmap ip_server
Be patient as nmap will scan all ports. You can shorten the scan by specifying the port:

$ nmap -p 3306 ip_server

From the above output we can see that you have received an IP address lease from the DHCP server, that it was assigned to your eth0 interface, that the route to the gateway is built and that you can...

That's strange because the dhcp request seems to work when you execute dhclient meaning that your dhcp server responds to your request.

Try again this:

$ sudo dhclient; ip address ls; ip route...

If your interfaces file only contains these two lines, it means that network-manager is in charge of bringing your interfaces up. Why don't you use NM for the other interfaces (right click on the NM...

And can you ping your gateway?

$ ping -C 2 -W 3 192.168.0.1

@dineshs routing tables have been posted (several) times above. (S)He has not route to the gateway.

@ OP Just try to add that route as I suggested above, and then we will see why the route is not...

Let's see with:

ping -c 2 -W 5 8.8.8.8

Result of:

$ dig google.com
$ dig @8.8.8.8 google.com

It means that you have received 192.168.0.100 from 192.168.0.1, the dhcp server.

What's the result of:

$ ip address ls
$ ip route ls
$ sudo cat /etc/resolv.conf

run and post result of:

$ sudo dhclient

What have you done so far?

You have no route to your gateway. First try this:

$ sudo ip route add default via 192.168.1.1

If it works (i.e. you are connected to internet) we will see why the route is not automatically...

Well done!

Now you just have to add a --source option to tighten your security and you are set.


iptables -I INPUT -p xxx --source 10.0.1.0/30 --dport xxx -j ACCEPT

So it is a firewall issue apparently. You can start with simple rules:


iptables -I INPUT -p tcp --dport 135 -j ACCEPT
iptables -I INPUT -p udp --dport 137 -j ACCEPT
iptables -I INPUT -p udp...

I stand corrected. Subnet calculation is not my forte. After checking it seems that both your host's ip and your gateway _are_ on the same subnet. A netmask of 255.255.248.0 produces a subnet ip...

As you suspected above, the firewall is not blocking anything.

From the client, run:

$ smbtree -Nor

$ smbclient -NL ip_samba_server

If no luck with that, drop your samba security level by...

Your gateway seems to be on another subnet. Check your routing tables and netmask.