Connecting EZX55W switch to E1000 router

I just purchased a E1000 wireless router to replace our BEFSR41 router that died. The old router had a EZX55W switch connected to it  (4 computers, xbox, blu-ray player) and I would like to do the same with the E1000. There is no uplink port on the E1000. Any knowledge out there on the proper way to accomplish this or is it not possible?
Thanks in advance for any help.
Rob

It's Good to know that you were able to resolve your issue your own...Enjoy .

Similar Messages

  • Connect unmanaged switch to 887VA fast ethernet port

    I tried connecting an unmanaged (and dumb) switch to one of the four fast ethernet ports on the back of the router. I configured the port to act as an access port bound to a specific VLAN, say no. 100.
    What I can see on the LEDs of the unmanaged switch is that the link goes up and down every few seconds. I don't know if this is related to the spanning tree protocol and unfortunately the unmanaged switch doesn't know about STP and doesn't send out BPDUs.
    So, how I should configure the port in order to avoid the link going up and down?
    The actual conf. for the port:
    interface fastEthernet 3
    switchport mode access
    switchport access vlan 100

    What do you mean by dumb siwthc? What model/make/company is that switch?
    Can you try to do the reset of the switch so that it wipe off all the config what so ever present on the box and then try to connect the switch to the router?

  • 2 switches and 1 router

    What is the best method to connect 2 switches to 1 router when both switches run the same VLANs? Method A - Enable etherchannel on the router and connect both switches to the router. Method B -Connect the two switches together and then connect one of the switches to the router.

    You are (probably) looking for a BVI - Bridged Virtual Interface (or maybe IRB - Integrated Route/Bridging ....don't remember).
    The bridged interfaces talk to each other as if connected via bridge/switch, the collective bridged interfaces talk to the other side as if it was an individual routed interface.
    So, each of your switches connect to a router's ethernet, those interfaces are bridged. The Bridged ethernet interfaces talk to (for example) a serial interface as a single unit/address/broadcast domain.
    Check it out
    Good Luck
    Scott

  • Unable to connect SD2008 switch to WRT610N

    I recently acquired a SD2008 8 port switch.  I attempted to connect it to my existing WRT610N router, and I am unable to get connectivity to the internet with devices connected to the switch.  I am not using a crossover cable to connect the switch to the router, but as I understand it, that should not matter as the SD2008 does not require this.  I have the switch connected via port 1 on the switch to port 4 of my WRT610N.  Any suggestions? 

    I actually already tried that and unfortunately, it did not work.  I was then looking on various sites regarding the SD2008 version 2.1 which is the version I have, and there have been technical concerns about this particular unit.  I noted it had a lifetime warranty, and took it back to where I bought it, and they gave me a new one-version 3.  I plugged it in and it worked on the first try without power cycling the network or router. 
    Thank you for your reply.  Maybe it was just a bad unit.  I could not figure it out for the life of me. 

  • Cannot get Cisco Connect to install or set up E1000 router

    1. We have been using an E1000 router connected to our main Dell desktop (running XP SP3) to handle a small home network that includes wife's laptop which has card and kids' desktop with USB wireless adapter.
    2. We purchased a new main desktop computer, ZT Systems running Windows 7. I am attempting to install Cisco Connect on this computer and set up the router. I reset it to factory specifications because I figured I'd have to start from step 1.
    3. I cannot find the original setup CD that came with the router and I have no clue whatsoever what my password is.
    4. So, I downloaded CiscoConnect.E1000.1.3.11069.2, the appropriate software to my desktop, and have been trying to install the software and configure the router, without any success whatsoever. When I plug it in, it asks me to connect the router which I do. It then will get to 25 percent of setup and stop, saying it couldn't be configured. At the same time, I have no Internet access, keeps telling me it's looking for networks when I actually am trying to set up a network.
    5. I've tried the steps for configuring without the software, Windows still searches for a network and tells me it can't find one and I have no Internet access.
    6. Can anyone tell me what's going on here, what I'm doing wrong, anything I'm missing? Do I need to just buy another router or what? Thanks in advance for any help.

    Does your desktop have wireless? If so, switch it off and retry the installation. Make sure to reset the E1000 by holding the reset button for about 10 seconds.

  • Help with connecting MacBook Pro with Cisco Routing and Switches?

    I'm running a CiscoASA 5510 router with several Cisco WS-C2960-48TT-L switches on a local network to connect with MacBook Pro. I need to be able to restrict access to specific users via their computer MAC address. ie: Joe Blow is limited to connecting through Switch 1 on port 10 and anywhere else he tries to plug in will simply not work.

    You need to look at the documentation that came with your router and switches. Or ask your network admin to set it up. Your question has nothing to do with your Macbook Pro configuration. MAC filtering is done in the router not in the computers/devices connecting to the router.

  • I just got my cable company to switch my wireless router to a wired one considering now I have the wireless airport device (the newest one) but now I can't get a wireless signal. The router works when directlyplugged in,the aiport wireless device is green

    I just got my cable company to switch my wireless router to a wired one considering now I have the wireless airport device (the newest one) but now I can't get a wireless signal. The router works when directlyplugged in,the aiport wireless device is green. I've tried going through my new MacBook Pro settings and it the diagnostics check, it says network changes detected, I tell it that it "yes" does connect to a cable modem, it tells me to restart it, after I do it asks if there are any other devices hooked up ( firewall) and when I say no it tells me that it can't fix the problem.
    Now I know that I probably have a new IP address because of the cable company switching the boxes but it was working fine with the other box, now there isn't a signal to be had on it!
    Please anybody out there that can help!!!??

    Any time you change networking hardware it is always a good idea to perform a complete power recycle with the new equipment. Check out the following AirPort User Tip. Please post back your results.

  • Connecting a Switch to the E4200

    Have a Linksys E4200 router located in my basement and I am experiencing a puzzling wired connectivity issue as follows: 
    Port 1 on the router is for my study, I have no problem getting connection regardless  if I use my study's Ethernet jack or if I run a 5 ft. cable (hereinafter THE CABLE) from the router’s  port 1 to my laptop (i.e., cabling does not make a difference).
    I then connect to router port 1 an EZXS55W Linksys switch (using port 1 on the switch and THE CABLE) and then connect my laptop to port 2 on the switch using a second cable.  I am unable to connect to the network/internet even after rebooting both the cable modem and router.
    I then reconnect my study to port 1 on the router, I go to my study and connect the study’s Ethernet  jack using THE CABLE to port 1 on the switch and using a second cable from port 2 on the switch to my laptop. …. I get an network/internet connection immediately !
    Can someone assist with this puzzle ?  Has anyone seen this before ?  FYI, I have had the exact problem with switches EZXS88W and SE2500 (no longer own this).
    Thanks,
    Zach
    Solved!
    Go to Solution.

    Sorry but the description of the problem is quite vague and a bit confusing.
    To get the switch working properly make sure the router is connected to the uplink port of the switch. Take note: When Uplink port is used, the port adjacent to it becomes inactive (port5) because they are shared. Switches are really pass-through devices so nothing is to be configured.
    "Also be aware that on the outside of the box for the EZXS88W switch, there is a picture showing a "Broadband Router" connected to port #1 of the switch.  The Uplink is shown as being connected to another switch."  The picture shown outside the box refers to how you could connect the switch to other networking devices; router, switch or a hub to expand your network.
    Check out these links, hope it could help;
    Connecting a Linksys switch to a router
    http://homekb.cisco.com/Cisco2/ukp.aspx?pid=93&vw=1&articleid=22996
    Checking if the router is working properly when connected to a switch
    http://homekb.cisco.com/Cisco2/ukp.aspx?pid=93&vw=1&articleid=22996

  • Networking Best Practices - Connecting Two Switches

    Connecting two switches together is an easy task, which makes it so frustrating when it doesn’t work. Here we will outline a basic scenario of connecting two switches and achieving connectivity. In these scenarios we will be using commands and settings that will work for most modern PowerConnect switches. However this does not cover all possible scenarios and the commands may differ slightly from switch to switch.
    For instance, in most cases you can use General or Trunk mode when connecting two switches. However, on the PowerConnect 62xx series switches, you must use General mode if you want to allow management traffic onto the switch over the PVID.  If you use Trunk mode, you will not have the default VLAN on those ports.  The ports will only allow tagged traffic.
    For more details on the difference between Access, General, and Trunk modes, follow this link.
    http://en.community.dell.com/support-forums/network-switches/f/866/p/19445142/20089157.aspx#20089157
    It is always a good idea to have the user and CLI guide for your switch, to reference any possible changes in command syntax.
    http://support.dell.com/support/edocs/network/
    Layer 2
    Layer 2 switches operate at the data link layer of the OSI model. Layer 2 is responsible for error checking and transmitting data across the physical media. MAC addressing sources and destination protocols are layer 2 protocols. Layer 2 switches use the MAC address of data packets to determine where those packets should go. It learns the MAC addresses of all devices and creates a segment/forwarding table.
    When a switch receives a frame with a destination address that isn't in its forwarding table, the switch forwards the frame to all other ports. If the destination machine responds to the server, the switch will listen to the reply and learn which port the destination machine is attached to. It then adds that MAC address to the forwarding table.
    The Dell PowerConnect Layer 2 switches have ports that all operate in VLAN 1 by default. If it is acceptable to have all traffic on the same broadcast domain, then you can simply leave the default alone, connect the two switches and traffic will flow.
     If you do not want all traffic on the same broadcast domain, then we need to look at adding additional broadcast domains through the use of VLANs.
     We will use 3 VLANs for the following scenario.
    VLAN 1=Management
    VLAN 2=Client
    VLAN 3=Server
    To create these VLANs we do the following commands (VLAN 1 is already created by default)
    console(config)# vlan database
    console(config-vlan)# VLAN 2
    console(config-vlan)# VLAN 3
    console(config-vlan)# exit
    We can then name the VLANs to help keep things organized.
    console(config)# interface vlan 2
    console(config-vlan)# name Client
    console(config-vlan)# exit
    console(config)# interface vlan 3
    console(config-vlan)# name Server
    console(config-vlan)# exit
    Once we have the VLANs created we can place a device in that VLAN by placing the port it plugs into, in access mode for the specific VLAN.
    So we have a workstation on port e2 we want to be placed in VLAN 2, we would issue the following commands.
    console(config)# interface ethernet 1/e2
    console(config-if)# switchport mode access
    console(config-if)# switchport access vlan 2
    console(config-if)# exit
    The next port plugs into a server on port e3 we want on VLAN 3, we would issue these commands.
    console(config)# interface ethernet 1/e3
    console(config-if)# switchport mode access
    console(config-if)# switchport access vlan 3
    console(config-if)# exit
    For the ports connecting the two switches together, we place the ports in trunk mode and specify the native VLAN and allowed VLANs.
    For the port e1 that connect the two switches to each other would be configured like this.
    console(config)# interface ethernet 1/e1
    console(config-if)# switchport mode general
    console(config-if)# switchport general allowed vlan add 2,3 tagged
    console(config-if)# switchport general pvid 1
    console(config-if)# exit
    Once these VLANs and port settings are made on both switches. A server connected to switch A on VLAN 3 should be able to communicate with another Server connected to switch B that is also in VLAN 3.  Without the use of a router the devices in VLAN 3 will not be able to communicate with devices that are outside of their broadcast domain (i.e. VLAN 2 devices could not reach VLAN 3 devices)
    Layer 3 + Layer 2
     Until recently, routers were the only devices capable of layer 3 protocols. Switches capable of routing are now available and in widespread use. In most cases we will connect our layer 2 switches to a Layer 3 capable switch to perform our routing for us.
     On the layer 3 switches we will use the same VLANs and setup that we did with the layer 2 switches.  Then we will add to the configuration.
     We can assign an IP address to each switch with the following command.
    Switch A
    console(config)#ip address 172.16.1.1 255.255.255.0
    Switch B
    console(config)#ip address 172.16.2.1 255.255.255.0
    Then we will enable routing only on Switch A
    console(config)# ip routing
    Switch A we assign an IP address to VLAN 2 and enabling routing on the VLAN.
    console(config)# interface vlan 2
    console(config-if-vlan2)# Routing
    console(config-if-vlan2)# ip address 172.16.20.1 255.255.255.0
    console(config-if-vlan2)# exit
    Switch A we assign an IP address to VLAN 3 and enabling routing on the VLAN.
    console(config)# interface vlan 3
    console(config-if-vlan2)# Routing
    console(config-if-vlan2)# ip address 172.16.30.1 255.255.255.0
    console(config-if-vlan2)# exit
    On both switch A and switch B we will keep things simple and use interface 1/e1 for the connection between each switch. Setting both switches 1/e1 to general mode, allowing the additional VLAN 2,3, and keeping the PVID of 1.
    console(config)# interface ethernet 1/e1
    console(config-if)# switchport mode general
    console(config-if)# switchport general allowed vlan add 2,3 tagged
    console(config-if)# switchport general pvid 1
    console(config-if)# exit
    We will have one client computer connect to switch A on port 1/e2 and one client connect to switch B on port 1/e2. These ports will be in access mode for VLAN 2, and the config should look like this on both switches.
    console(config)# interface ethernet 1/e2
    console(config-if)# switchport mode access
    console(config-if)# switchport access vlan 2
    console(config-if)# exit
    We will have another client computer connect to switch A on port 1/e3 and one client connect to switch B on port 1/e3. These ports will be in access mode for VLAN 3, and the config should look like this on both switches.
    console(config)# interface ethernet 1/e3
    console(config-if)# switchport mode access
    console(config-if)# switchport access vlan 3
    console(config-if)# exit
    On Clients connected to Switch A we will assign an IP address and gateway based on the VLAN they are in access mode for.
    Client connected to access port for VLAN 2.
    IP Address:172.16.20.11
    Default Gateway:172.16.20.1
    Client connected to access port for VLAN 3.
    IP Address:172.16.30.11
    Default Gateway:172.16.30.1
    On Clients connected to Switch B we will assign an IP address and gateway based on the VLAN they are in access mode for.
    Client connected to access port for VLAN 2.
    IP Address:172.16.20.12
    Default Gateway:172.16.20.1
    Client connected to access port for VLAN 3.
    IP Address:172.16.30.12
    Default Gateway:172.16.30.1
    External Connection
    At some point we may want traffic to have an external connection. To do this we can create a new VLAN for our point to point connection from Switch A to our router. We will use VLAN 7 for this and assign an IP address.
    console(config)# vlan database
    console(config-vlan)# VLAN 7
    console(config-vlan)# exit
    console(config)# interface vlan 7
    console(config-vlan)# name WAN
    console(config-if-vlan2)# Routing
    console(config-if-vlan2)# ip address 10.10.10.2 255.255.255.0
    console(config-if-vlan2)# exit
    On our router we will assign an IP address of 10.10.10.1
    Then place the port connecting the switch and router into access mode for VLAN 7.  In this case we use port e4.
     console(config)# interface ethernet 1/e4
    console(config-if)# switchport mode access
    console(config-if)# switchport access vlan 7
    console(config-if)# exit
    We will then need to put in a default route with the next hop as the router IP address.  This allows the switch to know where to route traffic not destined for VLANs 2, 3, or 7.
    console(config)#ip route 0.0.0.0 0.0.0.0 10.10.10.1
    Next on the router we’ll need to add a route back so the router knows about the networks attached to switch A.  Generally adding a static route on most routers is done with the following command: 
    ip route {Network} {Wildcard Mask} {Next Hop-IP}
    In our case here are the 2 static routes we could use.
    Ip route 172.16.20.0 0.0.0.255 10.10.10.2
    Ip route 172.16.30.0 0.0.0.255 10.10.10.2
    The routing that we enabled on Switch A will enable traffic from the other VLANs to traverse over port 1/e4 to the router, connecting us to external traffic. The routes we added to the router allow the traffic to flow back to the switch over port 1/e4.
    Layer 3 + Layer 3
    In some situations we have two switches, each setup to route for its own broadcast domain, which we want to connect together. In this situation we no longer have a need to use Trunk or General mode between the switches. Instead we can create a common VLAN that will be used for the connection between the two switches.
    To create this VLAN we will run the following commands on both switch A and B
    console(config)# vlan database
    console(config-vlan)# vlan 6
    console(config-vlan)# exit
    console(config)# interface vlan 6
    console(config-vlan)# name Connection
    console(config-vlan)# exit
    On switch A we assign an IP address to VLAN 6 and enable routing on the VLAN.
    console(config)# interface vlan 6
    console(config-if-vlan2)# Routing
    console(config-if-vlan2)# ip address 172.16.60.1 255.255.255.0
    console(config-if-vlan2)# exit
    On switch B we assign an IP address to VLAN 6 and enable routing on the VLAN.
    console(config)# interface vlan 6
    console(config-if-vlan2)# Routing
    console(config-if-vlan2)# ip address 172.16.60.2 255.255.255.0
    console(config-if-vlan2)# exit
    On both switch A and B we place the connecting ports into Access mode for VLAN 6.
    console(config)# interface ethernet 1/e1
    console(config-if)# switchport mode access
    console(config-if)# switchport access vlan 6
    console(config-if)# exit
    We then need to make some changes to switch B now that it is layer 3 and not layer 2 and has its own broadcast domain.
    We will enable routing on Switch B
    console(config)# ip routing
    What used to be VLAN 2 and 3 will now be VLAN 4 and 5 for our separate broadcast domains.
    Switch B we assign an IP address to VLAN 4 and enabling routing on the VLAN.
    console(config)# interface vlan 4
    console(config-if-vlan2)# Routing
    console(config-if-vlan2)# ip address 172.16.40.1 255.255.255.0
    console(config-if-vlan2)# exit
    Switch B we assign an IP address to VLAN 5 and enabling routing on the VLAN.
    console(config)# interface vlan 5
    console(config-if-vlan2)# Routing
    console(config-if-vlan2)# ip address 172.16.50.1 255.255.255.0
    console(config-if-vlan2)# exit
    On Clients connected to Switch B we will assign an IP address and gateway based on the VLAN they are in access mode for.
    Client connected to access port for VLAN 4.
    IP Address:172.16.40.11
    Default Gateway:172.16.40.1
    Client connected to access port for VLAN 5.
    IP Address:172.16.50.11
    Default Gateway:172.16.50.1
    The end result should look like this.
     Troubleshooting
    If we are having issues with connectivity, we may need to place some static routes in place to help traffic to the next hop in the network.
    On switch A we configure a static route to help traffic to the next hop in the network, which is the router.
    console(config)# ip route 0.0.0.0 0.0.0.0 10.10.10.1
    The external router will also need a path defined back to all networks/VLANs.
    To check the status of a port we can use the command. Show interfaces detail, this will help us see the port status. For example to check the status of port 48, we would run this command.
    console# show interfaces detail ethernet 1/g48
     To check routing paths:
    console# show ip route
    The IP address of the network for each VLAN should be listed as C – Connected. Then also a path or default route to your upstream router.
    We can use basic ping commands from a client to help test where connectivity is dropping off at. By doing this we can narrow down where in the network to start troubleshooting.
    -Ping from client to default gateway, being the VLAN the client is in access mode for. If this fails then we may need to double check our client settings making sure the proper IP and gateway are being used.
    -Ping from client to the ip address of the switch the client plugs into. If this fails we may not have VLAN routing enabled on the VLAN the client is in.
    -Ping from client to another client on same VLAN, same switch. If this fails we need to check on client settings, IP address and gateway.
    -ping from client to another client on different VLAN, same switch. If this fails we need to double check the VLAN routing commands are in place.
    -ping from client to the ip address of the next switch in the network. If this fails then check Trunk port configuration from switch to switch, ensuring the VLAN is added to the Trunk port.
    -ping from client to another client on same VLAN, different switch. If this fails, check Trunk port settings.
    -ping from client to another client on different VLAN, different switch. If this fails then check trunk settings and VLAN routing configuration.

    Derek,
    I tried to draw my prefered setup for this network configuration.
    I would create a Team with the two 1 GBit NICs and use it for Domain, DNS, Backup and any SystemCenter Agents.
    I would also Team the two 10 GBit NICs and than assign it to a Hyper-V Switch for the VMs. In Windows Server 2012 it is posible to create vNICs for the Management OS that use this Hyper-V Switch (Converged Network Design). I would create two vNICs SMB1
    and SMB2 to use them for Cluster and Livemigration traffic with SMB Multichannel. If your storage system supports SMB Multichannel you can also use both as storage NICs (but this depends wich vendor you have).
    Hope this helps.
    Grüße/Regards Carsten Rachfahl | MVP Virtual Machine | MCT | MCITP | MCSA | CCA | Husband and Papa |
    www.hyper-v-server.de | First German Gold Virtualisation Kompetenz Partner ---- If my answer is helpful please mark it as answer or press the green arrow.

  • A bridge? A switch? Another router?

    I had a internet modem connected via ethernet cable to a Linksys router (the wireless ability had been deactivated) and then I ran from the Linksys one ethernet cable to one Apple Express (N) and another ethernet cable to another Apple Express (b/g for some G3 Macs). The internet stopped working so I plugged the modem directly into the N Apple Express. I guess I need to get rid of the Linksys. What should I get to replace it so I can run the N and the B/G Apple Expresses again? A bridge? A switch? Another router?
    Thanks,
    P.Hyland

    When you plugged your Express devices into the Linksys router, did you first configure them to act as a "bridge"?. In other words, the Connection Sharing setting in AirPort Utility must be set to "Off (Bridge Mode).
    You would need to do this for both Express devices as follows:
    Open Hard Drive > Applications > Utilities > AirPort Utility
    Click Manual Setup
    Click the Internet icon at the top of the setup page
    At the bottom of the next page, look for the setting for Connection Sharing. This must be set to "Off (Bridge Mode) whenever the device is plugged into a router.
    Chances are, your Linkys is fine and the Express devices were not correctly configured to connect to the Linksys. If you connected the Expresses to your old Apple router (I'm assuming it has LAN ethernet ports as well), they will be configured the same way. So, whether you use the Linksys or the Apple, configure your Express devices as above.
    So, your network will look like this:
    Modem > Router > Express Devices > Computers can connect by wireless or they can connect by ethernet to the Router.

  • Problem finding Linksys E1000 router

    Hi all.
    I just purchased an E1000 router for my brothers computer. He has Comcast as his ISP so i was trying to set up the router and clone his IP address as per other instructions i have read online when dealing with Comcast. However i can not gain access to his router via the 192.168.1.1 address or the CD setup. They both say router not found.
    I know the cable is good because i take it directly out of the cable modem and plug it into the "internet" port of the router. I've also tried it in port 1 of the lan side and still can not get acceess. I havent tried the router on another computer yet but since his is the pc i want it to work with, i have to get it to work on that one. I've also tried restarting the pc after the cable was connected.
    Any help is appreciated.

    Press and hold the reset button on the router for 30 seconds. Release the reset button and wait for 30 seconds. Power cycle the router.
    Connect the modem to the Internet port and computer to Ethernet port 1 on the router. Open the setup page of the router.  Clone the MAC address of the main computer and save the settings. Unplug the power cable to the router and modem. First plug in the power to the modem and wait for 1 minute. Plug in the power cable to the router and wait for 1 minuter. Try to access the Internet through the router.

  • Connect Eternet Switch (for hardwired connections) AND WRT54G2 to WET610N

    Hello,
    In my main office, I have a cable modem which is connected to my main E4200 router. All of my equipment (except my Ooma) is served by the E4200. The E4200 broadcasts a wireless network.
    In my basement, I have a Wii / entertainment center. The E4200 signal from upstairs isn't strong enough to stream video.
    I bought the WET610N and have successfully set it up to interact with the E4200 wirelss network. I can hardwire my laptop to the WET610N and verify the internet works great.
    However, the Wii must connect over wireless. I have other equipment in the basement which would benefit from an internet connection. So, I want to A) connect the ESXS88W 10/100 8-port workgroup switch I have to the WET610N *AND* also broadcast a wireless signal in my basement (assuming the wireless network I see in the basement is the same "old" one from upstairs which has not benefited from the WET610N).
    How can I set up my WRT54G2 to broadcast a wireless signal in the basement so that it leverages the E4200 signal served by the WET610N, while also having the workgroup switch offer hardwired connections to my other equipment (like Dish Network receiver)? It doesn't seem to work by just plugging the WRT54G2 into the workgroup switch.
    Thanks!
    Solved!
    Go to Solution.

    if i'm correct, your setup looks like this:
    E4200 ( ( ( ) ) ) WET610N-----EZXS88W
    *wireless connection indicated by parentheses and wired connection indicatd by dashes
    if you want to connect a WRT54G2 to broadcast a wireless network in your basement, you'll have to connect this router (using port 1,2,3 or 4) to your switch. you'll have to change the WRT54G2's IP address to 192.168.1.2 so that it doesnt conflict with the E4200; then disable its DHCP server (since the E4200 is already the DHCP server).
    that should do it.

  • Setup a switch with my router.

    I have a Linksys router in which I recently bought. The model is WRT54G. I also have a switch as well. I am setting up the switch (which is a surecom) with the router. This switch does not have an uplink port, so I use a regular Cat5 cable.
    So I plug port 1 on my router, to port 1 on my switch (with a regular cable). Neither of the lights for Port 1 are lighting up. They blink on and off. I then plug my computer into port 2 of the switch and it is lit. I switch around the ports, and still the same result.
    Is there a certain way im supposed to set this up? Like on my router page (192.168.1.1)? Or am I supposed to setup my switch somehow?
    Thanks,
    Peter

    The internet connection works fine. THe router is brand new, and works perfect.
    Just I have multiple computers in my basement so I ran a cable down there with a switch. I was just wondering if I have to set anything up? I know that there MIGHT be an issue with the cable running down because I crimped it myself, and who knows how good that is, but I was just curious if I have to set anything up.

  • E1000 router

    I had a WRT54g router which I set up a point to point wireless connection to a wireless printer. I did not have a
    network set up and it worked fine.
    With the new E1000, do I have to set up a network for it to work with the wireless printer?
    Thanks in advance.

    I think you have to install the Linksys E1000 router on your computer so that you have the network in your home .
    If you are using the router only in Local network make sure you have the correct SSID and Password to connect the network on your wireless printer .
    Connect the Modem to the Internet port on your Linksys E1000 router .
    Connect the computer with the Ethernet cable to the Ethernet port on your router .
    Install the Cisco Connect Software on your computer .
    After the successful installation , Go to the Router settings and you will find the Router name (SSID) and password .
    Connect your wireless printer to that SSID using the password.
    Who is your Internet service provider ?

  • Connect to switch loopback address

    Hello,
    I have a loopback address on swich A, also switch A connects to switch B through a trunk.  Switch B has 3 SVI vlans that are routed thru eigrp.  What I want to do is connect to switch A to loopback IP address. I tried a static route but did not work can connect to loopback address.  The config for switch A is loopback address is 192.168.137.6 255.255.255.255. On swich B one switch SVI address is 192.168.136.1 255.255.255.128 and eigrp  routes 192.168.136.1 thru network 192.168.136.0.  Can I use a static route from loopback address to SVI address 192.168.136.1 I tried that did not work. I just want to configure something only on switch A to connect  to loopback address for management, any suggenstions what will work and with what switch commands?
    Thanks,

    I am not fully understanding the environment that you describe and so do not fully understand your issue. But based on what I think that I do understand it seems to me that it should be possible to configure a host specific static route on switch B that would allow you to connect to the loopback on switch A, assuming that switch A has an IP address other than the loopback which is reachable from switch B. If this does not seem to adequately address your question then please provide clarification of your question.
    HTH
    Rick

Maybe you are looking for