So all should be fine as I have researched and had replies to do it this way
And you have just learned how easy it is to get bad advice. :mrgreen:Or maybe is this a cause from my provider not allowing me to use 2 seperate lines as I see it as well?You have the right idea there:
* Your ISP will only assign youone IP address through the modem. The modem will pass that IP to a single device connected to it.
* A switch does not get assigned an IP address, nor does it isolate the routers from the modem. A switch is transparent; essentially, it just ties the modem and routers together on the same piece of wire.
* Therefore, as far as the cable modem is concerned, it sees two devices connected to it, and doesn't know how to handle that.
Please give us the exact model # of the X-Micro router; that info will come in handy in helping you configure things.
DMR
Wombat At Large
7,229 posts since Dec 2003
Reputation Points: 221
Solved Threads: 370
I thought the provider only sends one ip and what would the switch do for seperation.
Right.Routers can do the separation/translation (via NAT), but switches don't have that "intelligence".
For the network configuration you've described, the switch isn't needed.
* Connect the DI-524 directly to the modem.
* Configure the DI-524 with whatever info your ISP requires.
* Verify that computers connected to the DI-524 can access the Internet.
At this point you have a couple of options as far as adding the WF719 goes:
1. Connect one of the WF719's LAN ports to one of the D-Link's LAN ports. Since the LAN portion of a router is really just a switch, connecting the devices in this way just cascades/extends the D-Link's switch portion to the WF719's switch portion. Because the configuration doesn't make use of the WF719's WAN side, you won't need to worry about configuring NAT, DHCP, or anything else on the WF719; the connection to the D-Link should be transparent, with the D-Link handling all of the NAT, LAN IP addressing, etc.
* I believe the D-Link has auto-sensing ports, so you shouldn't need to use a crossover to connect the WF719 to it.
2. You can connect the WAN port of the 719 to one of the D-Link's Ethernet ports, although that will demand twiddling with the NAT/DHCP settings on the WF719 to get it (and the machines connected to it) configured to be one the same network segment as the D-Link. It isn't that hard to do, but it isn't necessary either, so I don't see a reson to go with this configuration.
3. I think the 719 has a wireless access point mode. If so, you can set it for that mode and connect it to the D-Link. In that configuration you would wire the 719's WAN port to one of the D-Link LAN ports, but the AP mode would automatically deal with getting IP addressing info from the D-Link, saving you from having to manually muck with the 719's software settings.
4. I believe the 719 can also act as a wireless bridge. Although it would be a slower (than Ethernet) connection, wifi bridging would allow you wirelessly connect the two routers.
as for the next one I right clicked and to disk management...
Ooops! I'm not sure why/howthat post ended up in this thread; it was meant to be a reply to another member's problem in another thread. :?: Anyway- it wasn't meant for us; I've deleted the post.
DMR
Wombat At Large
7,229 posts since Dec 2003
Reputation Points: 221
Solved Threads: 370
1. Seeing shares between the computers is a Good Thing, yes.
2. What happens if you connect the laptop via Ethernet to the D-Link router?
3. What happens if you connect the laptop via Ethernet to the XMicro router?
4. Disable WEP and/or any other security during the troubleshooting; doing so will eliminate one variable known to cause connection difficulties.
5. Setting the same SSID on both routers is the recommended way to go; please do that.
6. I'm assuming the desktop is happily connecting through the D-Link, yes?
7. To further isolate the source of the DNS error:
* Connect the laptop to the wireless network.
* Perform the following troubleshooting steps, in order, and post the results of each:
* Try reaching a site by its actual IP address instead of its URL. For example, open a browser and enter the following in the address/location bar:
http://66.102.7.99
If that takes you to Google, chances are pretty good that you've got a DNS problem.
* Click on the "Run..." option in your Start menu. In the "Open:" box of the resulting window, type "cmd" (omit the quotes) and hit Enter. This will bring up a DOS window.
At the DOS prompt, type the following commands, hit Enter after each, and tell us the results for each command:
ping The_D-Link_Router's_IP_Address
ping 66.102.7.99
ping www.google.com
* Again at the DOS prompt, type the following command and hit Enter. You won't see any result from the command, but when it completes, a second prompt with a flashing cursor will be displayed; close the DOS box once that happens:
ipconfig /all >"%userprofile%"\desktop\ipconfig.txt
The above command will have created a text file on you desktop named ipconfig.txt; double-click on the file to open it in Notepad, and then cut-n-paste the file's contents in your next post here. The contents of the file will give us some important details of your IP configuration.
DMR
Wombat At Large
7,229 posts since Dec 2003
Reputation Points: 221
Solved Threads: 370
You're welome; glad we could help. Post a follow-up when you get a chance; we'll be here...
DMR
Wombat At Large
7,229 posts since Dec 2003
Reputation Points: 221
Solved Threads: 370