Unable to login to SG200-26

[michaeldedulle]

Hi,

I recently aquired a SG200 26, as a NOOB(be warned) I'm trying to login to the router.

As for the moment I've connected the router to my laptop and try to acces it using this adress: 192.168.1.254 with timeout as a result.

I've tried to reset the switch several times, pushing +30sec on the reset button with noting connected to the switch. All led's light up suggesting that the switch has reset.

The status led is blinking fast but did so before the reset, however surfing to https://192.168.1.254 doesn't yield any succes nor displays the login page. Trying to ping gives me the 100% packages loss.

The previous owner removed it from a working setup before selling it to me, he has no idea how the or any switch work or how to acces GUI, let alone know the password.

Any help on the matter would be greatly appreciated. I believe it is some simple trick to acces the GUI, but I'm missing it. Searching the manual, google or yt doesn't help either.

[Flavio Miranda]

Hi

 Factory reset should help but is not, then I recommend a console cable and a cli terminal like putty. This way you can see what´s wrong.

[Richard Burts]

I believe that this switch, when new, does come with a default IP address configured. But this switch is not new. It was in a working setup. So it is reasonable to assume that they deleted the working/production config. But that does not provide a default IP address to use. I agree that a console connection to access the switch and to configure an IP address will be needed.

[michaeldedulle]

You are correct Richard, in factory mode normaly the login should be accesable thru this adres.

 After resetting the switch the adres should return to this I believe...

[michaeldedulle]

This model doesn't have a console port, as this is a common approach to access switches, but sadly this one doesn't have one.

Accessing thru the SFP ports is the same I presume, Ican't test it as I don't have a SFP connection on any of my devices.

The SFP port is internally linked thru port 25 and 26.

[Richard Burts]

It does sound like your attempt to reset may have been successful. I do not have much experience with this model and was not aware that it does not have a console port. Obviously our suggestions about console access were not helpful. Sorry for that. I do have a few suggestions or questions:

- is it possible that it makes a difference what port you connect the PC to? Try several different ports.

- Is is possible that it has an IP but is not the one that you expect? Can you try a ping to 192.168.1.255 and see if you get a response from some other address?

- Do you have any other network equipment (router or switch)? If so you could try connecting the new switch to the other network equipment, turn on debug for arp on the network equipment, power up the new switch, and look for any arp activity (as the new switch initializes it should arp for its own address). Or if you do not have other network equipment then connect your PC to the new switch, run wireshark (or any other packet capture software that you might have) and look for traffic from the new switch.

[michaeldedulle]

No need for apologies, I greatly appreciate any help from you or the community!

-Trying different ports didn't help, I get timeout every time.

-Completed it using 192.168.1.255 and /254

-did some research about ARP, but here my limited understanding of network comes in to play

-running wireshark, I'm able to see traffic, and a lot of:

     Cisco_fc:d0:f4  spanning - tree - ( for-bridges )_00   googling this reveals limited (comprehensible) info

So it seems the switch is a life and trying to do its thing, I believe we are getting somewhere

I've plugged in to a new port, with wireshark capturing:

