开云体育

just to keep you updated on the situation. My issue has been totally resolved with the (great) help of Fish. I have bought a USB-to-RJ45 ethernet adapter. i plugged it in my laptop USB port and after

Hello, Am 06.04.2025 um 19:58 schrieb Patrik Schindler via groups.io <poc@...>: I got a private reply stating that the OS I use predates the availability of the huge 3390-27 and

Hello, I'm trying to learn how to use (virtual) tapes with OS/390 ADCD 2.10 running on Hercules Hyperion Release 4.7. I guess I've discovered a hard bug in ADRDSSU, the utility to dump and restore

Mike Schwab wrote: That is ONE of the problems associated with Hercules's inability to directly support WiFi adapters, yes, but it is certainly not the main problem. The MAIN problem is that wired

The main problem with almost all wifi adapters is they don't work in Promiscuous mode. They limit themselves to one IP and so can't receive packets for more than one

Hello, I'm trying to learn how to use (virtual) tapes with OS/390 ADCD running on Hercules Hyperion Release 4.7. I'd prefer to minimize switching between windows to type commands, even if this is

Fish is 100% correct.? If you don't have a physical adapter, you should get one for inside your PC and not keep trying to force the wifi one to work because it won't be reliable at all.? If you are

I found this program to be interesting. Maybe you already have solved this problem. Just a couple of hints. There are many more experienced MVT Cobol programmers here. This is something I learned from

Thank you Fish. Much appreciated [email protected]> a écrit :

phil34130 wrote: (lots of stuff) First of all, you need to fix your CTCI-WIN (TTTest) problem. As explained to you on the main Hercules forum, CTCI-WIN does not support wireless WiFi adapters It

You know Philippe, on a linux host, and an emulated mainframe, they need to be on different networks. So you have everything on the same network, 192.168.0.0/24. Netmask 255.255.255.0 (witch is

Le 05/04/2025 à 01:11, Dave Trainor - N8ZFM via groups.io a écrit?: > > Well you still needed forwarding on for it to transfer packets from one interface to another.?? So yes I see its now on for

Well you still needed forwarding on for it to transfer packets from one interface to another. So yes I see its now on for you, good, you did need that. There must obviously be something else you

unfortunately it made no difference, even after enabling IP routing... 00:48:19.221 Copyright (C) 2002-2025, Software Development Laboratories 00:48:19.221 00:48:19.221 Using FishLib64-M90a.dll,

thanks Dave I'll give it a try and will let you know

I seriously am telling you guys this line from his post on network information: 23:05:37.029 23:05:37.029 Host Name . . . . . . . . . : TC-MAUGUIO 23:05:37.029 Node Type . . . . . . . . . :

Le 04/04/2025 à 23:40, Mike Schwab via groups.io a écrit?: > What is 192.168.0.0 ? > > On Fri, Apr 4, 2025 at 4:13?PM phil34130 via groups.io <http://groups.io> <phil34130@...>

What is 192.168.0.0 ? [email protected]> wrote:

A quick google search tells me this – but again my friend, I have never tried this on a windows machine. To enable IP forwarding on Windows, modify the registry by setting the IPEnableRouter value

I have no idea how to set this on a Windows machine as the host – but do you have IP Forwarding set to on? In Linux, which I am familiar with this is required, and I would imagine it is for windows