Networking Mess - Advice needed

[Carson Dyle]

Some additional questions:

I'd be willing to bet that you have just one public IP address through your internet provider. You could ask them. You could also go to a web page like http://zolx.com/ip to see what public IP address you're using.

Do it from computers on each part of your network. I would do:
- the server
- wired computer of Company 1
- wireless computer of Company 1
- wired computer of Company 2
- wireless computer of Company 2

Which company do you work for? I hope it's Company 1.

What is the model number of the D-Link router?

Are both the wired computers of Company 1 and their wireless devices connected through the D-Link's wifi on the same 192.168.0.x/255.255.255.0 subnet? That is, do they all have 192.168.0.xxx IP addresses?

What is the internal IP address of the server? Is its address pulled from DHCP or is it static (fixed)? Is this a Windows server? If so, which version of Windows?

And to clarify: The only (or main) problem you're having is that _wired_ computers from Company 1 are having intermittent problems connecting to the Internet? If that's not the case, please clarify.

Sketchy wifi connections most likely have to do with wifi router placement and signal strength, not your network configuration. So if that's also a problem, it should be tackled separately.

 

[Carson Dyle]

Question for others... I've never had a reason to set up a network like this, but is there any reason this configuration wouldn't work?

                   Internet
                      |
                 Cable Modem 
                 WAN: one public IP address                
                 LAN: 192.168.0.1
                   |     |
   +---------------+     +---------------+
   |                                     |
Router1                               Router2
WAN: 192.168.0.2                      WAN: 192.168.0.3
LAN: 192.168.1/24                     LAN: 192.168.2/24

 

[sdifox]

Question for others... I've never had a reason to set up a network like this, but is there any reason this configuration wouldn't work?

                   Internet
                      |
                 Cable Modem 
                 WAN: one public IP address                
                 LAN: 192.168.0.1
                   |     |
   +---------------+     +---------------+
   |                                     |
Router1                               Router2
WAN: 192.168.0.2                      WAN: 192.168.0.3
LAN: 192.168.1/24                     LAN: 192.168.2/24

He is apparently getting more than one up from ISP so gateway mode is the right one. So all you have to do is assign the ips from the ISP to the two routers.

 

[sdifox]

IP, not up.

 

[Carson Dyle]

He is apparently getting more than one up from ISP so gateway mode is the right one. So all you have to do is assign the ips from the ISP to the two routers.

That was an assumption you made. I'm not arguing, because I couldn't say, but I'd be willing to bet that they have only one. Definitely something that needs to be clarified.

assumption of mine: 1 external link shared by 2 companies, Rogers provides 2 ips.

yes, you are right about the first.. and i guess the second?

 

[sdifox]

That was an assumption you made. I'm not arguing, because I couldn't say, but I'd be willing to bet that they have only one. Definitely something that needs to be clarified.

The ISP knows about it and is not threatening them means they are already paying for multiple IP xd


Rogers is the big bad ISP up here in igloo nation.

 

[Carson Dyle]

OP: Have you gotten things worked out?

 

[boomerang]

Guys, just trying to learn a little something here. Based on his diagram, is the Server on the Internet? If not, why not?

 

[sdifox]

Guys, just trying to learn a little something here. Based on his diagram, is the Server on the Internet? If not, why not?

Well, access to internet is not exactly same as being on the internet.

 

[boomerang]

Well, access to internet is not exactly same as being on the internet.

Ah, yes. I understand the distinction and it's an important distinction. I have failed to clearly define my question. I should have asked can the Server be reached from the Internet? The OP states that his boss does not want that.

In other words is connecting it to the DPC 3825 isolating it from the Internet?

I don't see how connecting it to a wireless router in gateway mode isolates it in the slightest. But I may be wrong which is why I'm asking.

If I've misspoken again because I'm not well versed enough to be in the thread just tell me and I'll drop this. I was just curious.

 

[sdifox]

Ah, yes. I understand the distinction and it's an important distinction. I have failed to clearly define my question. I should have asked can the Server be reached from the Internet? The OP states that his boss does not want that.

In other words is connecting it to the DPC 3825 isolating it from the Internet?

I don't see how connecting it to a wireless router in gateway mode isolates it in the slightest. But I may be wrong which is why I'm asking.

If I've misspoken again because I'm not well versed enough to be in the thread just tell me and I'll drop this. I was just curious.

The gateway has firewall functions so he is not totally exposed. I wasn't being a pain, I just don't know how that gateway is configured :biggrin:

 

[boomerang]