No. Time Source Destination Protocol Length Info
1 0.000000 fe80::4934:3bdd:5897:6a8b ff02::1:2 DHCPv6 159 Solicit XID: 0x121976 CID: 00010001276bc22930e17123f1fe
2 0.034092 169.254.106.139 224.0.0.22 IGMPv3 54 Membership Report / Join group 239.255.102.18 for any sources
3 0.036534 169.254.106.139 239.255.102.18 UDP 207 62840 → 50001 Len=165
4 0.038881 169.254.106.139 239.255.102.18 UDP 207 62841 → 50002 Len=165
5 0.041111 169.254.106.139 239.255.102.18 UDP 207 62842 → 50003 Len=165
6 0.206354 HewlettP_23:f1:fe Broadcast ARP 42 Who has 169.254.106.139? (ARP Probe)
7 0.206703 169.254.106.139 224.0.0.22 IGMPv3 54 Membership Report / Join group 239.255.102.18 for any sources
8 0.207344 :: ff02::1:ff97:6a8b ICMPv6 78 Neighbor Solicitation for fe80::4934:3bdd:5897:6a8b
9 0.207661 fe80::4934:3bdd:5897:6a8b ff02::2 ICMPv6 62 Router Solicitation
10 0.207978 fe80::4934:3bdd:5897:6a8b ff02::16 ICMPv6 90 Multicast Listener Report Message v2
11 0.639127 Cisco_fc:d0:4c CDP/VTP/DTP/PAgP/UDLD CDP 213 Device ID: a0554ffcd03c Port ID: gi16
12 0.707980 fe80::4934:3bdd:5897:6a8b ff02::16 ICMPv6 90 Multicast Listener Report Message v2
13 0.938639 Cisco_fc:d0:4c Spanning-tree-(for-bridges)_00 STP 60 RST. Root = 32768/0/a0:55:4f:fc:d0:3c Cost = 0 Port = 0x8040
14 0.979983 0.0.0.0 255.255.255.255 DHCP 346 DHCP Discover - Transaction ID 0xb92f7aa8
15 0.994659 fe80::4934:3bdd:5897:6a8b ff02::1:2 DHCPv6 159 Solicit XID: 0x121976 CID: 00010001276bc22930e17123f1fe
16 1.053947 169.254.106.139 239.255.102.18 UDP 207 62843 → 50001 Len=165
17 1.058845 169.254.106.139 239.255.102.18 UDP 207 62844 → 50002 Len=165
18 1.063043 169.254.106.139 239.255.102.18 UDP 207 62845 → 50003 Len=165
19 1.208734 HewlettP_23:f1:fe Broadcast ARP 42 Who has 169.254.106.139? (ARP Probe)
20 1.208880 fe80::4934:3bdd:5897:6a8b ff02::1 ICMPv6 86 Neighbor Advertisement fe80::4934:3bdd:5897:6a8b (ovr) is at 30:e1:71:23:f1:fe
21 1.219300 fe80::4934:3bdd:5897:6a8b ff02::16 ICMPv6 110 Multicast Listener Report Message v2
22 1.219503 169.254.106.139 224.0.0.22 IGMPv3 54 Membership Report / Join group 224.0.0.251 for any sources
23 1.219636 169.254.106.139 224.0.0.22 IGMPv3 54 Membership Report / Join group 224.0.0.252 for any sources
24 1.221814 169.254.106.139 224.0.0.251 MDNS 83 Standard query 0x0000 ANY LAPTOP-HP-Michael.local, "QM" question
25 1.222524 fe80::4934:3bdd:5897:6a8b ff02::fb MDNS 103 Standard query 0x0000 ANY LAPTOP-HP-Michael.local, "QM" question
26 1.223962 fe80::4934:3bdd:5897:6a8b ff02::fb MDNS 141 Standard query response 0x0000 AAAA fe80::4934:3bdd:5897:6a8b A 169.254.106.139
27 1.224411 169.254.106.139 224.0.0.251 MDNS 121 Standard query response 0x0000 AAAA fe80::4934:3bdd:5897:6a8b A 169.254.106.139
28 1.231610 fe80::4934:3bdd:5897:6a8b ff02::16 ICMPv6 90 Multicast Listener Report Message v2
29 1.232160 169.254.106.139 224.0.0.22 IGMPv3 54 Membership Report / Join group 239.255.255.250 for any sources
30 1.638350 Cisco_fc:d0:4c CDP/VTP/DTP/PAgP/UDLD CDP 213 Device ID: a0554ffcd03c Port ID: gi16
31 1.709909 169.254.106.139 224.0.0.22 IGMPv3 70 Membership Report / Join group 224.0.0.251 for any sources / Join group 224.0.0.252 for any sources / Join group 239.255.255.250 for any sources
32 1.710675 fe80::4934:3bdd:5897:6a8b ff02::16 ICMPv6 130 Multicast Listener Report Message v2
33 2.070094 169.254.106.139 239.255.102.18 UDP 207 60890 → 50001 Len=165
34 2.071417 169.254.106.139 239.255.102.18 UDP 207 60891 → 50002 Len=165
35 2.072683 169.254.106.139 239.255.102.18 UDP 207 60892 → 50003 Len=165
36 2.211898 HewlettP_23:f1:fe Broadcast ARP 42 Who has 169.254.106.139? (ARP Probe)
37 2.638343 Cisco_fc:d0:4c CDP/VTP/DTP/PAgP/UDLD CDP 213 Device ID: a0554ffcd03c Port ID: gi16
38 2.938518 Cisco_fc:d0:4c Spanning-tree-(for-bridges)_00 STP 60 RST. Root = 32768/0/a0:55:4f:fc:d0:3c Cost = 0 Port = 0x8040
39 3.000227 fe80::4934:3bdd:5897:6a8b ff02::1:2 DHCPv6 159 Solicit XID: 0x121976 CID: 00010001276bc22930e17123f1fe
40 3.093534 169.254.106.139 239.255.102.18 UDP 207 60893 → 50001 Len=165
41 3.101557 169.254.106.139 239.255.102.18 UDP 207 60894 → 50002 Len=165
42 3.108079 169.254.106.139 239.255.102.18 UDP 207 60895 → 50003 Len=165
43 3.200571 HewlettP_23:f1:fe Broadcast ARP 42 ARP Announcement for 169.254.106.139
44 3.205028 fe80::4934:3bdd:5897:6a8b ff02::16 ICMPv6 90 Multicast Listener Report Message v2
45 3.205241 169.254.106.139 224.0.0.22 IGMPv3 54 Membership Report / Leave group 224.0.0.251
46 3.206883 fe80::4934:3bdd:5897:6a8b ff02::16 ICMPv6 90 Multicast Listener Report Message v2
47 3.207082 169.254.106.139 224.0.0.22 IGMPv3 54 Membership Report / Leave group 224.0.0.252
48 3.216290 fe80::4934:3bdd:5897:6a8b ff02::16 ICMPv6 90 Multicast Listener Report Message v2
49 3.216304 fe80::4934:3bdd:5897:6a8b ff02::16 ICMPv6 90 Multicast Listener Report Message v2
50 3.216683 169.254.106.139 224.0.0.22 IGMPv3 54 Membership Report / Join group 224.0.0.252 for any sources
51 3.216831 169.254.106.139 224.0.0.22 IGMPv3 54 Membership Report / Join group 224.0.0.251 for any sources
52 3.220328 169.254.106.139 224.0.0.251 MDNS 83 Standard query 0x0000 ANY LAPTOP-HP-Michael.local, "QM" question
53 3.221473 fe80::4934:3bdd:5897:6a8b ff02::fb MDNS 103 Standard query 0x0000 ANY LAPTOP-HP-Michael.local, "QM" question
54 3.228965 fe80::4934:3bdd:5897:6a8b ff02::fb MDNS 141 Standard query response 0x0000 AAAA fe80::4934:3bdd:5897:6a8b A 169.254.106.139
55 3.229603 169.254.106.139 224.0.0.251 MDNS 121 Standard query response 0x0000 AAAA fe80::4934:3bdd:5897:6a8b A 169.254.106.139
56 3.286850 169.254.106.139 169.254.255.255 NBNS 110 Registration NB LAPTOP-HP-MICHA<20>
57 3.287083 169.254.106.139 169.254.255.255 NBNS 110 Registration NB WORKGROUP<00>
58 3.287201 169.254.106.139 169.254.255.255 NBNS 110 Registration NB LAPTOP-HP-MICHA<00>
59 3.703207 169.254.106.139 224.0.0.22 IGMPv3 62 Membership Report / Join group 224.0.0.252 for any sources / Join group 224.0.0.251 for any sources

