Windows Messenger File Send Problem Solved


Recommended Posts

It worked for me, but i dont know if it will work for you, this , a text file was sent to me from a ISP Host

Okay, before you read on and try the solution you should determine if this

solution may apply to you.

Also, this solution requires you to do some registry hacking.

This solution might help you if you are:

* using Windows XP (although Windows 2000 users might try it as well)

* not using NAT (meaning not using: ICS, WinRoute, etc or a hardware router)

* able to recieve files and messenge normally, but unable to send files

* using at least one network card in your system.

If all of these apply (and even if not, you might wanna try the solution)

you should try the following:

Send a file to a friend and when the messenger is "connecting" execute:

'netstat -an | find "6891"' in a DOS-box.

Look at the IP-addresses, one should be the IP-address of the friend you are

sending to and the other should be yours.

If your IP-address is not your PP(T)P(OE)-address, but that from one of your

network cards (which are not connected to the internet), this solution is

for you!

Start the Registry Editor (regedit) and go to the key:

HKEY_LOCAL_MACHINESYSTEMControlSet001ServicesTcpipLinkage

There are four entries there: (Default), Bind, Export and Route. (Default)

can be ignored.

The other three entries are lists of strings. In case your wondering what

these strings mean, they are the network interfaces that are available on

your system. These are not limited to only network cards, but could also be

other drivers, like Video-conferencing drivers. Check these lists for the

string "NdisWanIp". In my case, this string was a the bottom of the list in

both Bind and Route. Then copy the string and paste it at the top of the

list, in other words, put it at the top of the list.

Do this as well for

HKEY_LOCAL_MACHINESYSTEMControlSet002ServicesTcpipLinkage and

HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesTcpipLinkage (this

last one should already be changed, since it's a copy of one of the others).

Then exit the Registry Editor and reboot.

On a side note, I also had a problem with ipconfig.exe. It only showed my

PPTP-connection and not my NICs. Removing my NICs from the device manager

and rebooting solved that problem.

--

Jeroen-bart Engelen

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.