Differences between revisions 1 and 17 (spanning 16 versions)
⇤ ← Revision 1 as of 2023-04-24 11:45:35 →
Size: 1126
Editor: hgiger
Comment:
← Revision 17 as of 2024-01-30 12:29:01 → ⇥
Size: 1724
Editor: davidsch
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
Assume you own a cabled network device and you are not able to establish any connection via one of the UTP wall sockets.
Did you consider the following:		 Assume you own a '''cabled''' network device and you are not able to establish any connection via one of the UTP wall sockets, <<BR>>
did you consider the following:

---------------
Line 9: Line 11:
1. Has my device already been registered on the DHCP server? ---------------

2. Has my device already been registered on the DHCP server?
Line 12: Line 16:
1. Is the network cable I'm using physically ok, resp. could it be, that it is not working?
   Ask the hardware responsible of your Institute for a alternative cable.		 ---------------
 
3. Is the network cable I'm using physically ok?
   Ask the hardware responsible of your Institute for an alternative cable.
Line 15: Line 21:
1. Did I deactivate WLAN of my device?
   If not, do so, because WLAN activated in parallel to cabled networking can cause problems.		 ---------------
Line 18: Line 23:
1. Did I deactivate 802.1x authentication of my device?
   If not, do so, because if 802.1x is activated, the registered MAC adress will be ignored, as a consequence you won't be able to get into the correct network.		 4. To reset the UTP socket, unplug and replug the network cable from the UTP socket for 20 to 30 seconds.
Line 21: Line 25:
1. Has a dumb switch been connected between my device and the UTP socket? ---------------

5. Did I deactivate wifi of my device?
   If not, do so, because wifi activated in parallel to cabled networking can cause problems.

---------------

6. Did I deactivate 802.1x authentication of my device?
   If not, do so, because if 802.1x is activated the registered MAC adress will be ignored, as a consequence you won't be able to get into the correct network.

---------------

7. Has a dumb switch been connected between my device and the UTP socket?
Line 23: Line 39:

---------------

8. Are the network settings of my device correct, e.g. did I activate DHCP?
   Please check

---------------

9. Is the hardware, e.g. network card, of my device working correctly, are the LEDs blinking?
   Please check

---------------

If you have checked it all and the problem persists, write to: support@ee.ethz.ch
probabely ISG D-ITET can help.

Network Connection Problems

Assume you own a cabled network device and you are not able to establish any connection via one of the UTP wall sockets,
did you consider the following:

1. Has the UTP socket already been patched?

2. Has my device already been registered on the DHCP server?

3. Is the network cable I'm using physically ok?

  • Ask the hardware responsible of your Institute for an alternative cable.

4. To reset the UTP socket, unplug and replug the network cable from the UTP socket for 20 to 30 seconds.

5. Did I deactivate wifi of my device?

  • If not, do so, because wifi activated in parallel to cabled networking can cause problems.

6. Did I deactivate 802.1x authentication of my device?

  • If not, do so, because if 802.1x is activated the registered MAC adress will be ignored, as a consequence you won't be able to get into the correct network.

7. Has a dumb switch been connected between my device and the UTP socket?

  • If yes, pull the dumb switch' power cable for approx. 20 seconds to empty it's port cache. After that, try again.

8. Are the network settings of my device correct, e.g. did I activate DHCP?

  • Please check

9. Is the hardware, e.g. network card, of my device working correctly, are the LEDs blinking?

  • Please check

If you have checked it all and the problem persists, write to: support@ee.ethz.ch probabely ISG D-ITET can help.

FAQ/network_connection_problems (last edited 2024-01-30 12:29:01 by davidsch)