Cannot ping in workgroup - help please

[Guest]

Hello, everyone! I have two PCs in my home workgroup: "A", with XPPro and
static IP address 192.168.0.1, submask 255.255.255.0; and "B", with XPHome
and IP address 192.168.0.5. Both have XP SP2 applied. They are connected
with a 4-port minihub. A month ago a virus hit my system so I had to
reinstall XP in both computers with their respective system recovery CDs, but
although everything seems to be normal, they cannot ping each other and
therefore cannot share the Internet connection as they used to do before.
However, if I start both computers in safe mode, they can ping each other
either with the IP address or with the local host name. As soon as I start
Windows in normal mode, “A†can see “B†but not the other way around. “Aâ€
used to be the ICS host, but as “B†cannot see “Aâ€, it cannot be shared.

I have tried everything: I have uninstalled SP2, I have used a crossover
cable to skip the hub, I have deactivated the firewall from SP2 but the
problem remains consistent. Nothing changes. In order to be able to share
folders and printers, I installed IPX/SPX and NetBIOS and they can see each
other with these protocols, but as far as the TPC/IP network is concerned,
nothing seems to work.

I have also review almost every conversation thread in the XP Networking
forum, but nothing seems to work.

Any clues? I cannot seem to bring these computers to work as they used to.
Thanks in advance.
Alex.

 

[Chuck]

Hello, everyone! I have two PCs in my home workgroup: "A", with XPPro and
static IP address 192.168.0.1, submask 255.255.255.0; and "B", with XPHome
and IP address 192.168.0.5. Both have XP SP2 applied. They are connected
with a 4-port minihub. A month ago a virus hit my system so I had to
reinstall XP in both computers with their respective system recovery CDs, but
although everything seems to be normal, they cannot ping each other and
therefore cannot share the Internet connection as they used to do before.
However, if I start both computers in safe mode, they can ping each other
either with the IP address or with the local host name. As soon as I start
Windows in normal mode, “A” can see “B” but not the other way around. “A”
used to be the ICS host, but as “B” cannot see “A”, it cannot be shared.

I have tried everything: I have uninstalled SP2, I have used a crossover
cable to skip the hub, I have deactivated the firewall from SP2 but the
problem remains consistent. Nothing changes. In order to be able to share
folders and printers, I installed IPX/SPX and NetBIOS and they can see each
other with these protocols, but as far as the TPC/IP network is concerned,
nothing seems to work.

I have also review almost every conversation thread in the XP Networking
forum, but nothing seems to work.

Any clues? I cannot seem to bring these computers to work as they used to.
Thanks in advance.
Alex.

Alex,

Please start with ipconfig information for each computer.
Start - Run - "cmd". Type "ipconfig /all >c:\ipconfig.txt" into the command
window - Open c:\ipconfig.txt in Notepad, copy and paste into your next post.

From each computer, test connectivity and name resolution:
1) Ping itself by name.
2) Ping itself by ip address.
3) Ping the other by name.
4) Ping the other by ip address.
5) Ping 127.0.0.1.
Report success / exact error displayed in each test (10 tests total).

As you've discovered, installing IPX/SPX and NetBEUI, though a workaround for
file sharing, will do nothing to make TCP/IP and your internet access work. And
if using a hub, using one of the alternative protocols for file sharing will
protect that from internet exposure, but your TCP/IP security problems will
continue.

Remember, the Windows platform as a whole is standardised upon TCP/IP, and
NetBIOS Over TCP/IP. Adding IPX/SPX and / or NetBEUI only complicates things.

If you can't use a NAT router (why not?) then please immediately enable a
firewall on both computers. Or at least as soon as you get TCP/IP working.

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.

 

[Steve Winograd [MVP]]

Hello, everyone! I have two PCs in my home workgroup: "A", with XPPro and
static IP address 192.168.0.1, submask 255.255.255.0; and "B", with XPHome
and IP address 192.168.0.5. Both have XP SP2 applied. They are connected
with a 4-port minihub. A month ago a virus hit my system so I had to
reinstall XP in both computers with their respective system recovery CDs, but
although everything seems to be normal, they cannot ping each other and
therefore cannot share the Internet connection as they used to do before.
However, if I start both computers in safe mode, they can ping each other
either with the IP address or with the local host name. As soon as I start
Windows in normal mode, “A” can see “B” but not the other way around. “A”
used to be the ICS host, but as “B” cannot see “A”, it cannot be shared.