The gateway has firewall functions so he is not totally exposed. I wasn't being a pain, I just don't know how that gateway is configured :biggrin:

I didn't think for a second you were being a pain. We were good and we are good.

 

[kevnich2]

Based on what I've read so far from the OP - it's time to stop looking at the rate of an MSP and just find a good MSP/IT Contractor in your area and get the problem fixed. By the time you "read up" on a little bit to even have a shred of understanding, the network could and would have been fixed.

If your day job is not in IT - there's really no point in trying to learn all this as it does you nor your company any good. With SMB's like this, the best thing to do is hire an MSP and pay them per month to basically run the IT side of things for you so you can concentrate on your job and business.

I don't undertand business that think it's ok to nickle and dime on IT and Network components, then wonder why things don't work correctly and it's costing them time and money.

If your business relies on technology, you will need to pay to make sure it's setup correctly. Once that's done, the MSP/Contractor only needs to come back when adding new components, which isn't a regular occurrence for most SMB's. I'd recommend using an actual MSP as opposed to a single IT contractor. A company will make sure things are well documented and will have multiple tech's available for reference and support.

 

[JackMDS]

Based on what I've read so far from the OP - it's time to stop looking at the rate of an MSP and just find a good MSP/IT Contractor in your area and get the problem fixed. By the time you "read up" on a little bit to even have a shred of understanding, the network could and would have been fixed.

If your day job is not in IT - there's really no point in trying to learn all this as it does you nor your company any good. With SMB's like this, the best thing to do is hire an MSP and pay them per month to basically run the IT side of things for you so you can concentrate on your job and business.

I don't undertand business that think it's ok to nickle and dime on IT and Network components, then wonder why things don't work correctly and it's costing them time and money.

If your business relies on technology, you will need to pay to make sure it's setup correctly. Once that's done, the MSP/Contractor only needs to come back when adding new components, which isn't a regular occurrence for most SMB's. I'd recommend using an actual MSP as opposed to a single IT contractor. A company will make sure things are well documented and will have multiple tech's available for reference and support.

+1 QFT. :thumbsup:

 

[Fallen Kell]

Based on what I've read so far from the OP - it's time to stop looking at the rate of an MSP and just find a good MSP/IT Contractor in your area and get the problem fixed. By the time you "read up" on a little bit to even have a shred of understanding, the network could and would have been fixed.

If your day job is not in IT - there's really no point in trying to learn all this as it does you nor your company any good. With SMB's like this, the best thing to do is hire an MSP and pay them per month to basically run the IT side of things for you so you can concentrate on your job and business.

I don't undertand business that think it's ok to nickle and dime on IT and Network components, then wonder why things don't work correctly and it's costing them time and money.

If your business relies on technology, you will need to pay to make sure it's setup correctly. Once that's done, the MSP/Contractor only needs to come back when adding new components, which isn't a regular occurrence for most SMB's. I'd recommend using an actual MSP as opposed to a single IT contractor. A company will make sure things are well documented and will have multiple tech's available for reference and support.

Not only this, but it is a business risk as well to the OP. I don't know how friendly the company he works with is with the one that shares the internet connection, but no matter the current relationship, there are possibly grounds for lawsuits related to lose of revenue, breach of security, etc., should there ever be a problem with the connection. It is simply not worth the business risk to not hire an outside company that will take on this job and have service guaranties which would then take on these risks instead of your company (just make sure both companies sign into the deal since they are both relying on the services). This way if/when things go bad, the fault in configuration relies on that hired company and not you at your company, which means the person/entity subject to the lawsuit is no longer you and your company, but the outside contracted company performing your IT services for the office.

 

[Old_newbie]

