first time trying, cant get switch to connect

[The Automation Guy]

Managed switches still need to be initially configured for the network they're on even if they're not being actively managed during operation.

That is incorrect.....

By default, managed switches are set up to run just fine as an "unmanaged" switch. They don't come set up with some "random" set of settings that prevent it from working on a normal network. They come set up in a mode that will work on all basic networks, and then it is up to the network administrator to customize the settings for their specific needs if needed.

....lots of variables when it comes to network configurations.

That is true, but by default every switch (including managed switches) are set up to work on a standard network without having to change any settings.

If a network admin has changed the settings on their network to something more complicated that breaks basic network functionality, then they are also knowledgeable enough to set up their managed switch prior to putting them into service. The opposite is not true however... Manufacturers don't ship their managed switches with some weird settings that break normal network functionality because that would require someone to log into the switch and play with the settings it in order for the switch to work on EVERY network, including the more advanced ones that might have some weird settings that break normal network functionality.

So with a managed (layer 3) switch you have the ability to.....

• enable a DHCP service to assign network address to connected devices...... but that service is not turned on by default
• segment your network using VLANs..... but the switch comes already set up with a default VLAN that includes all the ports (meaning it "works" out of the box on networks without VLANs).
• define routing rules to limit or control data transfer across the switch..... but no data is limited by default

etc, etc, etc,

 

[TonyR]

I don't think managed vs unmanaged is the issue here..... It sounds like the OP is trying to run a portion of his network without a DHCP server (router) connected and his computers/devices are set up for DHCP network addresses. That would be an issue with an unmanaged switch too.

You missed my point....an un-managed switch would not require a DHCP server or configuration and a non-novice would know that, as well as understanding basic networking.

I'm just saying a managed switch requires a little bit more understanding of basic networking than does an un-managed one. I'm not debating which type is better...

 

[TonyR]

If the switch is going to be kept on an isolated network there's no need to even configure it.
Just run it unmanaged.

You only need to configure it if you want to use it for multiple networks at the same time to keep them separate (and even then you could still leave it unmanaged if really had to).

You're preaching to the choir here...I understand when and where each type is needed and when not, etc. their purposes and capabilities.

I'm just saying that since it IS used the OP might very well STILL need to know how to either reset it or log into it to configure it as UN-managed!

 

[The Automation Guy]

You missed my point....an un-managed switch would not require a DHCP server or configuration and a non-novice would know that, as well as understanding basic networking.

I'm just saying a managed switch require a little bit more understanding of basic networking than does an un-managed one. I'm not debating which type is better...

I don't follow your logic. Devices on a network are required to have a valid network address in order to pass data on the network. An unmanaged switch doesn't have the ability to assign network address at all. Therefore an unmanaged switch DOES require either a DHCP server on the network assigning IP addresses or properly assigned static IP addresses set on every device on the network before devices can pass data between each other. While it is true that a managed switch has the ability to assign network addresses, it is NEVER turned on by default so the stock settings of a managed switch would cause it to act exactly like an unmanaged switch with this regard. Therefore using a managed or an unmanaged network switch will have ZERO effect on the network addresses of a normal network.

 

[TonyR]

I don't follow your logic.

Then you're not reading my post.

An unmanaged switch doesn't have the ability to assign network address at all.

.
I never said that.

Additionally, he bought the managed switched used off ebay and none of us or himself knows how it was configured when he received it.

 

[The Automation Guy]

An unmanaged switch doesn't have the ability to assign network address at all.

I never said that.

Umm, you said it in the post I was replying too....

You missed my point....an un-managed switch would not require a DHCP server.....

In fact using any switch (managed or unmanaged) DOES require a DHCP server OR the user has to assign static IP addresses to every device on that segment of the network.

Even the "Dual Nic" thread from the wiki goes into great length about how to set this all up with static addresses. Again, I suspect this is the real problem the OP is facing and the fact that he has a switch somewhere in this side of the network does not change that fact. It doesn't matter if the switch is an unmanaged switch or a managed switch set to it's default settings. Both will function in exactly the same way.....

Dual NIC setup on your Blue Iris Machine

In making your system more secure this is a great option to eliminate your cameras calling home / connecting to the internet This is a great place to start to setup a bit more secure network and learn more about IP/Subnets etc. before adding dual NICs: Router Security - Subnets and IP addresses...

ipcamtalk.com

 

[TonyR]

Umm, you said it in the post I was replying too....

