G
Guest
Guest
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.
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.