Hi,

I just recieved a Bay Networks (Now Nortel) BayStack 350T 16-port managed 10/100 autosensing switch from ebay. I have it connected to my workstation via a serial connection to the switch's console. I have a Cat 5 running from my current router (with DHCP) that is going to an ISP to port 1, and another Cat 5 running from port 2 to my workstation's NIC. I have reset the switch to default settings, all ports other than the two dead ports are enabled and are all in the same VLAN. In "IP Configuration" i have specified my current router (192.168.1.1) as the default gateway and have not changed anything else. My problem is that i am not recieving any DHCP or connection for that matter at the workstation connected to the switch. I have read the user manual i got of of Nortel's site, but it doesn't explain how to set the switch up but more give you an idea of what to enter into the config fields. I have never setup a managed switch and i am very confused if the switch is broken or configured wrong. At this point i would just like to get DHCP and connectivity to the internet. If any one can point me in the right direction or can tell me what to change that would be excellent.

Thanks for your time.

Try to set your eth0's IP to 192.168.1.2, gateway to 192.168.1.1, DNS address to the ISP's DNS address. It should work.

The router is obtaining Internet IP address by DHCP. Once router is working, your workstation is going to the Internet through the router. So the workstation doesn't need an Internet IP, it just need to talk to the router. That is why I suggested you setup a LAN address in your workstation. Hope this helps.

i am trying to get a 192 ip through the switch and it's not getting one, that is the problem. I'm not trying to get a public ip from my workstation, i'm looking to get a private one and the dhcp request isn't comming through the switch when i'm plugged into it. I shouldn't have to make any network setting static, the router's DHCP should work through the switch.

ok, i see, let's troubleshoot step by step,

1. give your box a static ip, and ping your router 192.168.1.1, if it gets any reply, that means your brandnew switch is working fine. or if you have any other computers, put them on the switch, if they can see others, it means the swithc is ok.

2. then the problem is dhcp configuration of the router

I have a couple of the old 24 port varieties of the BayStack and have never had any problems with them. Let's verify a few things first:

(1) Do you get a LED illuminated on the switch when you plug your cat5 from your workstation to the switch and your workstation is on?

If not, are you using the same cable to connect to the switch as you were to connect directly to the router? If so, it is probably a crossover cable and you need a straight through cable to connect to the switch.

(2) If (1) is OK, what does ifconfig eth0 on your workstation say?

(3) Have you verified that the dhcpd is running on your router? Does it have an illuminated LED on the switch port to which it is connected?

If you have defaulted the Baystack then all ports will be auto and in the same vlan. The most likely mistake would be that the cable between the router and the switch is the wrong type.

If you has a PC connected to a router with switchports on it as they mostly do, you would need a straight cable. If you then used this straight cable to connect the router and the switch together it wouldn't work.

Just a guess.

really? My network starts at a Motorola Modem over straight Cat 5e cable to my 3com HomeConnect 802.11G/5-Port Switch router (http://www.3com.com/products/en_US/d...=3CRWDR100U-72) then going to a Straight-wired 50ft. Cat 5e going to port 1 on my BayStack 350T. So what your saying is that I need a cross-wired cable between my 3com Router and my BayStack?

ok, now my switch is connected to the 3com switch/router with a Cat6 crossover to port 1 on the baystack, port 2 going to a staight-wired Cat 5e to a WinXP machine requesting dhcp net config. The baystack is on factory default config, still not working. Is it safe to say the switch is dead? I do know that ports 10 and 13 don't work. Depending on what ports are disabled/enabled, the switch will fail it's port loopback test on reset, until i enable them all and reset. Every reset after will fail port loopback. Is this thing a junker?