Windows IP 169.254.22.110 Mask 255.255.0.0 cannot direct connect to Windows IP: 169.254.27.10 mask 255.255.0.0 ?!?!?!?!?!

[s***@hotmail.com]

I find this highly annoying design of IANA and Microsoft Windows.

Laptop is connect to PC with ethernet cable.

Laptop IP: 169.254.22.110
Laptop Mask: 255.255.0.0

PC IP: 169.27.10
PC Mask: 255.255.0.0

Both seem to be on the same subnet ? as far as I can tell.

But they still cannot ping each other and cannot communicate with each other.

I FIND THIS HIGHLY FOKKING ANNOYING USELESS DESIGN !!!!!!

Why the fuck most If assign 192.168.x.x and mask 255.255.255.0 ?! and both computers... this interferes with automatic DHCP and Internet connection sharing.

TOTALLY SICK OF THIS RETARDED CONFIGURATION CRAP.

Can we pls get some ETHERNET COMMUNICATION SOFTWARE so we can do away with THIS FUCKING USELESS IP CRAP.

OPEN UP ETHERNET MICROSOFT.

I AM SICK OF IANA
I AM SICK OF IANA
I AM SICK OF IANA
I AM SICK OF IANA
I AM SICK OF IANA
I AM SICK OF IANA

MAKE IT WORK OUT OF THE BOX DEFAULT NO MATTER WHAT.

ETHERNET COMMUNICATION IS NOT THAT HARD. IANA/IP MAKES IT TOO HARD.

Make it best effort and not useless CRAP like 169.254.X.X

Bye,
Skybuck.

[s***@hotmail.com]

Just to be clear.

I reconfigured both to use:

Laptop 169.254.0.1
Mask 255.255.0.0

PC 169.254.0.2
Mask 255.255.0.0

Still can't ping.

I suspect some fucking retard designated these ips and mask as "unusable"

GREAT.

NOT.

I saw something about this on pascalcoin issue list:

Bogus ip ranges:

REALLY such a thing exists ?! HOW USELESS LOL:


For security reasons the node server list should be filtered out of these IP ranges. (perhaps at the TNetData.NetData.AddServer level)
List of Bogon ip blocks:

0.0.0.0/8 "This" network
10.0.0.0/8 Private-use networks
100.64.0.0/10 Carrier-grade NAT
127.0.0.0/8 Loopback
127.0.53.53 Name collision occurrence
169.254.0.0/16 Link local
172.16.0.0/12 Private-use networks
192.0.0.0/24 IETF protocol assignments
192.0.2.0/24 TEST-NET-1
192.168.0.0/16 Private-use networks
198.18.0.0/15 Network interconnect device benchmark testing
198.51.100.0/24 TEST-NET-2
203.0.113.0/24 TEST-NET-3
224.0.0.0/4 Multicast
240.0.0.0/4 Reserved for future use
255.255.255.255/32 Limited broadcast

LINK LOCAL ?!

BUT CANT USE IT LOCAL ?!?!?!?!?!?!?!?

WTF....

Cause it's for loopback only or something....

Why windows use this crap... to prevent interference with local networks ?!?!?! REALLY ???!?!?!?!?

CAN YOU RETARDS OF IANA PLS ADD A DIRECT CONNECTION IP RANGE WITH OS-ES like Windows are to FALL BACK ON for easy COMPUTER 2 COMPUTER CONNECTIONS.

Then we can use this as DEFAULT.

Instead of USELESS BOGUS CRAP.


STOP THE ANNOYING FUCKING USELESS BOGUS CRAP ALREADY !!!!

Bye,
Skybuck.

[s***@hotmail.com]

MORE FUCKING MICROSOFT FAIL.

Laptop: 192.168.0.2
Mask: 255.255.255.0

PC: 192.168.0.1
Mask: 255.255.255.0

PING STILL NOT WORKING.

Fucking software/hardware fail.

Must I really reset/restart these PCs for something as simple as this ?!

Fokking annoying.

[s***@hotmail.com]

After disabling/enabling both adapters.

PC can reach Laptop ping 192.16.8.0.2

Laptop cannot reach PC.

HP LAPTOPS ARE TOTALL CRAP.... Got a free one from my Brother.

Believe.. it's the biggest PIECE OF JUNK I have ever seen.

Can't even describe it to you...

It's full with all kinds of crap-ware.... BIOS-wise and software wise...

It has easy WIFI for probably getting into it.

It's battery is total shit.

It has weird blinking lights when it goes off.

And worst of all it's german... keyboard wise and software wise.

Every time I use it I literally want to throw it from the 5th floor out of the window ! =D

LOL.

Got it working once though... now I am again spending my time trying to solve THIS TOTAL IP CRAP.

[s***@hotmail.com]

I CAME VERY CLOSE TO DESTROYING THE LAPTOP... I SHOULD CAUSE IT S CRAP.

But I decided to give it the benefit of the doubt. It could be my PC at fault.

HOWEVER I HAVE NOW SUPER HARD EVIDENCE.

THAT USING LOCAL AREA NETWORKS + INTERNET TECH + WINDOWS IS BUGGED BY DESIGN !!!!!

I already knew this, but let this posting be the final nail in the coffin for Microsoft Windows believability.


I AM NOW 100% CONVINCED THAT MICROSOFT AND/OR NETWORK DRIVER MANUFACTURERS have DELIBRATEDLY implemented BUGS TO MAKE IP/LAN FAIL so you must buy expensive ROUTER CRAP !!!

Gonna post this on some other groups as well.

Bye,
Skybuck.