While there isn't enough info here to make a definitive answer, the process is fairly straightforward. I just did something similar two weeks ago at work. First off, the new LAN should use the same IP subnet as the existing LAN for simplicity's sake. If that's not possible, you'll need a router between LANs to make the connection. You can do this statically, or configure whatever device is handing out addresses to use a block of addresses within the existing subnet. If the Win2K LAN is using DHCP to assign addresses, you'll want to reserve this block to prevent it from being dynamically assigned to other hosts. The wireless routers I've seen handle address assignments for their wireless clients - you may have to change that, as two DHCP servers can't exist on the same subnet. With such a small network I'd start out with static addressing for all hosts, then experiment with changing them to dynamic assignment after all the basics work.
Connecting one of the wireless router LAN ports to the hub on the existing LAN will require a cable between them, and you may need to configure the wireless box to forward packets across that interface.
When I connected two networks together I ran into a problem that I should have expected, but overlooked. Whoever set these systems up cleverly named the server in each group SERVER. The moment I connected them, everything failed - panic time. Each host name must be unique before you make the connection, and changing names can be tedious. If any devices or services are accessed using UNC names instead of addresses, you'll have to reconfigure them after the change; in my case that meant a lot of time in the Registry of the the servers manually changing addresses. Hopefully you won't run into that.
If you want to give the new network hosts access to the Internet via your Linux firewall/router, set the default gateway addresses of the new hosts to the local (LAN-side) address of the Linux box.