same site - can and can't access it on different points on internal network

M

milomak

Honorary Master
Joined
May 23, 2007
Messages
12,571
Reaction score
92
hmm this is is strange and not an isp fault. though it may be router related.

Code: 
fibre -----> router -----> pc ------------> no site
                |
               ap -------> laptop (wifi) -> site accessed

router address is 192.168.1.1

ap has dns set as 192.168.1.1 as well

on pc (mac/win/linux) i am using safari/edge/konqueror

on laptop, i am using the same firefox profile on both
 
if you traceroute to the site what do u get?

Also u sure you're not plugging into a WAN or other reserved ethernet port on the Router and just arent having traffic routed?
 
on the pc (linux)

Code: 
traceroute neuvoo.co.za
neuvoo.co.za: Name or service not known
Cannot handle "host" cmdline arg `neuvoo.co.za' on position 1 (argc 1)

also
Code: 
$ cat /etc/hosts
127.0.0.1       localhost
127.0.1.1       mac

# The following lines are desirable for IPv6 capable hosts
::1     localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
 
try setting your dns as 8.8.8.8? Just guessing...:giggle:
 
windows on the laptop

Code: 
>tracert neuvoo.co.za

Tracing route to neuvoo.co.za [54.39.189.62]
over a maximum of 30 hops:

  1     1 ms   128 ms     1 ms  192.168.1.1
  2     3 ms     4 ms     3 ms  102.132.136.1
  3     *        5 ms     5 ms  154.0.3.97
  4     2 ms     2 ms     2 ms  154.0.5.2
  5     2 ms     1 ms     1 ms  154.0.5.129
  6     2 ms     2 ms     2 ms  154.0.5.147
  7   192 ms    37 ms    28 ms  197.96.214.112
  8   178 ms   206 ms   200 ms  core1b-dock-ten-0-4-3-0.ip.isnet.net [168.209.100.17]
  9     *        *        *     Request timed out.
 10   390 ms   247 ms   247 ms  be100-1298.nwk-5-a9.nj.us [192.99.146.133]
 11   256 ms   256 ms   254 ms  be100-1323.bhs-g2-nc5.qc.ca [192.99.146.138]
 12     *        *        *     Request timed out.
 13   293 ms   255 ms   255 ms  be7.bhs-z2g2-a75.qc.ca [178.32.135.225]
 14   266 ms   253 ms   253 ms  po7.bhs-z2b6-a70.qc.ca [158.69.44.246]
 15   268 ms   254 ms   255 ms
been stuck on step 15 for more than 5 min

yet site resolves in ff
 
On the Linux PC try: traceroute 54.39.189.62

Does it work now?

EDIT: if it does, please show the output of cat /etc/resolv.conf
 
neoprema said:
On the Linux PC try: traceroute 54.39.189.62

Does it work now?
Click to expand...

well it indeed does
Code: 
$ traceroute 54.39.189.62
traceroute to 54.39.189.62 (54.39.189.62), 30 hops max, 60 byte packets
 1  _gateway (192.168.1.1)  0.539 ms  0.513 ms  0.549 ms
 2  102.132.136.1 (102.132.136.1)  3.664 ms  3.831 ms  4.021 ms
 3  154.0.3.97 (154.0.3.97)  5.859 ms * *
 4  154.0.5.1 (154.0.5.1)  2.210 ms 154.0.5.2 (154.0.5.2)  2.122 ms  2.119 ms
 5  154.0.5.129 (154.0.5.129)  2.116 ms 154.0.5.130 (154.0.5.130)  2.732 ms  2.694 ms
 6  154.0.1.138 (154.0.1.138)  2.511 ms  2.329 ms  1.629 ms
 7  197.96.214.112 (197.96.214.112)  4.500 ms  4.324 ms  4.266 ms
 8  core1b-dock-ten-0-4-3-0.ip.isnet.net (168.209.100.17)  177.902 ms  174.351 ms  177.875 ms
 9  * * *
10  be100-1298.nwk-5-a9.nj.us (192.99.146.133)  246.565 ms  246.520 ms  246.482 ms
11  be100-1323.bhs-g2-nc5.qc.ca (192.99.146.138)  253.420 ms  253.376 ms  254.152 ms
12  * * *
13  be7.bhs-z2g2-a75.qc.ca (178.32.135.225)  255.770 ms  255.026 ms  254.811 ms
14  po7.bhs-z2b6-a70.qc.ca (158.69.44.246)  253.035 ms  253.040 ms  253.000 ms
15  158.69.45.107 (158.69.45.107)  254.174 ms  254.128 ms  254.063 ms
16  158.69.61.4 (158.69.61.4)  256.455 ms  256.143 ms  256.452 ms
17  54.39.189.62 (54.39.189.62)  245.453 ms  244.568 ms  244.622 ms

EDIT: if it does, please show the output of cat /etc/resolv.conf
Click to expand...

here you go
Code: 
$ cat /etc/resolv.conf 
# Generated by NetworkManager
search 192.168.1.1
nameserver 192.168.1.1
 
show me output of:

nslookup neuvoo.co.za 192.168.1.1

and

nslookup neuvoo.co.za 8.8.8.8

both from the linux pc.
thx
 
Also, your "search" in resolv.conf should be showing a domain or local hostname, not an IP

do sudo nano /etc/resolv.conf
OR
sudo gedit /etc/resolv.conf

delete the line that says "search 192.168.1.1"

save the file and try traceroute neuvoo.co.za again and see if it works.
 
will adress you now neoprema

from the laptop (linux)

Code: 
~$ traceroute neuvoo.co.za
neuvoo.co.za: Temporary failure in name resolution
Cannot handle "host" cmdline arg `neuvoo.co.za' on position 1 (argc 1)