Hi Carson,
No, it's still the same situation as before. And at this point, we've just been rebooting the modem + router whenever we run into a no connection situation. Weird thing is I almost never have a connection issue (I'm on wifi connected to the cisco router) but maybe it's because I'm right beside it.

I think I will have to go the route and convince my boss as Fallen Kell, JackMDS and kevinich2 suggest. I had hoped I could do it on my own, but it really is out of my realm , and as kevinich2 pointed out, it would probably have already been fixed by someone who knows this stuff when it will take me a good long while to research it (plus no guarantee I wouldn't screw things up!)

OP: Have you gotten things worked out?

 

[Old_newbie]

Hi Carson,

Some additional questions:

I'd be willing to bet that you have just one public IP address through your internet provider. You could ask them. You could also go to a web page like http://zolx.com/ip to see what public IP address you're using.

Do it from computers on each part of your network. I would do:
- the server
- wired computer of Company 1
- wireless computer of Company 1
- wired computer of Company 2
- wireless computer of Company 2
I don't have access to Company 2 connections

Which company do you work for? I hope it's Company 1. Yes you are correct.

What is the model number of the D-Link router? It's a DIR 818L.

Are both the wired computers of Company 1 and their wireless devices connected through the D-Link's wifi on the same 192.168.0.x/255.255.255.0 subnet? That is, do they all have 192.168.0.xxx IP addresses? I don't know this. I could check my comp and another wired comp to see.

What is the internal IP address of the server? Is its address pulled from DHCP or is it static (fixed)? Is this a Windows server? If so, which version of Windows? I believe it is pulled from DHCP, pretty sure it's not static. We are running Vista (heh )

And to clarify: The only (or main) problem you're having is that _wired_ computers from Company 1 are having intermittent problems connecting to the Internet? If that's not the case, please clarify. Yes, it's really the wired that's the problem.

Sketchy wifi connections most likely have to do with wifi router placement and signal strength, not your network configuration. So if that's also a problem, it should be tackled separately.

 

[Carson Dyle]

I think you'd be amazed at how often professionals screw things up. I've seen offices and production facilities with 100s of workers rendered inoperable by the IT staff. Oops. D:

 

[Old_newbie]

Thanks kevnich2. I don't think it will work with our company to go the MSP route (if what I gather from what you are saying, it is a company you sign up with for IT services)... I think the only option for now would be the IT contractor. And only hope that if I can get one in, it will fix the issues permanently or at least while I am here.. heh

Based on what I've read so far from the OP - it's time to stop looking at the rate of an MSP and just find a good MSP/IT Contractor in your area and get the problem fixed. By the time you "read up" on a little bit to even have a shred of understanding, the network could and would have been fixed.

If your day job is not in IT - there's really no point in trying to learn all this as it does you nor your company any good. With SMB's like this, the best thing to do is hire an MSP and pay them per month to basically run the IT side of things for you so you can concentrate on your job and business.

I don't undertand business that think it's ok to nickle and dime on IT and Network components, then wonder why things don't work correctly and it's costing them time and money.

If your business relies on technology, you will need to pay to make sure it's setup correctly. Once that's done, the MSP/Contractor only needs to come back when adding new components, which isn't a regular occurrence for most SMB's. I'd recommend using an actual MSP as opposed to a single IT contractor. A company will make sure things are well documented and will have multiple tech's available for reference and support.

 

[Old_newbie]

That kind of scares me.. haha.. maybe that's why sometimes I like to try on my own.. at least that way it's on my own shoulders (well, only if it's my personal stuff, work.. is a different story)

I think you'd be amazed at how often professionals screw things up. I've seen offices and production facilities with 100s of workers rendered inoperable by the IT staff. Oops. D:

 

[sdifox]

Thanks kevnich2. I don't think it will work with our company to go the MSP route (if what I gather from what you are saying, it is a company you sign up with for IT services)... I think the only option for now would be the IT contractor. And only hope that if I can get one in, it will fix the issues permanently or at least while I am here.. heh

one thing you can do is use a wifi scanner software and walk around the places that has connectivity issue, maybe all you need is more wap.

 

[Old_newbie]

Sorry to sound dumb, but what is wap?

one thing you can do is use a wifi scanner software and walk around the places that has connectivity issue, maybe all you need is more wap.

 

[sdifox]

Sorry to sound dumb, but what is wap?

Wireless access point.

 

[Carson Dyle]

WAP = Wireless Access Point ... your wireless router(s).

It sounds like your network may be pretty screwed up, but we'd need to know how the IP addresses, both private (192.168.x.x) and public IP addresses are being used. And which devices are acting as DHCP servers. Sounds like there may be addressing conflicts, but whether or not that's the source of your current troubles is unknown.

If it's only the computers connected to the Nortel switch that are having problems, that would sound like it's potentially just a hardware issue. The first/easiest/cheapest thing I would try along those lines is changing the patch cable between the Nortel and the Cisco (assuming that's the only wiring between them). How many computers are actually using wired connections to that switch?

 

[Squeetard]

Looking at your sketch and I can see a loop and a conflict.
The Cisco router is in a loop from the rogers modem through the nortel switch and back to the router. I can't see a need for the connection from the nortel switch to the Cisco router.
Secondly the wireless has the same 192.168.0.1 IP as the Rogers router. Change that lan to 192.168.2.xxx.