I have tried everything: I have uninstalled SP2, I have used a crossover
cable to skip the hub, I have deactivated the firewall from SP2 but the
problem remains consistent. Nothing changes. In order to be able to share
folders and printers, I installed IPX/SPX and NetBIOS and they can see each
other with these protocols, but as far as the TPC/IP network is concerned,
nothing seems to work.

I have also review almost every conversation thread in the XP Networking
forum, but nothing seems to work.

Any clues? I cannot seem to bring these computers to work as they used to.
Thanks in advance.
Alex.

Everything that you describe would be consistent with a firewall
program (that runs in normal mode, but not in Safe mode) blocking
access. Could there be one? Some antivirus programs (e.g. Norton,
McAfee, Trend Micro, eTrust) have related firewall components.

Can each computer ping itself in normal mode?

Are there any relevant messages in Event Viewer? To run it, click
Start | Control Panel | Performance and Maintenance | Administrative
Tools | Event Viewer. For more information, see:

HOW TO: View and Manage Event Logs in Event Viewer in Windows XP
http://support.microsoft.com/?id=308427

Are there any programs in the Startup folder that could interfere with
TCP/IP in normal mode?
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com

 

[Guest]

Hi, Chuck. Thanks for your quick response. I am aware that IPX/SPX is just
a workaround and I have only installed it to get the file and printer sharing
up and running. Once TPC/IP is configured correctly, I will remove these
protocols.

Here's the result for each one of the tests. Funny thing is, if I start
both computers in safe mode, all the test succeed.

---------------------------------------------------------------
“A†computer (XPPro, ICS host, IP address = 192.168.0.1)
---------------------------------------------------------------

Ping itself by name – ok
Ping itself by IP address – ok
Ping other by name – failed
Ping other by IP address – ok
Ping 127.0.0.1 – ok

Results of ipconfig /all (some info is in Spanish, as my XP is in that
language. Mexican aboard, man):