Code: 
$ traceroute 54.39.189.62
traceroute to 54.39.189.62 (54.39.189.62), 30 hops max, 60 byte packets
1  _gateway (192.168.1.1)  1.881 ms  1.805 ms  2.097 ms
2  102.132.136.1 (102.132.136.1)  3.878 ms  3.707 ms  3.886 ms
3  154.0.3.97 (154.0.3.97)  4.468 ms  4.231 ms  4.650 ms
4  154.0.5.2 (154.0.5.2)  3.260 ms 154.0.5.1 (154.0.5.1)  3.245 ms 154.0.5.2 (154.0.5.2)  3.183 ms
5  154.0.5.130 (154.0.5.130)  3.168 ms  3.123 ms  3.106 ms
6  154.0.5.147 (154.0.5.147)  3.081 ms  1.537 ms  1.902 ms
7  197.96.214.112 (197.96.214.112)  2.909 ms  7.210 ms  7.207 ms
8  core1b-dock-ten-0-4-3-0.ip.isnet.net (168.209.100.17)  207.759 ms  207.762 ms  207.749 ms
9  * * *
10  be100-1298.nwk-5-a9.nj.us (192.99.146.133)  248.095 ms  248.125 ms  248.126 ms
11  be100-1323.bhs-g2-nc5.qc.ca (192.99.146.138)  303.034 ms  303.068 ms  303.036 ms
12  * * *
13  be7.bhs-z2g2-a75.qc.ca (178.32.135.225)  255.882 ms  255.900 ms  255.832 ms
14  po7.bhs-z2b6-a70.qc.ca (158.69.44.246)  253.478 ms  253.877 ms  253.829 ms
15  158.69.45.107 (158.69.45.107)  254.857 ms  254.752 ms  256.499 ms
16  158.69.61.4 (158.69.61.4)  258.036 ms  258.041 ms  281.983 ms
17  54.39.189.62 (54.39.189.62)  279.611 ms  279.574 ms  258.562 ms

Code: 
$ cat /etc/resolv.conf
# Generated by NetworkManager
search 192.168.1.1
nameserver 192.168.1.1
 
from the laptop (linux)

$ nslookup neuvoo.co.za 192.168.1.1
Code: 
;; Truncated, retrying in TCP mode.
;; Connection to 192.168.1.1#53(192.168.1.1) for neuvoo.co.za failed: connection refused.

$ nslookup neuvoo.co.za 8.8.8.8
Code: 
Server:         8.8.8.8
Address:        8.8.8.8#53

