I can ping with IPv6. I can not ping with IPv4.

Hello,

I have a PC (SUN W2100z) with a Broadcom NetXtreme Gigabit
Ethernet adapter. The Gigabit Ethernet adapter is integrated in the
mother board.

I set up a LAN connection and manually specify the IPv4
address, netmask, and default gateway of the Ethernet
adapter (Local Area Connection).

I can not ping to the IPv4 default gateway. I have the following
message:
ping XX.XX.XX.XX
PING: transmit failed, error code 1232.
PING: transmit failed, error code 1232.

I CAN perfectly ping to the IPv6 default gateway.


The only way for me to fix the problem is by disabling and
enabling the "Local Area Connection". After that, IPv4 will
work perfectly until the next reboot. Again, after rebooting I will
have to disabling and enabling the Local Area Connection
to have IPv4 connection.

Do you know how can I fix this problem????

Thank you very much for your answer.

Eric.

Have you checked for Adaptor Driver up dates at theMOBO's or manufacturer's
website?

Also, have you tried disabling the TCP/IPv6 in theProperties of your Network
connection?
It is not necessary to use the v6; v4 is quite enough.
The change to v6 is only to increase the number of world-wide IP addresses
available.

--
Mick Murphy - Qld - Australia


"Eric Gamess" wrote:

> Hello,
>
> I have a PC (SUN W2100z) with a Broadcom NetXtreme Gigabit
> Ethernet adapter. The Gigabit Ethernet adapter is integrated in the
> mother board.
>
> I set up a LAN connection and manually specify the IPv4
> address, netmask, and default gateway of the Ethernet
> adapter (Local Area Connection).
>
> I can not ping to the IPv4 default gateway. I have the following
> message:
> ping XX.XX.XX.XX
> PING: transmit failed, error code 1232.
> PING: transmit failed, error code 1232.
>
> I CAN perfectly ping to the IPv6 default gateway.
>
>
> The only way for me to fix the problem is by disabling and
> enabling the "Local Area Connection". After that, IPv4 will
> work perfectly until the next reboot. Again, after rebooting I will
> have to disabling and enabling the Local Area Connection
> to have IPv4 connection.
>
> Do you know how can I fix this problem????
>
> Thank you very much for your answer.
>
> Eric.
>

Hello,

I finally found the problem.
Thank you Mick.

Here is the problem and the solution.

There is a difference between the Windows XP gratuitous ARP and the
one that Windows Vista sends. On the same computer, I also installed
Windows XP on another partition. Windows XP can get the IPv4 address
perfectly, while Windows Vista can not.

All happened when I restart the computer. Windows XP sends a
Gratuitous ARP request and does not received any response. So Windows
XP
can take the statically assigned IPv4 address.

Windows Vista also sends a Gratuitous ARP request (it is different
from the one that sends Windows XP). For some strange reason, some
devices on the network answer to the Gratuitous ARP request even If
they
do not owned the IPv4 address. So Windows Vista can not use the
statically
assigned address.

The big problem is that Windows Vista does not show any duplicate
address
error message on your screen. The only way to see the problem is by
running
"ipconfig" command and notice that no IPv4 address is assigned to the
Local Area Connection even if it is statically specified and the other
devices
of the network do not have the statically assigned address.

I could fix the problem by disabling Gratuitous ARP on Vista:

1: Go to "regedit"
2: Find HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Tcpip
\Parameters
3: Double-click the ArpRetryCount value, type 0, and then click OK.
If it does not exist create of type REG_DWORD.
4: Reboot the machine
5: IPv4 should work.

I hop this can help.

Eric.