Configuración IP de Windows Nombre del host . . . . . . . . . :
hp4100 Sufijo DNS principal . . . . . . : Tipo de nodo . .
.. . . . . . . . : desconocido Enrutamiento IP habilitado. . . . : Sí
Proxy WINS habilitado. . . . . : No
Adaptador Ethernet HomeNET : Sufijo de conexión específica
DNS : Descripción. . . . . . . . . . . : Broadcom NetXtreme Gigabit
Ethernet for hp Dirección física. . . . . . . . . : 00-30-6E-B4-F5-5D
DHCP habilitado. . . . . . . . . : No Dirección IP. . . . .
.. . . . . . : 192.168.0.1 Máscara de subred . . . . . . . . :
255.255.255.0 Dirección IP. . . . . . . . . . . :
2002:c980:eba7:4:f46d:c010:abda:a913 Dirección IP. . . . . . . . . .
.. : 2002:c980:eba7:4:230:6eff:feb4:f55d Dirección IP. . . . . . . . .
.. . : fec0::4:230:6eff:feb4:f55d%2 Dirección IP. . . . . . . . . . .
: fe80::230:6eff:feb4:f55d%4 Puerta de enlace predeterminada :
Servidores DNS . . . . . . . . . .: fec0:0:0:ffff::1%2
fec0:0:0:ffff::2%2
fec0:0:0:ffff::3%2 Adaptador Ethernet VPNremote Virtual Adapter
: Estado de los medios. . . .: medios desconectados
Descripción. . . . . . . . . . . : Avaya VPNet Virtual Adapter
Dirección física. . . . . . . . . : 00-60-A1-00-00-00 Adaptador PPP Prodigy
: Sufijo de conexión específica DNS :
Descripción. . . . . . . . . . . : WAN (PPP/SLIP) Interface
Dirección física. . . . . . . . . : 00-53-45-00-00-00 DHCP
habilitado. . . . . . . . . : No Dirección IP. . . . . . . . . . . :
201.128.235.167 Máscara de subred . . . . . . . . : 255.255.255.255
Puerta de enlace predeterminada : 201.128.235.167 Servidores
DNS . . . . . . . . . .: 200.23.242.196
200.23.242.202 NetBios sobre TCPIP. . . . . . . :
Deshabilitado
Adaptador de túnel Teredo Tunneling Pseudo-Interface :
Sufijo de conexión específica DNS : Descripción. . . . . . . . . . .
: Teredo Tunneling Pseudo-Interface Dirección física. . . . . . . .
.. : 00-00-FB-E8-36-7F-14-58 DHCP habilitado. . . . . . . . . : No
Dirección IP. . . . . . . . . . . : fe80::5445:5245:444f%6
Puerta de enlace predeterminada : NetBios sobre TCPIP. . . . . . .
: Deshabilitado
Adaptador de túnel 6to4 Tunneling Pseudo-Interface : Sufijo
de conexión específica DNS : Descripción. . . . . . . . . . . :
6to4 Tunneling Pseudo-Interface Dirección física. . . . . . . . . :
C9-80-EB-A7 DHCP habilitado. . . . . . . . . : No Dirección
IP. . . . . . . . . . . : 2002:c980:eba7::c980:eba7 Puerta de enlace
predeterminada : 2002:836b:213c:1:e0:8f08:f020:8
2001:1b10::c058:6301 Servidores DNS . . . . . . . .
.. .: fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1 NetBios sobre TCPIP. . . . . . . : Deshabilitado
Adaptador de túnel Automatic Tunneling Pseudo-Interface :
Sufijo de conexión específica DNS : Descripción. . . . . . . . . . .
: Automatic Tunneling Pseudo-Interface Dirección física. . . . . . .
.. . : C9-80-EB-A7 DHCP habilitado. . . . . . . . . : No
Dirección IP. . . . . . . . . . . : fe80::5efe:201.128.235.167%2
Puerta de enlace predeterminada : Servidores DNS . . . . . . . . .
..: fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1 NetBios sobre TCPIP. . . . . . . : Deshabilitado
Adaptador de túnel Automatic Tunneling Pseudo-Interface :
Sufijo de conexión específica DNS : Descripción. . . . . . . . . . .
: Automatic Tunneling Pseudo-Interface Dirección física. . . . . . .
.. . : C0-A8-00-01 DHCP habilitado. . . . . . . . . : No
Dirección IP. . . . . . . . . . . : fe80::5efe:192.168.0.1%2 Puerta
de enlace predeterminada : Servidores DNS . . . . . . . . . .:
fec0:0:0:ffff::1%2
fec0:0:0:ffff::2%2
fec0:0:0:ffff::3%2 NetBios sobre TCPIP. . . . . . . : Deshabilitado
---------------------------------------------------------------
“B†– computer (XPHome IP address = 192.168.0.5)
---------------------------------------------------------------
Ping itself by name – ok
Ping itself by IP address – ok
Ping other by name – failed
Ping other by IP address – failed
Ping 127.0.0.1 – ok

Configuración IP de Windows Nombre del host . . . . . . . . . :
SonyVAIO Sufijo DNS principal . . . . . . : Tipo de nodo. .
.. . . . . . . . . : híbrido Enrutamiento habilitado. . . . . .: No
Proxy WINS habilitado. . . . . : No
Adaptador Ethernet Conexión de área local : Sufijo de
conexión específica DNS : Descripción. . . . . . . . . . . :
Intel(R) PRO/100 VE Network Connection Dirección física. . . . . . .
.. . : 08-00-46-63-C5-B3 DHCP habilitado. . . . . . . . . : No
Dirección IP. . . . . . . . . . . : 192.168.0.5 Máscara de subred .
.. . . . . . . : 255.255.255.0 Dirección IP. . . . . . . . . . . :
2002:c980:eba7:4:6897:2a14:997:ab61 Dirección IP. . . . . . . . . . .
: 2002:c980:eba7:4:a00:46ff:fe63:c5b3 Dirección IP. . . . . . . . . .
.. : fec0::4:a00:46ff:fe63:c5b3%1 Dirección IP. . . . . . . . . . . :
fe80::a00:46ff:fe63:c5b3%4 Puerta de enlace predeterminada :
fe80::230:6eff:feb4:f55d%4 Servidores DNS . . . . . . . . . .:
fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
Adaptador de túnel Teredo Tunneling Pseudo-Interface :
Sufijo de conexión específica DNS : Descripción. . . . . . . . . . .
: Teredo Tunneling Pseudo-Interface Dirección física. . . . . . . .
.. : FF-FF-FF-FF-FF-FF-FF-FF DHCP habilitado. . . . . . . . . : No
Dirección IP. . . . . . . . . . . : fe80::5445:5245:444f%5
Puerta de enlace predeterminada : NetBios sobre TCPIP. . . . . . .
: Deshabilitado
Adaptador de túnel Automatic Tunneling Pseudo-Interface :
Sufijo de conexión específica DNS : Descripción. . . . . . . . . . .
: Automatic Tunneling Pseudo-Interface Dirección física. . . . . . .
.. . : C0-A8-00-05 DHCP habilitado. . . . . . . . . : No
Dirección IP. . . . . . . . . . . : fe80::5efe:192.168.0.5%2 Puerta
de enlace predeterminada : Servidores DNS . . . . . . . . . .:
fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1 NetBios sobre TCPIP. . . . . . . : Deshabilitado

 

