Cisco 2950 MT-RJ ports - Connect two switches?

Hi Everyone,
I'm wondering if I can connect two cisco 2950s together via the two MT-RJ ports they have?
Basically, I'd like the fibre ports to be the trunk between the two switches if possible
I have two of these: 
Thanks!

Hi,
Yes, that is possible. As long as your fiber patch cable is good there should be no issues.
HTH

Similar Messages

  • 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.

  • CLI support for Cisco SG100D-05 5-Port Gigabit Desktop Switch

    I would like to know if the SG100D series of switches support the CLI? If not what are the series of switches supported by the CLI.
    I am looking for an application where I need to tell which device is connected to which port on a switch. Hence I am looking at this option where I can run a script and use CLI to output the MAC id of devices connected on each port.
    Thanks!

    Hi Yiu Kay Lee,
    Thank you for sending me this document. It was very helpful. But I cannot understand one thing about it. Is it possible to extract the results from the CLI by passing a command via a script e.g. Python and get the results of it into Python?
    For e.g.
    ************Python script ******************
    >>print("send command to 200 series Cisco switch")
    >> results = show mac-addr-table
    >> print results
    Please let me know if such interfacing with the CLI is possible or not?
    Thanks

  • Can I connect two switches to a server?

    We share an office with another company but we currently have separate servers and networks.
    I'm looking into the possibility of us sharing their server.
    The thing is we both have our own switches and and I want to avoid any rewiring of the network. Will I be able to use two switches?
    It's a 2x 2.8 GHz quad core intel xeon (with dual ethernet). So is it just a matter of connecting both switches to the server and configuring them in some way?

    Hi Christiaan,
    I end up doing this quite often. You have a few options, the simplest is below...
    How many users and devices that require network connections does each company have? If it's under 254 which it sounds like it is and your happy to have the users on the same network, sharing the same ISP. Then the easiest option is going to be your company sharing their network. You'd save a bit of money on your internet connection which could be used to increase the bandwidth on the other companies line if needed.
    You would do following. Make sure all devices that need a fixed IP address such as printers/mfds'/switches/WiFI/phone system (if applicable) are changed to a fixed IP address with the relevant subnet mask, dns and gateway from the other companies network. You'd obviously need to get the relevant numbers from their IT guy.
    Then you could use your switch as extra capacity on their network by linking it with their switch. Obviously you'd want to use the fastest possible connection between the switches or look to buying something new with more ports. If you both have something like the HP 1810G ProCurve or a compatible switch you can buy two fibre transceivers and connect them with a fibre cable, this will free up more ports for users on the switch or simply connect them via an ethernet cable. On the 1800 series you can use LACP which allows you to use up to 4 ethernet ports to improve the bandwidth thus giving you a 4gigabit connection to their network. Depending on how much traffic there is going to be you might want to skip that as there might be no need.
    Then it's just a case of creating your users on their server and creating an area for your company that only you have the access rights to and creating a shared area inter-company area if you want to easily ping them over files.
    What do you both use for email? Are you going to look to share a server for it?
    Hope that helps
    Beatle

  • BT HH 4 - GigE port - connection to switch

    Anyone know how I can connect the GigE port to a switch at 1Gbps?
    I connect the HH4 GigE port to my computer and it does so at 1Gbps (according to Windows XP)
    I connect my computer to a netgear GS608 and it does so at 1Gbps (according to Netgear status lights and Windows XP)
    I connect the HH4 GigE port to the GS608 and it does so at 100Mbps!! (according to the status lights on the GS608)
    Cat 5 cable used - BT Home Hub 4 (Type A) | Software version 4.7.5.1.83.8.130.1.10 | Last updated 20/08/13

    correct about cable.
    Cat5 is not suited for Gig speeds.
    Cat5E can cope but again would be the weak link if the hardware can utilize the speeds.
    Your switch maybe picking up the inablilitly of the Cat5 cable to produce the right speeds and is auto switching down to maxamize stability. Borrow or buy a Cat6 cable and try that out
    If I've helped, just click the Star - Every little bit helps
    If you can't fix it with a hammer, you've got an electrical problem.

  • WLC5508 connected two switches

    Dear All,
    I have a WLC 5508 and a brief connected like below.
    Internet->Router->2960G A-> (Port0)  WLC5508 (Port1) -> 2960G B-> Access Points <-> wireless clients
    My Question : Is the above topology work? The access points register to the controller via 2960B, and the data traffic ffrom wireless clients go through from 2960G B to WLC port 1, and WLC pass it to port 0 itself and then go to internet?
    Thanks.
    Mic

    As long as you don't have LAG enabled that will work. You do need to specify a dynamic interface in which the Internet traffic will egress. Your management will be primary port 1 and the your dynamic interface will be primary port 2. Of course port 1 and port 2 would have to be on a different subnet.
    If you have both on the same subnet, that will not work. You would trunk the ports and only allow the vlans for that port. Port 1 connected to the switch would only allow the vlan for the management. Port 2 connected on the switch will only allow the vlan for that dynamic interface.
    Sent from Cisco Technical Support iPhone App

  • Cisco SG300-52 52-Port Gigabit Managed Switch losing VLAN-Port Membership

    Hello
    We have some cisco switches in use and we're facing some problems everytime the switch loses Power.
    After a reboot the port/vlan membership is lost, so are other settings recently made (like SSH access allowed, etc.).
    The settings made up a year ago like the IPs, password, etc. remain untouched.
    Upgrading the Firmware, Saving the Configs, etc. didn't solve the problem.
    Is this a known issue? Anyone facing the same problem?
    Bye and thanks for the help.
    Viktor

    Vlan       Name           Tagged Ports      UnTagged Ports      Created by
     1           1                              gi51-52,Po1-8           D
     10         10              gi51-52                                 S
     20         20              gi51-52                                 S
     30         30              gi51-52                                 S
     40         40              gi51-52       gi1-9,gi14-34,            S
                                              gi38-41,gi49-50
     50         50              gi51-52                                 S
    100         100             gi51-52                                 S
    190   SecurityNetwork       gi51-52        gi11-13,gi35-37          S
    200         200             gi51-52                                 S
    210      Wireless           gi51-52              gi10               S
    300   ServerSubnetOne       gi51-52            gi42-48              S
    config-file-header
    as4
    v1.4.0.88 / R800_NIK_1_4_194_194
    CLI v1.0
    set system mode switch 
    file SSD indicator encrypted
    ssd-control-start 
    ssd config 
    ssd file passphrase control unrestricted 
    no ssd file integrity control 
    ssd-control-end cb0a3fdb1f3a1af4e4430033719968c0 
    no cdp run 
    no spanning-tree
    port jumbo-frame
    vlan database
    vlan 10,20,30,40,50,100,190,200,210,300 
    exit
    voice vlan state disabled 
    voice vlan oui-table add 0001e3 Siemens_AG_phone________
    voice vlan oui-table add 00036b Cisco_phone_____________
    voice vlan oui-table add 00096e Avaya___________________
    voice vlan oui-table add 000fe2 H3C_Aolynk______________
    voice vlan oui-table add 0060b9 Philips_and_NEC_AG_phone
    voice vlan oui-table add 00d01e Pingtel_phone___________
    voice vlan oui-table add 00e075 Polycom/Veritel_phone___
    voice vlan oui-table add 00e0bb 3Com_phone______________
    no lldp run 
    hostname as4
    no passwords complexity enable 
    username cisco password encrypted xxxxx
    ip ssh server
    snmp-server location Eingang
    snmp-server contact [email protected]
    clock timezone " " +1
    clock source sntp
    sntp unicast client enable
    sntp unicast client poll
    sntp server 157.161.57.2 poll 
    ip name-server  192.168.200.1
    interface vlan 190
     name SecurityNetwork 
    interface vlan 200
     ip address 192.168.200.34 255.255.255.0 
    interface vlan 210
     name Wireless 
    interface vlan 300
     name ServerSubnetOne 
    interface gigabitethernet1
     switchport mode access 
     switchport access vlan 40 
     lldp med disable 
    interface gigabitethernet2
     switchport mode access 
     switchport access vlan 40 
     lldp med disable 
    interface gigabitethernet3
     switchport mode access 
     switchport access vlan 40 
     lldp med disable 
    interface gigabitethernet4
     switchport mode access 
     switchport access vlan 40 
     lldp med disable 
    interface gigabitethernet5
     switchport mode access 
     switchport access vlan 40 
     lldp med disable 
    interface gigabitethernet6
     spanning-tree disable 
     switchport mode access 
     switchport access vlan 40 
     lldp med disable 
    interface gigabitethernet7
     switchport mode access 
     switchport access vlan 40 
     lldp med disable 
    interface gigabitethernet8
     switchport mode access 
     switchport access vlan 40 
     lldp med disable 
    interface gigabitethernet9
     switchport mode access 
     switchport access vlan 40 
     lldp med disable 
    interface gigabitethernet10
     switchport mode access 
     switchport access vlan 210 
     lldp med disable 
    interface gigabitethernet11
     switchport mode access 
     switchport access vlan 190 
     lldp med disable 
    interface gigabitethernet12
     switchport mode access 
     switchport access vlan 190 
     lldp med disable 
    interface gigabitethernet13
     switchport mode access 
     switchport access vlan 190 
     lldp med disable 
    interface gigabitethernet14
     switchport mode access 
     switchport access vlan 40 
     lldp med disable 
    interface gigabitethernet15
     switchport mode access 
     switchport access vlan 40 
     lldp med disable 
    interface gigabitethernet16
     switchport mode access 
     switchport access vlan 40 
     lldp med disable 
    interface gigabitethernet17
     switchport mode access 
     switchport access vlan 40 
     lldp med disable 
    interface gigabitethernet18
     switchport mode access 
     switchport access vlan 40 
     lldp med disable 
    interface gigabitethernet19
     switchport mode access 
     switchport access vlan 40 
     lldp med disable 
    interface gigabitethernet20
     switchport mode access 
     switchport access vlan 40 
     lldp med disable 
    interface gigabitethernet21
     switchport mode access 
     switchport access vlan 40 
     lldp med disable 
    interface gigabitethernet22
     switchport mode access 
     switchport access vlan 40 
     lldp med disable 
    interface gigabitethernet23
     switchport mode access 
     switchport access vlan 40 
     lldp med disable 
    interface gigabitethernet24
     switchport mode access 
     switchport access vlan 40 
     lldp med disable 
    interface gigabitethernet25
     switchport mode access 
     switchport access vlan 40 
     lldp med disable 
    interface gigabitethernet26
     switchport mode access 
     switchport access vlan 40 
     lldp med disable 
    interface gigabitethernet27
     switchport mode access 
     switchport access vlan 40 
     lldp med disable 
    interface gigabitethernet28
     switchport mode access 
     switchport access vlan 40 
     lldp med disable 
    interface gigabitethernet29
     switchport mode access 
     switchport access vlan 40 
     lldp med disable 
    interface gigabitethernet30
     switchport mode access 
     switchport access vlan 40 
     lldp med disable 
    interface gigabitethernet31
     switchport mode access 
     switchport access vlan 40 
     lldp med disable 
    interface gigabitethernet32
     switchport mode access 
     switchport access vlan 40 
     lldp med disable 
    interface gigabitethernet33
     switchport mode access 
     switchport access vlan 40 
     lldp med disable 
    interface gigabitethernet34
     switchport mode access 
     switchport access vlan 40 
     lldp med disable 
    interface gigabitethernet35
     switchport mode access 
     switchport access vlan 190 
     lldp med disable 
    interface gigabitethernet36
     switchport mode access 
     switchport access vlan 190 
     lldp med disable 
    interface gigabitethernet37
     switchport mode access 
     switchport access vlan 190 
     lldp med disable 
    interface gigabitethernet38
     switchport mode access 
     switchport access vlan 40 
     lldp med disable 
    interface gigabitethernet39
     switchport mode access 
     switchport access vlan 40 
     lldp med disable 
    interface gigabitethernet40
     switchport mode access 
     switchport access vlan 40 
     lldp med disable 
    interface gigabitethernet41
     switchport mode access 
     switchport access vlan 40 
     lldp med disable 
    interface gigabitethernet42
     switchport mode access 
     switchport access vlan 300 
     lldp med disable 
    interface gigabitethernet43
     switchport mode access 
     switchport access vlan 300 
     lldp med disable 
    interface gigabitethernet44
     switchport mode access 
     switchport access vlan 300 
     lldp med disable 
    interface gigabitethernet45
     switchport mode access 
     switchport access vlan 300 
     lldp med disable 
    interface gigabitethernet46
     switchport mode access 
     switchport access vlan 300 
     lldp med disable 
    interface gigabitethernet47
     switchport mode access 
     switchport access vlan 300 
     lldp med disable 
    interface gigabitethernet48
     switchport mode access 
     switchport access vlan 300 
     lldp med disable 
    interface gigabitethernet49
     switchport mode access 
     switchport access vlan 40 
     lldp med disable 
    interface gigabitethernet50
     switchport mode access 
     switchport access vlan 40 
     lldp med disable 
    interface gigabitethernet51
     switchport trunk allowed vlan add 10,20,30,40,50,100,190,200,210,300 
     lldp med disable 
    interface gigabitethernet52
     switchport trunk allowed vlan add 10,20,30,40,50,100,190,200,210,300 
     lldp med disable 
    exit

  • Enable port security between Two switches

    Hi Everyone,
    I connected two switches together  via below config
    Switch A
    int gi0/1
    switch mode access
    switchport access vlan 10
    Switch B
    int gi0/1
    switch mode access
    switchport access vlan 10
    They work fine with above config.
    I did the Test below
    However when i changed Config of Switch B  as below
    int gi0/1
    switch mode access
    switchport access vlan 10
    switchport port-security  
    Switch B is unable to ping its default gateway.
    Also Switch B is not reachable via SSH.
    Port is up up and in STP forwarding state.
    Switch B can see Switch A as a neighbour.
    Also Switch B is not reachable via SSH.
    I know that switchport port-security we use only when connecting to PC.
    S does this mean that  on above scenario layer 1 and layer 2 are up but layers beyond 3 and above are not reachable like ping,ssh etc??
    Regards
    MAhesh

    I was just trying to see how the switches behave with this config.Nothing much just  exploring the options in the network world
    Ideally if you want to connect two switches together in Layer 2, Dot1Q trunking is the way to go.  You do not want to put port security because it is useless. 

  • Uplink ports and actual switches sfp usages (please help~~)

    Dear all,
    I am reading around to see the differences between uplink ports and normal ethernet ports. It seems to be uplink port just reverse the rx,tx pins and remove the needs of using a crossover cable.
    I have done a simple representation of using the below (normal ethernet ports)
    PC
    SWITCH
    ROUTER 
    RX
    straight
    TX
    straight
    RX
    RX
    straight
    TX
    straight
    RX
    TX
    straight
    RX
    straight
    TX
    TX
    straight
    RX
    straight
    TX
    I assumed that the SWITCH ethernet port pins are naturally arranged as opposite from the PC so that a straight cable can be used and the same applies to a router port.
    Q1) Hence from PC to Router ethernet port, I will need a cross cable, am I right ?
    ============================================================
    Then I chance upon this website http://duxcw.com/faq/network/uplink.htm which states "A PC can be connected to an uplink port with a crossover cable"
    As per my assumption above, a router has normal ethernet ports and uplink ports (for connecting to the wan/modem), since the normal ethernet ports of a router are in the order of (RX,RX,TX,TX) as shown above, I assumed the uplink port is (TX,TX,RX,RX).
    PC
    ROUTER normal ethernet port
    PC
    ROUTER uplink port
    RX
    cross
    RX
    RX
    straight
    TX
    RX
    cross
    RX
    RX
    straight
    TX
    TX
    cross
    TX
    TX
    straight
    RX
    TX
    cross
    TX
    TX
    straight
    RX
    Q2) So how can the PC connect to the Router's Uplink port using a crossover cable ? Shouldn't it be using straight cable instead if it is trying to connect to a router's uplink port ?
    ============================================================
    Q3) Where connecting switches (switch 1 to swtich2) using uplink port, can I say that a straight cable will be connected to switch 1 uplink port on 1 end, and a normal ethernet port in switch 2 on another end ?
    SWITCH#1 ethernet port
    SWITCH#1 Uplink port
    SWITCH#2 ethernet port
    TX
    RX
    straight
    TX
    TX
    RX
    straight
    TX
    RX
    TX
    straight
    RX
    RX
    TX
    straight
    RX
    ============================================================
    Q4) What is the purpose of an SFP port in a switch ? is it use as an uplink port ? Where does it actually uplink/connect to ?
    Q5) If i connect a switch Uplink port to another switch Uplink port, does it means that I have to use a crossover cable ? does SFP fiber come with "crossover" type too ?
    ============================================================
    Q6) If an uplink port in a switch is use to connect to a router (can we?), do i need to use a crossover cable then ? since a normal switch ethernet port will use a straight cable to connect to a router port ? as shown below
    SWITCH
    ROUTER 
    SWITCH UPLINK
    ROUTER 
    TX
    straight
    RX
    RX
    cross
    RX
    TX
    straight
    RX
    RX
    cross
    RX
    RX
    straight
    TX
    TX
    cross
    TX
    RX
    straight
    TX
    TX
    cross
    TX
    ============================================================
    Q7) Last but not least, if a design connect two switches using SFP uplink ports on both side, what would be the main purpose ? to increase the amount of ports ?  Why not stack them then ?
    Sorry for the lengthy post, will really appreciate if some gurus can shed some light on the above.
    Thanks a million.
    Regards,
    Noob

    An uplink port doesn't necessarily run at wire speed but it is more likely to.
    But this doesn't mean you don't get oversubscription from the switch to other switches.
    It's quite a big subject to cover but i'll try and keep it brief.
    Internally within a switch there is a crossbar switch fabric which I think we covered before. Think of it of as pathways between ports. On any switch there are a number of ports that are capable of certain speeds.
    Put simply if you take the number of ports on the switch and multiply that by the fastest speed the ports can operate at, if that number is greater than the switch fabric then the switch is said to be oversubscribed.
    It doesn't mean in practice it will be oversubscribed but the potential is there.
    What can happen though with oversubscribed switches is that the uplinks ports are guaranteed not to be oversubscribed ie. they do not need to contend with the other ports on the switch. It's complicated but it is to do with the connectors per port group etc. to the switch fabric.
    But even though the uplinks ports can run at wire speed so they are not oversubscribed, if they are uplinks to other switches there may very well be more traffic combined from the other ports on the switch to that uplink port so you still get an oversubscription ratio.
    But what would make it a whole lot worse was if your uplink port was oversubscribed within the switch as well.
    So there is oversubscription within the switch and this is where we talk about ports running at wire speed or not and then there is oversubscription between different layers of the network eg. access to distribution for example.
    Jon

  • Connecting Two Power Supplies in one PC

    Hello there  :hypecrite:
    Will someone help me on how to connect two Switching P/S in one PC (If it's possible)?
    I tried using two P/S in my old PC and it's working just fine. However, the problem is that I cannot switch them on simultaneously because the one is connected directly to the motherboard and the other, I just used a simple switch to turn it on.
    Also, please check my P/S for this PC if it's OK.
    Thank you and more POWER!!!
     :hypecrite:

    Hello again :hypecrite:
    Thank you for your support guyz.  I would like to tell you that you are all correct.
    I think it's time for me to stop fooling aroung, experimenting things, too.  And to trust the verdors instead.  I looked for the psu brands that you all mentioned and it turned out my pockets could still handle such a cost, eventhough it costs twice as much as the psu that I have right now, but as long as it's dependable.
    And about the problem with my CPU's temperature that I posted last November 12, 2004 (MSI KT4A-V with S/PDIF out and Core center), AMD support center finally replied to me and told me that my temp is OK but not to go above 70C.
    Below is my inquiry to AMD and their reply:
    My inquiry:
    Dear Sir:
       I would like to ask what is the NORMAL operating temperature of Athlon XP 2400+ FSB 266 model 8?  
       When my PC is at idle, my CPU temp reading is 60C and during full load, it reaches to about 66C. It doesn't have any problems though (such as random reboot) but I'm a bit concerned of the temperature reading.  Some people say that it's a bit TOO HOT  for comfort. Still others say that it is OK.  What do you think?
      I have read your post on MAXIMUM operating temperatures of Athlon XPs but not the recommended NORMAL operating temperatures.
      And also when I turn  the BIOS CPU core voltage to AUTO mode the default is 1.575V. My friends said the minimal operating voltage of 2400+ is 1.650V. Is it OK to just leave it to default?
    Thank you very much
    Sincerely,
    Mark E. Guillem
    Philippines
    My PC Specifications:
    AMD Athlon XP 2400+ (Family 6, Model 8, Stepping 1), FSB266 256L2
    GlobalWin TAK68 CPU fan (dual fan, ball bearing 5200RPM max each)
    MSI KT4A-V (VIA KT400 chipset) BIOS ver. 2.3 date: 09092004 (with MSI Core Center)
    512MB DDR333 mem (2x256MB)
    Inno3D GeForce FX 5200 128MB with AGP8x w/ TV out
    80GB Maxtor 7200RPM 1x133
    40GB Seagate 5400RPM 1x100
    LiteON LDW 411S DVDRW 40x12x40
    LITE-ON XJ-HD166S DVDROM 16x
    Pinnacle PCI PCTV Rave TV tuner/capture card
    OS: Windows XP SP2
    The Reply:
    Dear Guillem,
    Thank you for contacting Asian and Pacific AMD Technical Support Centre.
    I can confirm that the temperatures ranges from 40° - 55° C  in moderate usage and with a higher workload around 65° C, but never over 70° C.
    What the correct voltage is concerned there are three models of the Athlon XP 2400+. If you have the CPU with the OPN AXDA2400DUV3C the
    voltage should be 1.60V otherwise it is 1.65V.
    It seems your system would overheat dangerously when set to the right voltage. I would suggest, you do check if the heatsink /fan is installed
    properly.
    You may find a different reading after upgrading your BIOS.
    * Please make sure to download the right BIOS version for your motherboard.
    Then, please, make sure that your processor Athlon XP 2400+ is configured in BIOS as follows:
    -          FSB speed to 133MHz (It is a bidirecctional bus, the full speed would be 266)
    -          CPU multiplier of 15x
    -          CPU voltage of 1.65V (1.60V if OPN = AXDA2400DUV3C)
    With these settings the clock frequency of the processor should be 2000 MHz.
    And finally you can test the CPU on another system to establish if the processor or the motherboard is responsible for the problem . If no other system is
    available to you then ask your retailer/reseller to test it for you.
    Given the case that the processor is faulty, we inform you that the PIB processors (box processors) have 3 years warranty, whilst OEM processors (tray processors) have only one year. In both cases the first year is given by the reseller and the PIB processors second and third years are served directly by AMD.
    If you have any further questions, please, do not hesitate to contact us again.
    Kind regards,
    Roberto Erler
    Technical Support Engineer
    Spain: 900 99 71 21 (Número Gratuito)
    France: 0800 908 621 (Numéro Vert)
    Germany: +49 89 450 53199
    Italy: 800 877 224
    United Kingdom: +44 1276 803 299
    Yesterday, I increased the CPU voltage to 1.60V (from the default of 1.575) and my temp reading was reduced to 50C at idle (from an idle of 60C) and at full load to 60C (from a full load of 66C).  I was not expecting this though.  I was expecting that my CPU's temp will increase further.  But this is what happened. I guess the RIGHT THING should be the RIGHT THING.
    Tomorrow, I will buy a new psu with the brands that you mentioned and I hope that my PC's stability and performance will increase further.
    Again thank you very much for your support and all.
      :hypecrite:

  • Connecting two Cisco 2950 switches to a 2600 router

    Hello,
    I'm trying to have two LANs connected to 2950 switch each, connect to a 2600 router and have the two LANs communicate with each other...i can't seem to get it working...any help...thanks
    LAN 1 192.168.10.1/20
    LAN 2 192.168.12.1/21
    Thanks again

    Alright, these are only basic configs here:
    Router
    hostname Router
    int fastethernet0/0
    description Network 1
    ipaddress 192.168.10.65 255.255.255.192
    int fastethernet0/1
    description Network 2
    ip address 192.168.10.129 255.255.255.192
    end
    Switch 1 (the one connecting to f0/0)
    hostname SwitchNet1
    int f0/1
    description Host 1 Net 1
    no ip address
    no shut
    int f0/2
    description Host 2 Net 1
    no ip address
    no shut
    int f0/3
    description Host 3 Net 1
    no ip address
    no shut
    int f0/4
    description Host 4 Net 1
    no ip address
    no shut
    int range f0/5 - 23
    no description
    no ip address
    shut
    int f0/24
    description UPLINK to Router
    no ip address
    no shut
    int vlan 1
    ip address 192.168.10.66 255.255.255.192
    no shut
    default-gateway 192.168.10.1
    end
    Switch 2 (the one connecting to f0/1)
    hostname SwitchNet2
    int f0/1
    description Host 1 Net 2
    no ip address
    no shut
    int f0/2
    description Host 2 Net 2
    no ip address
    no shut
    int f0/3
    description Host 3 Net 2
    no ip address
    no shut
    int f0/4
    description Host 4 Net 2
    no ip address
    no shut
    int range f0/5 - 23
    no description
    no ip address
    shut
    int f0/24
    description UPLINK to Router
    no ip address
    no shut
    int vlan 1
    ip address 192.168.10.130 255.255.255.192
    no shut
    default-gateway 192.168.10.129
    end
    This config assumes only ports f0/1 - f0/4 will be used on each switch. If that is not the case, you will need to modify the interface configs accordingly. You may want to use descriptions more suited than to your network on the switchports. Also, this config assumes the router is connected to port f0/24 on each switch as well.
    The default-gateway for the hosts and the switches is going to be the router IP address for the subnet they are attached to. The hosts/switches attached to f0/0 use 192.168.10.65 as their gateway. The hosts/switches attached to f0/1 use 192.168.10.129 as their gateway.
    You do not need to configure a port on the switch as the default-gateway. The default-gateway is an IP address the host/switch uses to direct all traffic from itself out past the router. In fact, if you don't need the switch to talk to devices on the other subnet, you don't even need to configure a default-gateway on the switches (but I would anyway).

  • Connecting two cisco ESW 500 series switches.

    Hi Experts,
    I have a basic knowledge of network and need some help.
    I have two cisco ESW 500 series switches and i want to connect them together.
    Q1 # Which type of cable i should use to connect these two switches CrossOver or fiber...What is the advantage of using Fiber over CrossOver. ?
    Q2 # What are the marked ports in the image used for...???

    tech spec,
    Traditionally you would use crossover to connect switches. Most modern network devices have Auto-MDIX which allows the device to connect using either crossover or straight through.
    The ports on the right can be used for uplink or as regular network ports. On the 10/100 versions the ports on the right are usually Gigabit, thus making them more suitable for uplink to another switch, etc.
    Please mark this thread as answered or reply if you have any additional questions.
    - Marty

  • Best way to connect 2 Cisco 3750 PoE 24-port Switches

    Hello. I have 2 Cisco 3750 PoE 24-port switches in a small office environment. Right now I have a trunk configured off my ASA 5505 to switch 1, and then just an access port configured on a port (switch 1) and an access port configured on a port (switch 2) to connect them together. These switches also have 2 GB SFP ports but they are not being used in this configuration.
    I was curious to know if anyone had any better recommend configurations for connecting these 2 switches together? I'm not sure if this particular model can be stacked? 

    What are the exact model numbers (should be written on a sticker)?
    You will know if they can be stacked as you will see the 2x stack ports on the back of each switch :)
    If they can then that is probably the way to go unless you want to keep them as separate switches for some reason.
    If you want them separate, I would connect them via a Trunk link at least so you can have the same Vlans on both.
    Thanks

  • Cisco 2950 - 3350 Trunking issue - Port not lighting up

    Hi There,
    I have two switches I am trying to connect a 2950 and a 3350. I have a crossover cable connecting them from fa0/24 to fa0/24 setup as a trunk,
    however they won't connect and the port on both switches is down, (e.g no port light coming on on switch)
    here is some show commands from both switches.. does anyone know where I am going wrong.. thanks in advance
    2950#sh ip int brief
    Interface                  IP-Address      OK? Method Status                Protocol
    Vlan1                      192.168.0.11    YES NVRAM  up                    up
    FastEthernet0/1            unassigned      YES unset  up                    up
    FastEthernet0/2            unassigned      YES unset  down                  down
    FastEthernet0/3            unassigned      YES unset  down                  down
    FastEthernet0/4            unassigned      YES unset  down                  down
    FastEthernet0/24           unassigned      YES unset  down                  down
    2950#sh vlan
    VLAN Name                             Status    Ports
    1    default                          active    Fa0/2, Fa0/3, Fa0/4, Fa0/5, Fa0/6, Fa0/7, Fa0/8, Fa0/9, Fa0/10, Fa0/11, Fa0/12, Fa0/13, Fa0/14, Fa0/15, Fa0/16, Fa0/17, Fa0/18, Fa0/19, Fa0/20
                                                    Fa0/21, Fa0/22, Fa0/23, Fa0/24
    1002 fddi-default                     act/unsup
    1003 token-ring-default               act/unsup
    1004 fddinet-default                  act/unsup
    1005 trnet-default                    act/unsup
    VLAN Type  SAID       MTU   Parent RingNo BridgeNo Stp  BrdgMode Trans1 Trans2
    1    enet  100001     1500  -      -      -        -    -        0      0
    1002 fddi  101002     1500  -      -      -        -    -        0      0
    1003 tr    101003     1500  -      -      -        -    -        0      0
    1004 fdnet 101004     1500  -      -      -        ieee -        0      0
    1005 trnet 101005     1500  -      -      -        ibm  -        0      0
    Remote SPAN VLANs
    Primary Secondary Type              Ports
    2950#sh run
    Building configuration...
    Current configuration : 1278 bytes
    version 12.1
    no service pad
    service timestamps debug uptime
    service timestamps log uptime
    no service password-encryption
    hostname 2950
    enable secret 5 $1$JKXw$gcYpfOaSQRiQqcCuVF5371
    ip subnet-zero
    ip ssh time-out 120
    ip ssh authentication-retries 3
    spanning-tree mode pvst
    no spanning-tree optimize bpdu transmission
    spanning-tree extend system-id
    interface FastEthernet0/1
    interface FastEthernet0/2
    interface FastEthernet0/3
    switchport mode access
    interface FastEthernet0/4
    interface FastEthernet0/24
    switchport mode access
    speed 100
    duplex full
    interface Vlan1
    ip address 192.168.0.11 255.255.255.0
    ip http server
    line con 0
    line vty 0 4
    password cisco
    login
    line vty 5 15
    login
    end
    2950#
    3350#sh vlan
    VLAN Name                             Status    Ports
    1    default                          active    Fa0/1, Fa0/3, Fa0/4, Fa0/5, Fa0/6, Fa0/7, Fa0/8, Fa0/9, Fa0/10, Fa0/11, Fa0/12, Fa0/13, Fa0/14, Fa0/15, Fa0/16, Fa0/17, Fa0/18, Fa0/19, Fa0/20
                                                    Fa0/21, Fa0/22, Fa0/23, Fa0/24, Gi0/1, Gi0/2
    1002 fddi-default                     active
    1003 token-ring-default               active
    1004 fddinet-default                  active
    1005 trnet-default                    active
    VLAN Type  SAID       MTU   Parent RingNo BridgeNo Stp  BrdgMode Trans1 Trans2
    1    enet  100001     1500  -      -      -        -    -        0      0
    1002 fddi  101002     1500  -      -      -        -    -        0      0
    1003 tr    101003     1500  -      -      -        -    -        0      0
    1004 fdnet 101004     1500  -      -      -        ieee -        0      0
    1005 trnet 101005     1500  -      -      -        ibm  -        0      0
    Remote SPAN VLANs
    Primary Secondary Type              Ports
    3350#sh ip int brief
    Interface                  IP-Address      OK? Method Status                Protocol
    Vlan1                      192.168.0.12    YES NVRAM  up                    up
    Vlan200                    unassigned      YES NVRAM  down                  down
    FastEthernet0/1            unassigned      YES unset  down                  down
    FastEthernet0/2            unassigned      YES unset  up                    up
    FastEthernet0/3            unassigned      YES unset  down                  down
    FastEthernet0/24           unassigned      YES unset  down                  down
    GigabitEthernet0/1         unassigned      YES unset  down                  down
    GigabitEthernet0/2         unassigned      YES unset  down                  down
    3350#sh run
    Building configuration...
    Current configuration : 1728 bytes
    version 12.1
    no service pad
    service timestamps debug uptime
    service timestamps log uptime
    no service password-encryption
    hostname 3350
    enable secret 5 $1$ojzz$X.gjyIj/4JDGAUDXYP5ie1
    ip subnet-zero
    ip routing
    spanning-tree mode pvst
    spanning-tree extend system-id
    interface FastEthernet0/1
    no ip address
    interface FastEthernet0/2
    no ip address
    interface FastEthernet0/3
    switchport mode access
    no ip address
    interface FastEthernet0/24
    switchport trunk encapsulation dot1q
    switchport mode trunk
    no ip address
    duplex full
    speed 100
    interface GigabitEthernet0/1
    no ip address
    interface GigabitEthernet0/2
    no ip address
    interface Vlan1
    ip address 192.168.0.12 255.255.255.0
    interface Vlan200
    no ip address
    ip classless
    ip http server
    line con 0
    line vty 0 4
    password cisco
    login
    line vty 5 15
    login
    end
    3350#

    Hi  Karthick,
    I had a look under the interface however I don't appear to have any command for mdix-auto?
    2950(config-if)#?
    Interface configuration commands:
      arp                 Set arp type (arpa, probe, snap) or timeout
      bandwidth           Set bandwidth informational parameter
      carrier-delay       Specify delay for interface transitions
      cdp                 CDP interface subcommands
      channel-group       Etherchannel/port bundling configuration
      channel-protocol    Select the channel protocol (LACP, PAgP)
      default             Set a command to its defaults
      delay               Specify interface throughput delay
      description         Interface specific description
      dot1x               Interface Config Commands for 802.1x
      down-when-looped    Force looped interface down
      duplex              Configure duplex operation.
      exit                Exit from interface configuration mode
      fair-queue          Enable Fair Queuing on an Interface
      help                Description of the interactive help system
      hold-queue          Set hold queue depth
      ip                  Interface Internet Protocol config commands
      keepalive           Enable keepalive
      lacp                LACP interface subcommands
      load-interval       Specify interval for load calculation for an interface
      logging             Configure logging for interface
      mac-address         Manually set interface MAC address
      macro               Command macro
      mls                 mls interface commands
      mvr                 MVR per port configuration
      no                  Negate a command or set its defaults
      pagp                PAgP interface subcommands
      random-detect       Enable Weighted Random Early Detection (WRED) on an
                          Interface
      rmon                Configure Remote Monitoring on an interface
      shutdown            Shutdown the selected interface
      snmp                Modify SNMP interface parameters
      spanning-tree       Spanning Tree Subsystem
      speed               Configure speed operation.
      storm-control       storm configuration
      switchport          Set switching mode characteristics
      timeout             Define timeout values for this interface
      transmit-interface  Assign a transmit interface to a receive-only interface
      tx-ring-limit       Configure PA level transmit ring limit
      udld                Configure UDLD enabled or disabled and ignore global UDLD
                          setting
    2950(config-if)#

  • Cisco 2950 - 24 WS switch express install issue

    Hi Guys,
    Got a Cisco 2950 24 port switch that I need to setup and I can't seem to get the page for Express install
    In firefox when trying to connect to 10.0.0.1 I get the message "connection was reset" in internet explorer "page cannot be displayed"
    when doing a arp -a I can see that the switch does get the IP address 10.0.0.1 and I can also ping the switch ok.
    Have followed the instructions and reset the switch and all the mode lights are green etc.
    my ethernet adapter does get the address 10.0.0.2 given from the switch (however connectivity is limited / not sure if this is supposed to be like this or not)
    have tried earlier versions of firefox (even 1x 2x 3x 4x) etc and also older versions of IE incase there is something weird going on there. have also tried using a mac and trying safari which gives similar results.
    So i think the http server is enabled on the switch, as it should be by default when it is reset etc. according to cisco's documentation.
    I know using the console cable would be alot easier however I don't have one available and not easy for me to get
    any ideas? has anyone ever successfully been able to use this express install  web page on a cisco 2950 before? It has Version 12.1(22)EA14 so express install should work on this switch!
    cheers,

    managed to get hold of a console cable. checked switch and http-server command was enabled so have no idea why this feature was not working...
    did some research and someone suggested that it is fussy with the version of java you are running on the pc ( requires old version of java?) .. possibly that may have an influence who knows?
    Think ill just carry around a Console cable in future!

Maybe you are looking for

  • Need help in forms and reports

    I am new to forms and reports .. when i am trying to connect database using forms builder its giving followin error; ora-12170--TNS CONNECT TIME OUT OCCURED. Can any one tell what might be the reason?

  • I've been using PScc for 2 months and suddenly when I open a file in camera raw and attempt to use the

    radial, graduated and adjustment filters those and all the other options which do work  are immediately  "greyed out" and I've got to restart the computer to get rid. Assistance would be greatly appreciated.  Win 8.1 64 bit

  • Ichat can't see buddy

    i'm confused, i used to use ichat to video chat with friends regularly and for some reason recently cannot see the person i am chatting with when i attempt a video chat.  the other user can see/hear me, but i can't see/hear them.  help!

  • Upgrading iTunes...

    I had just opened iTunes when the message came up to upgrade it, so I did. Then, the next day (today), I tried to open it, when I got "iTunes cannot run because some of its required files are missing. Please reinstall iTunes." So I went to Add/Remove

  • Aperture 3 and iPhoto slideshows

    Still looking for someone who can tell me whether they've been a able to transfer their slideshows from iPhoto (08/09) to Aperture. Jay