Non-authoritative answer:
Name:   neuvoo.co.za
Address: 54.39.180.68
Name:   neuvoo.co.za
Address: 54.39.57.41
Name:   neuvoo.co.za
Address: 142.44.164.230
Name:   neuvoo.co.za
Address: 54.39.57.37
Name:   neuvoo.co.za
Address: 142.44.244.152
Name:   neuvoo.co.za
Address: 142.44.164.24
Name:   neuvoo.co.za
Address: 54.39.57.5
Name:   neuvoo.co.za
Address: 54.39.59.121
Name:   neuvoo.co.za
Address: 54.39.186.68
Name:   neuvoo.co.za
Address: 54.39.56.120
Name:   neuvoo.co.za
Address: 142.44.164.236
Name:   neuvoo.co.za
Address: 54.39.57.36
Name:   neuvoo.co.za
Address: 54.39.59.115
Name:   neuvoo.co.za
Address: 192.99.4.68
Name:   neuvoo.co.za
Address: 192.99.6.114
Name:   neuvoo.co.za
Address: 142.44.164.222
Name:   neuvoo.co.za
Address: 54.39.189.62
Name:   neuvoo.co.za
Address: 54.39.59.114
Name:   neuvoo.co.za
Address: 198.27.69.35
Name:   neuvoo.co.za
Address: 192.99.0.219
Name:   neuvoo.co.za
Address: 54.39.57.40
Name:   neuvoo.co.za
Address: 192.99.6.69
Name:   neuvoo.co.za
Address: 54.39.184.164
Name:   neuvoo.co.za
Address: 192.99.6.56
Name:   neuvoo.co.za
Address: 192.99.0.221
Name:   neuvoo.co.za
Address: 54.39.187.238
Name:   neuvoo.co.za
Address: 54.39.59.118
 
ok for some reason you are being denied DNS port access to the router on 192.168.1.1 - I'm not sure why.

If you do this:

sudo echo "nameserver 8.8.8.8" > /etc/resolv.conf

Chances are everything will start working fine on the linux pc? (until next reboot)
 
neoprema said:
Also, your "search" in resolv.conf should be showing a domain or local hostname, not an IP

do sudo nano /etc/resolv.conf
OR
sudo gedit /etc/resolv.conf

delete the line that says "search 192.168.1.1"

save the file and try traceroute neuvoo.co.za again and see if it works.
Click to expand...

from laptop (linux)

# cat /etc/resolv.conf
Code: 
# Generated by NetworkManager
#search 192.168.1.1
nameserver 192.168.1.1

don't i need to restart some service?
 
no resolv.conf changes apply immediately but that wont work as you cant reach 192.168.1.1 on port 53 for NS lookups for some reason.

Therefore you need to change the file to:

nameserver 8.8.8.8

using the command I showed or just manually. If you save that, everything should start working on the Linux PC
 
neoprema said:
ok for some reason you are being denied DNS port access to the router on 192.168.1.1 - I'm not sure why.

If you do this:

sudo echo "nameserver 8.8.8.8" > /etc/resolv.conf

Chances are everything will start working fine on the linux pc? (until next reboot)
Click to expand...
and indeed that works

but why this specific site?

there was a reason i tested on safari, edge and konqueror because these are not web apps i use so i figure they cannot be impacted by the things which are browser specific.

but again on the same pc - macos, linux and windows have the same behaviour. i can't see what they could be possibly sharing but some router setting.

edit - i assume it goes down the list. if 192.168.1.1 can't find the site it then goes to 8.8.8.8?
 
i could add that to the startup sequence but it would leave me highly unsatisfied as to what the root issue is.

thanks though that i know how to have a workaround.
 
where is is the windows hosts file? I want to compare my laptop to the pc
 
Just to understand;

When you're on ETHERNET connection it did not work right?

SAME machine/OSs but on WI-FI and they do work right?
 
Linux:

/etc/resolv.conf

nameserver 8.8.8.8


Windows:

c:\Windows\System32\Drivers\etc\hosts.

You need to open this file and edit while running notepad in administrator mode.
 
neoprema said:
Just to understand;

When you're on ETHERNET connection it did not work right?

SAME machine/OSs but on WI-FI and they do work right?
Click to expand...
so on the pc (macos/linux/windows). tried on ethernet. and then tried on wifi. so one was on and the other was off

same problem.

same machine. the pc.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X