[Chuck]

Hi, Chuck. Thanks for your quick response. I am aware that IPX/SPX is just
a workaround and I have only installed it to get the file and printer sharing
up and running. Once TPC/IP is configured correctly, I will remove these
protocols.

Here's the result for each one of the tests. Funny thing is, if I start
both computers in safe mode, all the test succeed.

<SNIP>

Alex,

OK, reviewing and summarising your ping tests - HP4100 can ping SonyVAIO by ip
address, so you do have connectivity. SonyVAIO cannot ping HP4100 by ip
address.

You say that with both computers in Safe Mode, all pings are successful.
Between that, and the fact that the ping results in normal mode are asymmetrical
(HP4100 can ping SonyVAIO but not vice versa), I'll bet that you have a firewall
on HP4100 that's misconfigured.

If that's not it, look at the list of running tasks, using Task Manager.
Compare the list of tasks from normal and safe modes. Something in the
difference will be your problem.

If you find it painful using Task Manager, get PSList (free) from
<http://www.sysinternals.com/ntw2k/freeware/pslist.shtml>. You can run PSList
as "pslist >c:\pslist.txt", then open and print c:\pslist.txt using Notepad.
Compare the two listings from normal and safe modes.

FWIW, yo no hablo Espanol (Gringo on board), but I can see a few entries
"NetBios sobre TCPIP. . . . . . . Deshabilitado ". Make sure that NetBIOS Over
TCP/IP (Local Area Connection - Properties - TCP/IP - Properties - Advanced -
WINS) is enabled on each computer.

Once we get the ping and NBT working on both computers, then we can work on file
sharing permissions.

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.

 

[Guest]

Bingo! You’re totally correct. I installed an antivirus from TrendMicro and
I did not notice that there was in fact a firewall running, besides Window’s.
I disabled it and both computers can see each other normally via TCP/IP.

Now, I cannot seem to make my ICS to work, but that’s an entirely different
subject, and I will post a new discussion thread for it.

Thank you kindly for your time and your advice.
Best of luck.
Alex.

 

[Guest]

As I mentioned in the above thread with Chuck, you guys are totally right:
There was a third party firewall preventing the TCP/IP flow between both
computers. I disabled it and now they can see each other normally.

Thank you so much for your time and your advice. It was really helpful.
It’s amazing how these little details can stop us in our tracks, when all it
takes is to remove a small checkmark for a certain option.

Best of luck,
Alex.

 

[Chuck]

Bingo! You’re totally correct. I installed an antivirus from TrendMicro and
I did not notice that there was in fact a firewall running, besides Window’s.
I disabled it and both computers can see each other normally via TCP/IP.

Now, I cannot seem to make my ICS to work, but that’s an entirely different
subject, and I will post a new discussion thread for it.

Thank you kindly for your time and your advice.
Best of luck.
Alex.

Kewl, Alex. Thanks for the feedback.

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.

 

[Steve Winograd [MVP]]

As I mentioned in the above thread with Chuck, you guys are totally right:
There was a third party firewall preventing the TCP/IP flow between both
computers. I disabled it and now they can see each other normally.

Thank you so much for your time and your advice. It was really helpful.
It’s amazing how these little details can stop us in our tracks, when all it
takes is to remove a small checkmark for a certain option.

Best of luck,
Alex.

You're welcome, Alex. I'm glad that my suggestion helped you solve
the problem.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com