Please show me where I said whatever it was that merited your reply, and I quote, "...An unmanaged switch doesn't have the ability to assign network address at all. "
I just want to know where it is in case it's my alter-personality is making statements without my knowledge...
What is the post number?

 

[The Automation Guy]

Please show me where I said whatever it was that merited your reply, and I quote, "...An unmanaged switch doesn't have the ability to assign network address at all. "
I just want to know where it is in case it's my alter-personality is making statements without my knowledge...
What is the post number?

You never said that specifically and I didn't attribute that line to you until my rebuttal post (which is after you claim I attributed that line to you). I would edit my rebuttal post to remove that, but I don't want to seem like I'm trying to change the narrative here. I don't know why you picked that line out of my reply either. The only point in my saying that was to walk someone through the process of BASIC networking functionality because that is what is wrong in the OPs situation. They don't understand BASIC networking functionality.

The whole managed switch vs unmanaged switch "debate" is not relevant to the actual problem. I have no idea why so many people - yourself included - are tying to change the narrative to "managed switches should never be used by novice users". Not only is that untrue, but it is nor relevant to the problem at hand.

 

[TonyR]

You never said that specifically and I didn't attribute that line to you until my rebuttal post which is after you claim I attributed that line to you. I would edit my rebuttal post to remove that, but I don't want to seem like I'm trying to change the narrative here.
I don't know why you picked that line out of my reply either.

I'm all about moving on here, we're just not communicating and I don't want a misunderstanding or a miscommunication so trivial as this to disrupt this thread or this forum or to prevent us, you and me, from co-existing comfortably on IPCT in the future.

Have a great day.......

 

[Mike A.]

This might be an easy way to help make sure that you're starting from a default config:

 

[alastairstevenson]

No they don't.
They'll just work.

Maybe not if the original configuration is still active. There could be any variety of restrictive settings in place if so.
I may have missed if it's been stated that the device has been reset back to factory defaults, where it would initially just operate as an unmanaged switch when connected to a new network.
Again - without checking out the linked user manual - there will generally be a 'reset to defaults' recessed button which can be used with a paper clip to get back to the as-built configuration.

 

[alastairstevenson]

In fact using any switch (managed or unmanaged) DOES require a DHCP server

Sorry but that's not correct.
The network can conveniently benefit from a DHCP server (but it's not mandatory, each device could be manually configured) but an unmanaged switch doesn't require one.
An unmanaged switch won't even have an IP address - what purpose would that have? If not managed, there is no requirement to address it.

 

[The Automation Guy]

In fact using any switch (managed or unmanaged) DOES require a DHCP server

Sorry but that's not correct.
The network can conveniently benefit from a DHCP server (but it's not mandatory, each device could be manually configured) but an unmanaged switch doesn't require one.

Why don't you quote the entire sentence before you start telling me I'm wrong.....

In fact using any switch (managed or unmanaged) DOES require a DHCP server OR the user has to assign static IP addresses to every device on that segment of the network.

Which is exactly the same thing you just said when you "corrected" me.

In fact the rest of that particular post talks about setting static ip addresses and links the "How To" thread on this exact subject.....

 

[looktall]

For the record, even if there is not a dhcp server and static addresses are not assigned, everything should still work on that Lan segment
Auto assigned addresses (169.254.x.x) will still talk to other auto assigned addresses on the same Lan segment.
They're just not routable.

So if you have a PC and a bunch of devices all in the same segment and all using auto assigned addresses they will still talk.

 

[Flintstone61]

you could slap an old cheapo router on that switch and let it handle ip addresses.

 

[Starglow]

you could slap an old cheapo router on that switch and let it handle ip addresses.

Even then the managed switch may need to be reset before it will pick up the new DHCP assigned IP address from the router. People want to believe everything is always plug and play when it comes to setting up networks but sometimes it isn't.

 

[Flintstone61]

Oh im sure that should be done 1st....
or right after the Cheapo Router slapping results in a shitshow.

I tossed a Cisco layer 3 switch (IP based) vs. a layer 2 ( LAN based) in to my 1st BI build ( in case I wanted to get cute with Vlans)
It was factory defaulted by ebay seller, and so it began sending POE power straightaway to the cams.

But ended up taking an old Dlink router/switch combo that some lady was tossing, and plugging it into the switch, and bing bang boom, I started going places. Cam setup was able to be initiated after that.
and no @wittaj I didnt plug the PC into the MthrFkin router! everything goes thru the switch.