Symptom of running out of subnet?
-
@JaredBusch said:
@LAH3385 said:
@Jason
Not that I am aware of. They are connected by a switch.You cannot access TCP/IP across two different subnets without something routing traffic.
While this is true - a Layer 3 switch can route between subnets - that's what I do for my VLANs. I don't have a router handle this, I have a my layer 3 switch handle it.
-
From the computer having the problem, run
tracert xxx.xxx.xxx.xxxReplace the x's with the IP of the server.
Do that same thing from the server to the PC's IP address.
Post the results if you can.
Also post the results from ipconfig /all from both.
-
@Dashrender said:
@JaredBusch said:
@LAH3385 said:
@Jason
Not that I am aware of. They are connected by a switch.You cannot access TCP/IP across two different subnets without something routing traffic.
While this is true - a Layer 3 switch can route between subnets - that's what I do for my VLANs. I don't have a router handle this, I have a my layer 3 switch handle it.
I never said a router. I said something routing traffic, which does of course include a L3 switch with routing capabilities.
-
@Dashrender said:
While this is true - a Layer 3 switch can route between subnets - that's what I do for my VLANs. I don't have a router handle this, I have a my layer 3 switch handle it.
Some people argue that there is something unique there. But those of us from the old days have long pointed out that an L3 Switch is a marketing term for a multiport router. Anything doing routing on L3 is a router, no matter what marketing label is put on it. There is value to knowing what is considered a switch or not, but I've never seen any definition of router that does not completely include an L3 switch every time. It's just that L3 switches do L3 and L2 transparently across many ports.
-
@scottalanmiller said:
@Dashrender said:
While this is true - a Layer 3 switch can route between subnets - that's what I do for my VLANs. I don't have a router handle this, I have a my layer 3 switch handle it.
Some people argue that there is something unique there. But those of us from the old days have long pointed out that an L3 Switch is a marketing term for a multiport router. Anything doing routing on L3 is a router, no matter what marketing label is put on it. There is value to knowing what is considered a switch or not, but I've never seen any definition of router that does not completely include an L3 switch every time. It's just that L3 switches do L3 and L2 transparently across many ports.
LOL - good point.
-
I've search on finding the differences but they are clearly wrong. Like so wrong that how anyone buys them I don't know. I see weird claims like the difference is speed, or that router means software and switch means ASIC. Which is absolutely false. Routing is a function, not an implementation, routers have long been offered on ASICs. Switches can be done in software. Both are specific network things, not "types of hardware."
I saw another that said that routers have WAN interfaces and L3 Switches do not. Also obviously false. Any port can be either. Most routers don't have anything but Ethernet ports. Some switches have non-Ethernet options.
The degree to which people just make up illogical crap to try to excuse the marketing around the L3 switch concept is extreme. bottom line appears to be... it's totally made up and isn't actually a thing at all.
-
There is a lot of "typically it means this" and that is somewhat useful. Switches are typically faster, have more ports, are implemented in custom hardware, etc. But typical does not a technology define. There do not appear to be any definitions that actually differentiate one from the other just this kind of "feeling" that people have.
Which is fine, it's a marketing term. Just important to know that an L2 switch is really a "multiport bridge" and an L3 switch is really a "multiport router" and anything beyond that is really just "generally acceptable generalities around marketing and intended use cases."
