Wine Networking Problem

Originally Posted by business_kid Ok. Tried an rsync -avc but that failed.

When I set up a local alien mirror, I had a hard time finding a functional mirror that was up to date and also supported rsync.

I had to use rsync://rsync.slackware.uk/people/alien/multilib/current/ and still use it.

BK

/Some time later.

I had the empty-looking ~/.wine64 prefix. So, as this wine-9.8 is 64+32 built wine, I tested it. I installed my library thing from scratch with

WINEPREFIX=~/.wine64 wine64 /path/to/library_setup.exe

and it installed pretty painlessly. So the one ~/.wine directory apparently will do. Anyhow I updated it from disc, which applies downloaded updates and is the speediest way by a lot.

Then, with my new wine64 directory and my new wine-9.8 package and my new install of the Library archive, I asked it to check for further updates. It threw the same error as in post #13

I also ran the 32 & 64 bit 'wine(64) cmd' and got two terminals one in 32bit speak using ~/.wine, and one in 64bit using ~/.wine64. I ran 'ipconfig' in both, and they gave me sensible working parameters assuring me everything's going to the right places.

I guess I'll have to go manually updating for the moment...

At this point, assuming other wine programs work with networking and linux native things are fine, I might raise a bug report with the WINE people.

Originally Posted by garpu At this point, assuming other wine programs work with networking and linux native things are fine, I might raise a bug report with the WINE people.

It is not a wine bug. Alien's wine-8.6 works just fine in my elderly laptop. I had, and reinstalled the exact same package here on this box, and it didn't work. The only difference is a later version of current here, and a more recent Multilib. But there's a distinct lack of networking issues with ~current, and all vital signs are good. Why would I be the only one to have this? Everything I try, I'm getting this sort of thing

Z:\home\dec>c:

c:\>ping www.jw.org
preloader: Warning: failed to reserve range 0000000000010000-0000000000110000
Pinging www.jw.org [23.57.162.22] with 32 bytes of data:
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.

Ping statistics for 23.57.162.22
        Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)

whereas the one that networks correctly gives me

preloader: Warning: failed to reserve range 00010000-00110000
Pinging www.jw.org [2.18.238.139] with 32 bytes of data:
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.

Ping statistics for 2.18.238.139
        Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)

You see that in each case wine accesses the net to resolve dns, then claims it's not connected. Wine won't ping localhost. Networking is a cosmetic mess, but it functions by throwing requests to the linux OS. Except this one request from a closed source program doesn't work on one installation.

Can I bring debug tools to bear on that? I have a menu option mouse-click that triggers the error on one box, but not the other.

BTW, I'll spare you the shaggy dog story, but the different urls in the pings for the same site are ok.