Local network: ping impossible
Solved
der
-
caro666 Posted messages 8 Status Membre -
caro666 Posted messages 8 Status Membre -
Hello,
I have two computers behind a Hitachi AH4021 router.
Both access the internet without any problem (via WiFi).
However, pinging between the 2 PCs is impossible, so no file sharing...
Why?
I'm desperately looking for answers, but I can't find anything...!
Could you please help me?
Thank you so much.
I have two computers behind a Hitachi AH4021 router.
Both access the internet without any problem (via WiFi).
However, pinging between the 2 PCs is impossible, so no file sharing...
Why?
I'm desperately looking for answers, but I can't find anything...!
Could you please help me?
Thank you so much.
13 réponses
Why are you all on GMT +2, while in France we are on +1?
To try to answer your question:
If I understand correctly:
- 2 devices connected to a router, one at 192.168.1.2 and the other at 192.168.1.3. Your mask is good... So your PCs are connected to the router via cable. Is it your router that handles the Wi-Fi connection, or do you have devices on your 2 PCs (like USB Wi-Fi keys)? If it's your router that manages everything, configure it; if it doesn't work, remove it and try without.
To try to answer your question:
If I understand correctly:
- 2 devices connected to a router, one at 192.168.1.2 and the other at 192.168.1.3. Your mask is good... So your PCs are connected to the router via cable. Is it your router that handles the Wi-Fi connection, or do you have devices on your 2 PCs (like USB Wi-Fi keys)? If it's your router that manages everything, configure it; if it doesn't work, remove it and try without.
juste, the pfff,
he wasn't dismissive in my mind, but just because of the repetition.
it's because it was the second time I was talking about the firewall or rather lanlard had already mentioned it before.
this issue (one-way ping) is FORCIBLY due to a firewall problem.
each firewall should allow local traffic unconditionally, only filtering what comes from or is destined for the internet.
otherwise, ports 135 to 139, plus 445 yes, are essential for the windows network.
in fact, for 2K /XP 135 and 445 are sufficient.
137,138,139 are only used for netbios over tcpip.
for telnet (23) check in the router administration to disable administration on the wan side, if possible, otherwise just keep what is useful for administration and use strong passwords (not admin).
--
and ... Voila Voila Voila!
he wasn't dismissive in my mind, but just because of the repetition.
it's because it was the second time I was talking about the firewall or rather lanlard had already mentioned it before.
this issue (one-way ping) is FORCIBLY due to a firewall problem.
each firewall should allow local traffic unconditionally, only filtering what comes from or is destined for the internet.
otherwise, ports 135 to 139, plus 445 yes, are essential for the windows network.
in fact, for 2K /XP 135 and 445 are sufficient.
137,138,139 are only used for netbios over tcpip.
for telnet (23) check in the router administration to disable administration on the wan side, if possible, otherwise just keep what is useful for administration and use strong passwords (not admin).
--
and ... Voila Voila Voila!
Good evening
I realize that I hadn't provided the update on my "research".
I found that both PCs were experiencing ping issues.
I tried with another modem/router, and it worked very well.
Moreover, some time later, the router unexpectedly went into blackout...
These were actually signs of distress from a modem/router that was at the end of its life.
It was replaced without any difficulties by my ISP, and now it works smoothly.
Thank you for your help.
See you soon.
I realize that I hadn't provided the update on my "research".
I found that both PCs were experiencing ping issues.
I tried with another modem/router, and it worked very well.
Moreover, some time later, the router unexpectedly went into blackout...
These were actually signs of distress from a modem/router that was at the end of its life.
It was replaced without any difficulties by my ISP, and now it works smoothly.
Thank you for your help.
See you soon.
Hello,
First, I would like to tell brupala that the disdainful "pfff" is not necessary, knowing that I only want to learn. I am not one of those small-minded pretentious people who want to show off in computing just because they know VB and a few commands in Linux... I am more than willing to humble myself in front of your knowledge and experience.
Furthermore, I am glad to have found my mistake thanks to your message. It turns out that I had disabled the firewalls the other day and the ping was not going through... another mistake on my part? Maybe... Anyway, I have disabled the firewalls now and it works, well, 3 pings out of 4... There's still one that fails.
If I’m not abusing, do I need to open ports 137 to 139 on each firewall now?
Thank you for your help.
See you soon!
PS: Regarding port forwarding, I wasn't running both PCs at the same time. So I thought that since computer 1.2 was not connected, it would forward to 1.3 with the existing second rule... But apparently not...
PS2: When I do an online scan, it tells me that port 23 (among others) is open. How do I close it? I don't use telnet. We can only open ports via the interface, and normally what is not specifically opened is closed. Except for 21, 22, 23, and 80. I haven't created a special rule, yet it's still open...
First, I would like to tell brupala that the disdainful "pfff" is not necessary, knowing that I only want to learn. I am not one of those small-minded pretentious people who want to show off in computing just because they know VB and a few commands in Linux... I am more than willing to humble myself in front of your knowledge and experience.
Furthermore, I am glad to have found my mistake thanks to your message. It turns out that I had disabled the firewalls the other day and the ping was not going through... another mistake on my part? Maybe... Anyway, I have disabled the firewalls now and it works, well, 3 pings out of 4... There's still one that fails.
If I’m not abusing, do I need to open ports 137 to 139 on each firewall now?
Thank you for your help.
See you soon!
PS: Regarding port forwarding, I wasn't running both PCs at the same time. So I thought that since computer 1.2 was not connected, it would forward to 1.3 with the existing second rule... But apparently not...
PS2: When I do an online scan, it tells me that port 23 (among others) is open. How do I close it? I don't use telnet. We can only open ports via the interface, and normally what is not specifically opened is closed. Except for 21, 22, 23, and 80. I haven't created a special rule, yet it's still open...
Hello everyone.
Thank you for your responses.
I think my problem is more complicated. I've enabled file sharing etc... none of this is new to me, I'm used to doing it.
I believe the issue lies with the router, which is blocking connections from the local network. It only allows individual connections from each PC to the outside...
I don't see any settings on the router that would allow the PCs connected to it to communicate with each other...
Does anyone know the HITACHI AH4021?
The simplest way is to schematically outline my issue, I'm having a hard time explaining:
http://ge.wattelier.club.fr/reseau.JPG
Thanks a lot
See you soon
PS: I'm wondering if the router isn't malfunctioning, as 192.168.1.3 cannot access the internet via port 3728 despite my NAT rule defined as follows:
3728 - 3728 - TCP - 3728 - 3728 from: 192.168.1.3
While the same NAT rule works for 192.168.1.2:
3728 - 3728 - TCP - 3728 - 3728 from: 192.168.1.2
Strange, right?
Thank you for your responses.
I think my problem is more complicated. I've enabled file sharing etc... none of this is new to me, I'm used to doing it.
I believe the issue lies with the router, which is blocking connections from the local network. It only allows individual connections from each PC to the outside...
I don't see any settings on the router that would allow the PCs connected to it to communicate with each other...
Does anyone know the HITACHI AH4021?
The simplest way is to schematically outline my issue, I'm having a hard time explaining:
http://ge.wattelier.club.fr/reseau.JPG
Thanks a lot
See you soon
PS: I'm wondering if the router isn't malfunctioning, as 192.168.1.3 cannot access the internet via port 3728 despite my NAT rule defined as follows:
3728 - 3728 - TCP - 3728 - 3728 from: 192.168.1.3
While the same NAT rule works for 192.168.1.2:
3728 - 3728 - TCP - 3728 - 3728 from: 192.168.1.2
Strange, right?
PFFF,
there's no reason for a router to block local traffic, or else it's not a router. Your Wi-Fi router is actually a router + a built-in access point.
An access point is equivalent to a hub.
If something is blocking traffic between the 2 PCs, in my opinion, it's the PCs themselves.
As for port forwarding (what you call the NAT rule).
You should know that an internet port can only be forwarded to one single machine (private IP rather), not 2, not 3, just one.
If it works on one machine and not the other: the same applies: look at the firewall of the PC in question.
--
and ... There you go!
there's no reason for a router to block local traffic, or else it's not a router. Your Wi-Fi router is actually a router + a built-in access point.
An access point is equivalent to a hub.
If something is blocking traffic between the 2 PCs, in my opinion, it's the PCs themselves.
As for port forwarding (what you call the NAT rule).
You should know that an internet port can only be forwarded to one single machine (private IP rather), not 2, not 3, just one.
If it works on one machine and not the other: the same applies: look at the firewall of the PC in question.
--
and ... There you go!
Thank you very much for your response.
The ping problem is within the same command.
Typical example:
--ping 192.168.1.2--
response = ok
timeout exceeded
response = ok
response = ok
--end of ping--
If I'm not mistaken, Netbios is basically used to associate a name with an IP address. Since my addresses are fixed, do I really need to use it?
If it's not necessary, I will only open 135 and 445.
Otherwise, is port 23 open for direct access to the modem's configuration from the internet? I thought that port 23 open was just to allow traffic on this port towards the machines on the network, in case telnet is running on a machine...
Thank you very much!
@+
The ping problem is within the same command.
Typical example:
--ping 192.168.1.2--
response = ok
timeout exceeded
response = ok
response = ok
--end of ping--
If I'm not mistaken, Netbios is basically used to associate a name with an IP address. Since my addresses are fixed, do I really need to use it?
If it's not necessary, I will only open 135 and 445.
Otherwise, is port 23 open for direct access to the modem's configuration from the internet? I thought that port 23 open was just to allow traffic on this port towards the machines on the network, in case telnet is running on a machine...
Thank you very much!
@+
no no, the 23 is only for the router administration (normally) there is no reason for it to be forwarded by default to the local network.
for pings, you can do extended pings to better analyze the problem (25% loss on 32-byte pings is a lot: poor transmission quality)
already, you can ping the router instead of the other PC, to see which of the 2 PCs is causing the most problems possibly.
to diagnose, you can modify:
the size, option -l, up to 1472
the number option -n
permanent: option -t stop with ctrl+c
on a correct transmission with 1000-byte pings, we shouldn't lose more than 2%.
--
and ... There you go!
for pings, you can do extended pings to better analyze the problem (25% loss on 32-byte pings is a lot: poor transmission quality)
already, you can ping the router instead of the other PC, to see which of the 2 PCs is causing the most problems possibly.
to diagnose, you can modify:
the size, option -l, up to 1472
the number option -n
permanent: option -t stop with ctrl+c
on a correct transmission with 1000-byte pings, we shouldn't lose more than 2%.
--
and ... There you go!
Hello everyone, I also had a firewall issue, I had the same problem
go to your control panel. In your firewall, go to the advanced tab, then the ICMP tab, check the options you want, then click OK. But be sure there are no checked boxes in the "do not allow exceptions" section of your firewall. Try pinging your own machine to see. Try it and let me know if it works or not
Have a good day
Caro
go to your control panel. In your firewall, go to the advanced tab, then the ICMP tab, check the options you want, then click OK. But be sure there are no checked boxes in the "do not allow exceptions" section of your firewall. Try pinging your own machine to see. Try it and let me know if it works or not
Have a good day
Caro
Hello,
Thank you for your responses.
The addresses are 192.168.1.2 and 1.3
Mask 255.255.255.0
Differently named in the same workgroup.
How can I transfer files between these machines?
The problem persists even with firewalls disabled...
Is there a configuration to be done at the router level?
Thank you!
Thank you for your responses.
The addresses are 192.168.1.2 and 1.3
Mask 255.255.255.0
Differently named in the same workgroup.
How can I transfer files between these machines?
The problem persists even with firewalls disabled...
Is there a configuration to be done at the router level?
Thank you!
--
and ... There you go!