LA

Notes from the help desk to the network

Layan Albahouth

Systems & Networking

Every ticket is a small puzzle, and this site is my notebook of the ones I’ve solved: what I checked, what I learned, and what I’d do next time.

Systems Networks
01

About

I work as a systems support administrator. Day to day that means users, devices, accounts and the connections between them. I’m moving toward infrastructure work where systems and networks meet.

This site is where I keep what I learn: troubleshooting steps and lab write-ups. It only contains personal labs and general techniques.

أعمل في دعم الأنظمة، وأتطور نحو البنية التحتية حيث تلتقي الأنظمة بالشبكات. أوثّق هنا ما أتعلمه من خطوات حل المشاكل والمختبرات.

TroubleshootingDNSVPNMicrosoft 365Endpoint managementWindows
02

Packets & Tickets

Real-world problems, solved step by step. Open a ticket to see how I work through it.

01VPN
Network · FortiClientResolved

FortiClient VPN stops at a percentage: what it tells you

Where the progress bar stops tells you which stage failed, and which team should take the ticket.

Open ticket

FortiClient’s SSL VPN shows a progress percentage while it connects, and where it stops narrows down the cause. These are the stages I use.

  • Stops around 10%. The client can’t reach the VPN server. Check the internet connection first, then the gateway address and port set in FortiClient.
  • Stops at 42 or 43%. An authentication problem. Re-enter the username and password with the exact case they were created in, and check that the user is in the right group.
  • Stops at 45%. Also authentication: wrong credentials, or the FortiGate didn’t get an answer from the remote authentication server.
  • Stops at 48%. A two-factor authentication problem.
  • Stops at 98%. Login worked but the tunnel couldn’t be built. The usual suspects are the network (IPv6 to IPv4, high latency, blocked or inspected traffic) or a corrupted FortiClient installation, so try a different network first, then reinstall FortiClient.

Server-side fixes (groups, policies, timeouts) belong to the network team, but knowing the percentage makes the ticket much faster to route.

الملخص: النسبة اللي يوقف عندها FortiClient تدل على مرحلة المشكلة: عند 10% الوصول للسيرفر، عند 43% و 45% مشكلة مصادقة، عند 48% المصادقة الثنائية، وعند 98% فشل بناء النفق بعد نجاح تسجيل الدخول.

02DNS
Network · ConnectivityResolved

“No internet”: is it the network or the system?

The most common ticket. A few cheap checks show whether it’s the browser, DNS or the connection.

Open ticket

This is one of the most common support tickets, and the cause can sit in either world. Before changing anything, I work through these checks in order, from cheapest to deepest.

  1. Close the browser and try another one. If the second browser works, the problem is the first browser, not the network.
  2. Read the exact error. DNS_PROBE_FINISHED_NO_INTERNET and a connection timeout point to different causes, so I never skip this.
  3. Try one site, then several. One site failing usually means the site itself or its DNS record. Every site failing points to the connection.

Then separate IP from name. Ping an IP address, then a domain name:

  • The IP works but the name doesn’t: DNS is the problem.
  • Neither works: the connection is down, so check the cable or Wi-Fi, the IP configuration and the default gateway.

Some networks block ping, so a failed ping on its own isn’t proof. Run nslookup google.com as a second check: if it fails while the IP address still answers, that points to DNS.

These steps are small, but they tell you where to look before you escalate. They are also where my systems and networking work overlap, and it’s the part I enjoy most.

الملخص: عند شكوى «ما عندي إنترنت»، جرّب متصفحًا آخر، واقرأ رسالة الخطأ بدقة، وحدّد هل المشكلة في موقع واحد أو كل المواقع، ثم اختبر الاتصال بعنوان IP ثم باسم نطاق لتعرف هل المشكلة في الـ DNS أو في الاتصال.

03Mail
Systems · OutlookResolved

Outlook: search not working or new mail not arriving

A full mailbox is only one cause. The local cache and the profile can break sync too.

Open ticket

A full mailbox is one cause, but not the only one. A damaged local cache (the OST file) or a damaged profile can also stop Outlook from showing new mail, so I check in this order:

  1. Check mailbox space. Under File > Info, look at the storage bar. If it’s full, clear Deleted Items.
  2. Check Work Offline. If Outlook is working offline, new mail won’t sync until you switch it back.
  3. Rename the OST file. Close Outlook, open %localappdata%\Microsoft\Outlook, and rename the .ost file to .ost.old. Outlook builds a fresh one and syncs again.
  4. Create a new profile. If it still fails, go to Control Panel > Mail > Show Profiles > Add.

Only rename the OST when the mailbox lives on Exchange or Microsoft 365, because the OST is a local copy and anything stored only on the PC would be lost. Also note that if “Mail to keep offline” is set to a short range, local search only covers that period.

الملخص: افحص مساحة الميلبوكس ووضع Work Offline، ثم أعد تسمية ملف OST، وإذا استمرت المشكلة أنشئ بروفايل جديد. لا تعيد تسمية OST إلا إذا كان البريد على Exchange أو Microsoft 365.

04Teams
Systems · Outlook add-insResolved

Teams meeting option missing in Outlook

Outlook can quietly disable the Teams add-in. Here’s how to bring it back and keep it on.

Open ticket

Outlook sometimes disables the Teams add-in when it decides the add-in loads too slowly. To bring it back:

  1. Go to File > Options > Add-ins, set Manage to Disabled Items, and click Go.
  2. Select the Teams add-in and click Enable.
  3. Restart Outlook.

To stop it happening again, go to File > Info > Slow and Disabled COM Add-ins and choose Always enable this add-in. The new Outlook doesn’t use COM add-ins at all, so this applies to classic Outlook.

الملخص: إذا اختفى خيار Teams Meeting، فعّل الإضافة من Disabled Items ثم أعد تشغيل Outlook، واختر Always enable لمنع تعطيلها مرة أخرى.

03

Longer reads

Feedback

Found this useful? Have a topic idea?

Rate the site or suggest what I should write about next. It takes less than a minute.

Share feedback →

Let’s connect

I’m always glad to talk with people working in systems, networking and security.