I need some creative suggestions for solving a network problem and wonder if their is a linux or free dos solution.

I have a friend who works in a shared office space with an NT2000 network, IP addresseses assigned through DHCP Server service, and the internet connection shared through Microsoft Proxy Server. She can share this service for free but can't make any demands on the Network Administrator who is basically a DB guy who has no Network Administration skills (i.e. I had to show him how to configure a Win98 client on his own network). The administrator just set up the service sufficiently so that my friends two Win98 computers can cruise the internet and ping each other. They can't share files or printers because they have been assigned a different work group name and the Network Administrator, unfortunately, doesn't know how to configure a domain with two work groups.

Are their any network alternatives I could install on these two machines that would allow these two win98 boxes to share files and printers but still use the internet connection provided by the NT2000 network

BTW, a 30 foot rj45 crossover cable is not an option (i already suggested it and was shot down for asthetic purposes).

Is there some reason why the two machines must have different workgroup names?

First, setting the two machines to the same workgroup name is vital to being able to share information - this is a rule of Windows Workgroup networking that can only be overridden by a Windows NT server. Samba is not very good at linking multiple workgroups (although in theory it can - I have not had any luck with it).

Once the workgroup names are the same, if the machines still have problems finding eachother, load the IPX/SPX protocol on both. Then bind NetBIOS to IPX. Since addresses used by IPX do not change, the two machines should always be able to find eachother on the network.

Good luck,
Gary Allen Vollink

the administrator has set up the different workgroup name so that my friend can't browse files, etc on his network. He does not know how to set up my friend on a distinct workgroup within his domain so that she can share files, etc. but only within her workgroup. Otherwise, this would be a simple problem of setting up the workgroup in the domain, assigning my friend administrator rights in her workgroup, and then let me set up the shared services.

My friend's "work group" consists of two windows 98 boxes that used to be connected by an RJ45 crossover in her home office and shared files, printers, and connections in a peer network. She has moved into a new office with an NT2000 network.

I'm trying to come up with a work around that would allow these two boxes to talk with each other outside of the windows domain services. For example, I am looking at setting up a dos network connection that these two could share. I'm trying to see if anyone has some suggestions from a linux point of view. Right now they connect to the network only to use the proxy services for browsing the web. In addition, they can ping each other.

Everyone will hate me for saying this BUT.

Windows 98 is not so insurmountably in-secure that it MUST sit "behind" a firewall/proxy. It does fine for 80% of the world on dial-up. If they are both set up in the "DMZ" (outside the firewall - between the firewall and the router) then they can connect directly to the gateway. I have users from my company in (satallite offices) shared office spaces - and this is how those users are set up.

However, if the person at the remote office is able to change the workgroup of one machine to something, then he can change the workgroup of BOTH machines to the same thing. By creating a different workgroup OUTSIDE of his "domain" - then simply setting both to the same workgroup will be sufficient in every case.

The person at the far end is probably just making this too complex. Even with the proxy support - you would log in the same [\\domain\user] (since you are forign to the domain anyway).

thanks. i'll give it a try. the office is closed for the next two weeks so i won't be able to report back before then (oh, what a joy it would be to have remote administration priv's!)