Windows Forum

Ask something
Discussion Locked

SOHO Network

0 helpful
9 replies

by naamor

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am attempting a SOHO network. My equipment is as follows:
Server
350MHz
128MB RAM
Windows 2000 Server
2-3Com 3C905B-TX NICs

Workstation
1GHz
256MB RAM
Windows 2000 Professional
1-3Com 3C905B-TX NIC

Network
Netgear 8 port 10BaseT hub
CAT 5E straight cable
Cable Modem

Layout
Cable modem Cat 5E connected to NIC #1 on the server.
Cat 5E connected between NIC #2 and uplink (port 8) on the hub (link light on)
Cat 5E connected between port 2 on the hub (link light on) and NICon the workstation.

Server NICs
NIC #1: Configured to ISP specifications. Functioning properly for internet access

NIC #2: IP address 192.168.x.x (x=subnet and address I am using.)
Subnet Mask 255.255.255.0
Default Gateway is the same as the NIC #2 IP address.

Workstation NICs
IP address: same subnet as NIC #2 on server. address number is 1 digit higher than server NIC #2
Subnet Mask 255.255.255.0
Default gateway is the same as NIC #2 on the server.

Results:
I can ping NIC #2on the server from the workstation. I cannot ping from the server to the workstation.
I cannot map drives either way.
I have tried crossover cable direct from server to workstation.
I have tried changing NICs on the server.
Any other ideas wouldbe appreciated.

9 replies

by naamor

I tried changing NIC #2 to one of the standard ports(actually I tried it in each port). There was no change. Thanks for trying though.

by steffeno

ok...I have roughly a similar configuration.
What I suggest is that
1. remove the default gateway on your NIC #2 (the server NIC).
2. setup routing and remote access on your server so that you could share internet access for your workstation.

enjoy =)

by william jay

Got things a little backwards there mate. From the well written description of the network set up, you have some hardware conflicts arising out of incomplete understanding of the processes involved. Please don't blow off the good advice given in this forum just because you want to do it your way. Many of the posters here can do this setup in their sleep mode ...

Recommendations:
General
Server - 1Ghz/256
WorkStation - 350Mhz/128

Network cables
Server Nic1 - It works, don't fix it
Server Nic2 - Port 1 on the hub
Wkstn Nic - Port 2 on the hub

Hub - this hub runs at 10 while the Nics run at 100 ...

**A nic will not normally work plugged into an uplink port, (unless one uses a crossover cable or config switch, which is what the uplink port does already), it is intended for daisy-chaining devices. The uplink port and the next lower port are usually hard-wired shared, and so their use is mutually exclusive. Check the manual for the hub.

Address Resolution - assign the NIC2 to 192.168.xxx.1 and leave .2 .3 .4 for later assignment to the server also, wkstns to .11 .12 .13 ...

If server Nic2 is to be the default gateway, it need not be told, but the wkstns will need to know, so remove all reference and settings given to the server in that regard and set up the wkstns to use it.

There are reasons why an ip address might return ping results, without actually reaching the intended Nic, are the lights on the hub and nics blinking at the appropriate times ??
There is no mention of ip services to be used in the internal network. DNS and DHCP and so forth, as well as Active Directory Services, IIS, mail and so on ...

by naamor

I fully understand networking protocols, being that its part of my job.
Some of the comments above were incorrect. For instance the NICs in question are auto-sensing, therefore they will run at 10mbs when required.
Also weather thye 1gig or 350 issetup as server is irrelevent to the problem at hand. I have run server on 200 MHz machines.

This discussion is closed to new replies.