[Richard Burts]

Here are a few follow up things:

- it does look like the switch is running, especially seeing spanning tree frames and CDP frames which are generated by the switch.

- when you did the ping to 192.168.1.255 did you then check the arp table on your PC and see if there were any entries that you did not expect? 

- when you were running wireshark was the switch powered down, wireshark started, and switch powered up? Or when wireshark was started was the switch already running?

- can you take a closer look at lines 11, 30, and 37? These are CDP and almost certainly generated by your switch. Sometimes in CDP messages there is information about the device that generated the frame.

[Richard Burts]

In looking at the output another thought occurs to me. There is a lot of traffic from IP 169.254.106.139 which suggests that your computer is set up to use DHCP to get an IP address and that it did not get an IP address from DHCP and so is using this address. Manually configure the computer for an address in the subnet and test again.

[michaeldedulle]

Your are again correct my network adapter is set to DHCP (yellow).

To set a static IP, win 10 doesn't allow it ( probably because I do not know what I'm doing) so once again I took a screen shot:

The red description is dutch, translated: Can't save IP-settings. Check one or more settings and try again.

I believe the gateway is wrong, as there is no dhcp server on the network (lan network: laptop <=> switch)

Trying 192.168.1.255 and 254 for gateway gives the same result.

Leaving all fields empty except for static ip 192.168.1.10 gives me also the same result something is wrong and win 10 doesn't allow it.

[Richard Burts · Accepted solution]

We are certainly making progress. The output from wireshark does confirm that the switch is using IP 192.168.1.254. So that is one question resolved. I believe that the issue preventing you from saving the IP setting is not having any DNS configured. If you have any DNS server in your network then use that IP or use 8.8.8.8 for DNS. Also in the IP settings you need to change the Gateway from 192.168.1.1 to 192.168.1.254 (the address of the switch). Try that and see if it will then let you save the IP settings.

[michaeldedulle]

Many thanks Richard to bear with me. Using your suggested settings AND cmd running as ADMIN I was able to alter my(laptop) IP adress, now I'm able to enter the GUI.

I believe it was Win10 not allowing me to alter my IP from DHCP to static in combination with poor settings.

As I surf all the settings of the GUI, it becomes clear I do not understand a lot of them,

maybe somebody could suggest a good tutorial or a free course?

[Richard Burts]

This has been an interesting discussion. Originally we focused on it being some issue with the switch. It was unexpected that the issue turned out to be with the laptop. Glad that you now have it working. Thank you for marking this question as solved. This will help other participants in the community to identify discussions which have helpful information. This community is an excellent place to ask questions and to learn about networking. I hope to see you continue to be active in the community.

[michaeldedulle]

when you did the ping to 192.168.1.255 did you then check the arp table on your PC and see if there were any entries that you did not expect?

Apologies but I can't determine if these entries are to be expected, I took a screenshot

- when you were running wireshark was the switch powered down, wireshark started, and switch powered up? Or when wireshark was started was the switch already running?

The switch was running for more then 5min, started the capturing and then plugged in the the cable

- can you take a closer look at lines 11, 30, and 37? These are CDP and almost certainly generated by your switch. Sometimes in CDP messages there is information about the device that generated the frame.

This is a screenshot from the expanded message