What's new

Expanding a network with limited access

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Zero1

Occasional Visitor
Hi guys.

In the not so distant future, I will be given the task of slightly expanding an existing network where I work. It consists of a Unix 7 server and 4 thin clients that are basically little boxes running telnet. We also have a Windows XP system that we use for other office work/emails etc. It is also connected to the Unix 7 server and has some terminal emulation software so it can access the system and it's information just like one of the thin clients, perform screen dumps or print invoices from one of the thin clients to the Windows XP's printer.

Currently the printer and router are connected to the Windows XP machine via USB, which means that the Unix 7 server does not have an internet connection, and the Windows XP machine has to be switched on for print outs. My goal is to connect the router via ethernet, which should then give the server an internet connection, plus printing can bypass the Windows PC since the printer will be connected to the network also.

Unfortunately my knowledge of Unix is very limited, however I can get support or remote desktop help should I need it (from our system vendor, very nice people too). What I am hoping someone can help me with, is what addresses would I need to put in place for my plan to come together. I have a rough idea since I have set up my own network, but with having limited knowledge about Unix, I am not able to be as flexible, or reconfigure things as I'd like.

Here is what the network currently looks like. As you can see, it's nice and simple :)
http://img193.imageshack.us/img193/4690/net1.png

Here is what I hope to have at the end of it.
http://img51.imageshack.us/img51/8862/net2.png

I don't think it should cause too much headache. I've decided to keep the IP address of the Windows XP machine the same, just for my sanity (not having to reconfigure anything in Unix). My only point of confusion is what settings/static route would I set in the router? My guess so far is this:

2Wire911 ADSL Modem/Router:
Local IP address: 128.0.0.150
Subnet mask: 255.255.0.0 (This is the same as the thin clients and XP machine)
DHCP: Disabled

Brother MFC7440 Printer
Local IP address: 128.0.0.175
Subnet mask: 255.255.0.0
DHCP: Disabled

Once these devices are configured, I'm guessing I'll have to add these static routes in Unix, or get support to do this for me. Out of interest, if I was to set this up in Unix, what static routes would I set for those two devices?

So, should this work? My goal is for the Windows XP and Unix 7 machine to have internet access, and also shared use of the Brother printer, while not changing any other aspects of the network. This might also mean that we can connect both of our networks at other locations if we decide too (I guess that's another thread, another time though, but hopefully, once this is in place, the vendor can sort it out). If I have missed any vital settings, or if you have any better suggestions, please let me know.

Also, if I wanted to avoid configuring Unix altogether, could I just set the router to have the IP address that the Windows XP machine currently has, but have the router forward information to a new IP address for the Windows XP machine, so I am configuring in the router rather than Unix? It's maybe a sloppy workaround, but just a thought.

Thanks a lot. Let's hope it works this time! (I gave up last time :p)
 
Last edited:
Why not just connect everything to the LAN side of the router and set its LAN IP to 128.0.0.1?
 
Thanks. I am pretty limited with component location. It's a very cramped office and things such as where the telephone line is dictates where I can place the router. Currently the Unix server is in a different office. As it happens, I gave it a test run earlier today and it works how I intended. The only problem was internet connectivity, but I suspect that was because when the network was originally set up, it wasn't done so with a private IP range. I'll speak to the vendor tomorrow, but it should be something I could even do with my limited Unix knowledge. I've been using Suse recently and it's not as obscure as I thought it could be.
 

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top