We have several computers that run a business software in our building. We have a server in one room and all of the other computers connect to it. For many years, when the internet would go out, we couldn't connect to the server. One day, I was screwing around with my windows 10 settings and to my surprise, I did something that allowed us to connect to the server, even if the internet connection was unplugged. What did I do? I seem to remember that I bridged something? Thanks for any help in advance!
> [...] We have a server in one room and all of the other computers > connect to it. [...]
"connect to it" _how_? What, exactly, is connected to what, exactly?
> [...] For many years, when the internet would go out, we couldn't > connect to the server. [...]
"connect to the server" _how_?
"couldn't" is not a useful problem description. It does not say what you did. It does not say what happened when you did it. As usual, showing actual actions (commands) with their actual results (error messages, LED indicators, ...) can be more helpful than vague descriptions or interpretations.
> [...] What did I do? [...]
With my weak psychic powers, I have no idea. I don't know why you'd need to do anything. An Internet connection is not required to have a functional LAN.
The router is wired to the server with a usb cable and all of the laptops connect to the router via wiresless. The router is connected to the modem with a usb cable.
Although this doesn't makes sense the more I think about it. When the internet would go do down. The laptops would not connect with the server.
I made a note that the wired ip address to the server was .25, but the wireless IP address to the server was .210. I made a note to myself that I discovered that if the internet went down, and if I switched the connection on the server to the wireless connection, and if everyone's laptop was connected wirelessly, that the internal network would work. I then think that I "bridged" something so that the internal network would work regardess whether the server was connected with a usb or wirelessly.
Right now I can turn the internet modem off and everything works great (the server is plugged in and the laptops are wireless). I'm just trying to figure out what I did from an educational standpoint.
Does this make any sense? Again, I really appreciate that you have the patience to hear such a half baked story.
> [...] We have a server in one room and all of the other computers > connect to it. [...]
"connect to it" _how_? What, exactly, is connected to what, exactly?
> [...] For many years, when the internet would go out, we couldn't > connect to the server. [...]
"connect to the server" _how_?
"couldn't" is not a useful problem description. It does not say what you did. It does not say what happened when you did it. As usual, showing actual actions (commands) with their actual results (error messages, LED indicators, ...) can be more helpful than vague descriptions or interpretations.
> [...] What did I do? [...]
With my weak psychic powers, I have no idea. I don't know why you'd need to do anything. An Internet connection is not required to have a functional LAN.
That's a modem+router in one package. What, exactly, is your "the modem"? What, exactly, is your "The router"? What, exactly, is connected to what, exactly? (Hint: If a device has different types of ports, then "connected to device" is not enough detail.)
If you actually have a C7000, and its router section is still active, and it's connected to some _other_ router, then you'd seem to be cascading multiple routers, which could cause multiple problems.
> [...] When the internet would go do down. The laptops would not > connect with the server.
Treating that as one sentence, ...
"connect" _how_?
If "the internet would go do down" because of a problem with the router (whatever it might be), then any traffic through that (unspecified) router might be affected.
> I made a note that the wired ip address to the server was .25, but the > wireless IP address to the server was .210. [...]
Don't abbreviate IP addresses, unless everyone knows what you're omitting. If you actually have cascaded two routers, then the hidden parts of those addresses could be significant.
A computer/device, strictly speaking, does not have an IP address; a network _interface_ can have an IP address. If your (unspecified) "the server" has two network interfaces, then each one could (probably should) have its own IP address. If the omitted parts of those (partial) addresses are the same, then I'd expect problems if both were active at the same time. And if the omitted parts of those (partial) addresses are different, then I'd expect _different_ problems.
> [...] if I switched the connection on the server to the wireless > connection, [...]
I don't know what that means. What, exactly, did you change where?
> [...] I then think that I "bridged" something [...]
I think that you don't know enough to judge why any of what's happening is happening. You haven't described what you did, or what happened when you did it, clearly enough for me to conclude anything.
Currently, I know less than I thought that I did about your (unspecified) "the modem" and your new (unspecified) "The router".
> [...] I'm just trying to figure out what I did from an educational > standpoint.
I can't tell you what you did. I expect you to tell _me_ what you did, and what happened when you did it. And what you have. And how it's all connected.
> Does this make any sense? [...]
Less all the time.
> [...] Again, I really appreciate that you have the patience to hear > such a half baked story.
It's about exhausted. Put your story back into the oven, and come back with a more complete and coherent description of everything?
