Sign in with
Sign up | Sign in
Your question

Network Gurus, lend me a hand!

Last response: in Components
Share
Anonymous
September 18, 2001 5:44:49 PM

I work in a small office building and our network has been very basic until recently. Here's what we've got now:

Network A:
- Full dedicated T-1 line
- 8 servers all using Windows NT server, one of which has two sites running on it via two NICs
- All systems are connected via standard hubs.


Network B:
- Buisness grade DSL line
- 10 work stations. Some running NT Server, some running NT Workstations, some running Win 98.
- All systems are connected via standard hubs.

The problem before the court is that I want to link these two networks together so that machines on network A can access machines on network B through Network Neighborhood, but they need to continue to use their respective T1 or DSL gateway.

I realise that I should have some switches in there instead of just using all hubs, but bare with me. You know how hard it can be to convince higher ups that they need to spend a few hundred bucks on new equipment.

I took a cross-link ethernet cable (or "patch cable" as some call it) and simply connected two hubs from opposing networks.

After doing that, any of the machines that have both TCP/IP and NetBEUI installed can access the entire network without much trouble. Take NetBEUI away (using TCP/IP only now) and they'll only see computers using the same gateway.

Also, as a final problem, the one computer that is hosting multiple sites using two NICs can't access *anything* through network neighborhood, but all other computers can access it without trouble.

Any suggestions or glaring problems that you guys could point out would be appreciated.
September 19, 2001 12:44:24 PM

1) Write down all your current settings

2) Ask your DSL ISP their DNS server addresses (ie: 201.144.34.1 and 201.144.34.2)

3) Buy a router such as the NetGear 311 or LinkSys BEFSR11 (I've used both, I think the netgear is a bit better)

4) Determine the IP address range, subnet mask, DNS servers, and gateway of the computers in network A . I think under WIN NT you can type "IPCONFIG /ALL" at a command prompt. Print these out if you can. Look for a pattern in the IP addresses (ie: 192.168.1.5, 192.168.1.6, 192.168.1.7, etc...). Some (particularly the server with two NICs) of these NT machines may have multiple IP addresses. If there are two patterns let me know.

5) Set up the router on network B. The ethernet line from your DSL modem goes into the WAN port, your hub goes into the LAN port.

6) On a computer in network B, set the IP address, subnet mask, and DNS servers to server assigned / automatic and clear any assigned gateways. Reboot the computer and access the router setup (NetGear: goto 192.168.0.1 in a browser, LinkSys goto 192.168.1.1, or see router instructions). Change the ROUTERS LAN IP address and subnet mask to something that matches the ones in network A (ie: if the computers in network A used 192.168.1.1 -> 192.168.1.8 and subnet mask 255.255.255.0 then set the router to 192.168.1.50 subnet 255.255.255.0) Also disable the routers internal DHCP server. Save and exit the router setup.

7) On the computer in network B that you are using, change the IP address and subnet mask to something similar to that in network A (ie: 192.168.1.51 subnet 255.255.255.0), the DNS servers to those given out by your DSL ISP (see step 2), and add the IP address of your router (ie: 192.168.1.50) as a gateway.

8) Determine the workgroup name of the computers in Network A (under "Network Identification", ie: MYWORKGROUP). Change the workgroup name of the computer in network B you have been using so that it matches. Reboot the computer.

9) Change the remaining computers in network B so they match the pattern (ie: IP addresses 192.168.1.52 -> 192.168.1.60, subnet mask 255.255.255.0, DNS servers (step 2), gateway 192.168.1.50, and workgroup MYWORKGROUP). Make sure none of these computers are acting as DHCP servers.

10) Connect your patch cable between the hubs. Turn the router off the on. Reboot all the computers in network B. They should all work now.


So in this example:

Computer A1: IP:192.168.1.5 Subnet:255.255.255.0
Computer A2: IP:192.168.1.6 Subnet:255.255.255.0
Computer A3: IP:192.168.1.7 Subnet:255.255.255.0
Computer A4: IP:192.168.1.8 Subnet:255.255.255.0
Computer A5: IP:192.168.1.9 Subnet:255.255.255.0
Computer A6: IP:192.168.1.10 Subnet:255.255.255.0
Computer A7: IP:192.168.1.11 Subnet:255.255.255.0
Computer A8: IP:192.168.1.12 Subnet:255.255.255.0
All computers in network A keep their original settings

Router: IP:192.168.1.50 Subnet:255.255.255.0
DHCP disabled

Computer B1: IP:192.168.1.51 Subnet:255.255.255.0
Computer B1: IP:192.168.1.52 Subnet:255.255.255.0
Computer B1: IP:192.168.1.53 Subnet:255.255.255.0
Computer B1: IP:192.168.1.54 Subnet:255.255.255.0
Computer B1: IP:192.168.1.55 Subnet:255.255.255.0
Computer B1: IP:192.168.1.56 Subnet:255.255.255.0
Computer B1: IP:192.168.1.57 Subnet:255.255.255.0
Computer B1: IP:192.168.1.58 Subnet:255.255.255.0
Computer B1: IP:192.168.1.59 Subnet:255.255.255.0
Computer B1: IP:192.168.1.60 Subnet:255.255.255.0
All computers in network B have the DNS servers given by the ISP, the workgroup name that the computers is network A have, and Gateway:192.168.1.50

Let me know if you need more help
- J
!