D-Link WBR-2310 No Wired Connectivity

[oskar2001]

I have an Internet Connectivity problem which I believe was caused by resetting our D-Link WBR-2310 router. We have a strange, perhaps illogical network setup in our office. Although it was set up before my time, I have figured it works as follows:

(1) A wired/wireless router (let's call it Router A) is connected directly to the DSL modem.

(2) An Ethernet cord runs from this router to a 5 port switch.

(3) 4 cords run from the switch to individual workstations. These computers obtain their IP addresses automatically.

(4) 1 cord runs from the switch to another wired/wireless router (let's call it Router B).

(5) Two cords run from Router B to individual workstations (let's call them Workstations C). These computers used permanent IP, subnet mask, default gateway, and DNS server addresses. I understand that this was done because they could not obtain their IP addresses automatically.

The problem I've caused seems to stem from me resetting Router B to the factory settings while trying to secure its signal and changing its IP address from 192.168.0.1 to 192.168.1.1 (in order to avoid conflict with the modem which has the same IP address). Once I did that, Workstations C could not access the Internet.

I have tinkered with the TCP/IP settings for Workstations C (e.g. by changing the default gateways to the Router B's new IP address), but it doesn't work. What else should I be doing? Should I go into the router admin to change settings there? I would appreciate any help.

[stroyal]

If router B was being used as a router, you will have to wait for our network experts.
Sub networks, give me a headake.
The 198.168.0.1 should be router A, not the modem.

Are you sure B was being used as a router, or just a switch?

Edit;
Oh. Welcome to TechIMO!

[stroyal]

Here is a tutorial on subnets.
As you can see, it is not as simple as making up a different IP.

IP Sub-Networking Mini-Howto

If I thought I would ever need it, I would endure the headache, but I don't, so I won't.

[Nude_Lewd_Man]

If router B was being used as a router, you will have to wait for our network experts.
Sub networks, give me a headake.
The 198.168.0.1 should be router A, not the modem.

Are you sure B was being used as a router, or just a switch?

Edit;
Oh. Welcome to TechIMO!

You didn't send me a PM..!!



See comments "in-line" below:

I have an Internet Connectivity problem which I believe was caused by resetting our D-Link WBR-2310 router. We have a strange, perhaps illogical (Yes, it seems a bit odd...especially with such a small number of network devices) network setup in our office. Although it was set up before my time, I have figured it works as follows:

(1) A wired/wireless router (let's call it Router A) is connected directly to the DSL modem. What is the LAN IP and subnet of this "R1" device? (Asking so I can give better advise later)

(2) An Ethernet cord runs from this router to a 5 port switch. Makes sense, quite a normal thing....so far... I'll refer to this as "S1".

(3) 4 cords run from the switch to individual workstations. These computers obtain their IP addresses automatically. Again, what is the network address for this - the IP, the subnet mask and the "default gateway"... I know that you're likely to see the last (host) section of the IP addresses change, but just for a snapshot.... Oh, and I'd like to see what the DHCP server's IP is too...

You can either copy-paste from the CLI (Start --> Run --> cmd [Enter] --> IPCONFIG [Enter] ) and use example1 below, or use the IP/subnet abbreviation, as in example2:
example1
IP 192.168.1.5
Subnet 255.255.255.0
192.168.1.1

example2
192.168.1.5/24
192.168.1.1

(4) 1 cord runs from the switch to another wired/wireless router (let's call it Router B). I'll refer to this as "R2" as it is the second Router...

(5) Two cords run from Router B to individual workstations (let's call them Workstations C). These computers used permanent IP, subnet mask, default gateway, and DNS server addresses. I understand that this was done because they could not obtain their IP addresses automatically. As these have static IPs, I (we) will need to see what the IP, subnet and gateway details are.

The problem I've caused seems to stem from me resetting Router B to the factory settings while trying to secure its signal and changing its IP address from 192.168.0.1 to 192.168.1.1 (in order to avoid conflict with the modem which has the same IP address). Once I did that, Workstations C could not access the Internet.

I have tinkered with the TCP/IP settings for Workstations C (e.g. by changing the default gateways to the Router B's new IP address), but it doesn't work. What else should I be doing? Should I go into the router admin to change settings there? I would appreciate any help.

As mentioned, see in-line responses...but I would also like to know what port R2 is connected to S1, as this could be a major factor in how R2 thinks it should be working...


Let me/us know the details above, and then we can start trying to help you to help yourself.....

[stroyal]

Actually, I was waiting for a reply. so you would have more info.
I knew it would be over my head, if it was not just a switch.

Hows it going?

[oskar2001]

I believe that I might have solved the issue by buying a $15 switch and plugging in all the devices involved, including the wireless router. Now the two workstations have Internet access and mobile devices can connect securely to the router. I'm not opening up any glaring vulnerabilities by doing this, am I?

[Nude_Lewd_Man]

Actually, I was waiting for a reply. so you would have more info.
I knew it would be over my head, if it was not just a switch.

Hows it going?

YGPM, but I'm fine - just realised that I asked you to give me your thoughts and suggestions on my site....but then forgot to give you a link... :doh:
Nude_Lewd_Man's Site

I believe that I might have solved the issue by buying a $15 switch and plugging in all the devices involved, including the wireless router. Now the two workstations have Internet access and mobile devices can connect securely to the router. I'm not opening up any glaring vulnerabilities by doing this, am I?

That would've been the best option really. Given that I/we didn't know whether the machines were close enough for that to be an option, we couldn't suggest it before... I would *guess* that R2 prolly had an IP of 192.168.0.2 but, if you had the link between R1 and R2 going into the switch ports in R2 (not WAN port) then it *might* have saved you $15 on the switch....

Bear in mind that that us guesswork based on the minimal info available from your previous post...

Glad to hear that you're back up though...