Answered by:
TechNet forums weirdness

Question
-
I have not been able to open TechNet forums using the usual host name today but can both see and post to them by substituting MSDN for TechNet! WTH?
Also, while I was trying to understand the symptom I used nslookup to find an IP address and then used that to connect via HTTP. The forum brand which I got was Expression!? Also, InPrivate browsing as an option worked a bit until I needed to Sign in.
Robert Aldwinckle
---
Answers
-
Looks like it may be Skype that is doing this to me. Now I can't use Answers but there it seems to be looking for me to create yet another Profile for its account. And then trying to Sign out and Login with either of my other accounts fails. If they hadn't forced me to create multiple accounts in the first place I probably wouldn't have these problems. Now they appear to be trying to combine things but botching it.
Robert Aldwinckle
---- Proposed as answer by Ed Price - MSFTMicrosoft employee Wednesday, June 15, 2016 10:11 PM
- Marked as answer by Ed Price - MSFTMicrosoft employee Friday, July 1, 2016 10:58 PM
-
- Proposed as answer by Ed Price - MSFTMicrosoft employee Wednesday, June 15, 2016 10:11 PM
- Marked as answer by Ed Price - MSFTMicrosoft employee Friday, July 1, 2016 10:58 PM
-
for me, I can open the forums but didn't see any post/thread updates beyond may 24, 2016. I have subscribed to feeds and from there I can individually open the posts but as soon as I go back to powershell forum, it just doesn't show anything beyond 24th may.
cheers..uc
Yep, the forums have been having problems all week. See here for more detail:
EDIT: Actually, it seems like the issues have cleared up for now.
EDIT2: Or not.. Now that I look closer, it seems like threads from yesterday and at least part of Tuesday aren't showing up in the thread list yet.
- Edited by Mike Laughlin Thursday, May 26, 2016 12:04 PM
- Proposed as answer by Ed Price - MSFTMicrosoft employee Wednesday, June 15, 2016 10:12 PM
- Marked as answer by Ed Price - MSFTMicrosoft employee Friday, July 1, 2016 10:58 PM
All replies
-
I have had no problems browsing / posting today over here.
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows Server] Datacenter Management
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. -
-
Looks like it may be Skype that is doing this to me. Now I can't use Answers but there it seems to be looking for me to create yet another Profile for its account. And then trying to Sign out and Login with either of my other accounts fails. If they hadn't forced me to create multiple accounts in the first place I probably wouldn't have these problems. Now they appear to be trying to combine things but botching it.
Robert Aldwinckle
---- Proposed as answer by Ed Price - MSFTMicrosoft employee Wednesday, June 15, 2016 10:11 PM
- Marked as answer by Ed Price - MSFTMicrosoft employee Friday, July 1, 2016 10:58 PM
-
Yea I don't use the microsoft office logon that much. It may be the "keep me signed in" has got it jacked up. It may be if you clear history and cookies you can "undo" the "keep me signed in"
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows Server] Datacenter Management
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. -
- Proposed as answer by Ed Price - MSFTMicrosoft employee Wednesday, June 15, 2016 10:11 PM
- Marked as answer by Ed Price - MSFTMicrosoft employee Friday, July 1, 2016 10:58 PM
-
Today was worse and I finally had to reboot. That would be the first one since the last update (for production W10). Then that would be a new quirk related to its updates. Previously the only unplanned restarts which I have found to be obligatory have been with the preview versions where that has been the only way to get sound into my Hyper-V VM.
The troubleshooters are really useless and just plain irritating. One thing that works and puts the lie to every other symptom is PowerShell's Invoke-WebRequest. If it can retrieve a whole page, why do both IE and Edge pretend that there is a connectivity issue and not give instead some useful diagnostics?
Robert Aldwinckle
--- -
They did push a fix last night or early this AM for the authentication cookie issue, that could have impacted your issue as well.
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows Server] Datacenter Management
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. -
I'm still having to use my TechNet = MSDN workaround. This morning it started to look as if things were back to normal but these two threads (and this one) all needed that treatment.
and again, PS Invoke-WebRequest proves that there is no connectivity issue when using the TechNet host.
This is what my nslookup gave me and ipconfig /displaydns confirmed that it would have been used
PS>ipconfig /displaydns | clip PS>nslookup social.technet.microsoft.com Server: UnKnown Address: 192.168.1.1 Non-authoritative answer: Name: lb.social.ms.akadns.net Address: 157.56.75.164 Aliases: social.technet.microsoft.com PS>
From time to time I have to use a HOSTS file override for answers.microsoft.com to work around related performance problems there. However, in that case it is easy to know which data center an IP address goes to. I have no idea what data centers are involved here or even yet have a collection of possible IP addresses to try to use.
Heh. Maybe there's an addressing loop? Look at this tracert extract (out of Canada and until ICMP is assumed to be blocked by the next hop).
6 60 ms 33 ms 34 ms xe-3-3-0.chi12.ip4.gtt.net [141.136.105.33] 7 30 ms 30 ms 30 ms microsoft-corporation-gw.ip4.gtt.net [199.229.231.130] 8 43 ms 32 ms 35 ms ae10-0.ch1-96c-2a.ntwk.msn.net [207.46.40.15] 9 81 ms 79 ms 80 ms be-73-0.ibr02.ch1.ntwk.msn.net [104.44.8.40] 10 79 ms 115 ms 78 ms be-5-0.ibr01.dm2.ntwk.msn.net [104.44.4.76] 11 82 ms 84 ms 87 ms be-3-0.ibr01.dm3.ntwk.msn.net [104.44.4.74] 12 80 ms 84 ms 81 ms be-4-0.ibr02.den07.ntwk.msn.net [104.44.4.97] 13 80 ms 80 ms 79 ms be-1-0.ibr01.den07.ntwk.msn.net [104.44.4.58] 14 82 ms 81 ms 80 ms be-3-0.ibr01.cys01.ntwk.msn.net [104.44.4.112] 15 80 ms 81 ms 87 ms be-1-0.ibr02.cys01.ntwk.msn.net [104.44.4.98] 16 80 ms 79 ms 79 ms be-3-0.ibr01.co2.ntwk.msn.net [104.44.4.122] 17 83 ms 78 ms 79 ms ae71-0.co1-96c-1a.ntwk.msn.net [104.44.8.237] 18 * * * Request timed out. 19 * * *
So, it starts in Chicago, goes to Des Moines, then to Denver, then to Cys? (new to me), then bounces around "Co" (somewhere else in Colorado or Corporate, e.g. Redmond?)In contrast social.msdn.microsoft.com might even be here in Canada. More direct in any case.
9 19 ms 18 ms 18 ms bx7-toronto63_HundredGigE0-6-0-0.net.bell.ca [64.230.51.15] 10 18 ms 19 ms 18 ms a184-84-185-14.deploy.static.akamaitechnologies.com [184.84.185.14] Trace complete. PS>
In order to get this out I had to ultimately switch off power to all my comm gear. I think the latest W10 update has broken my Networking (which does involve a vSwitch over Wi-Fi). Maybe I should try switching to Ethernet.
Robert Aldwinckle
---- Edited by Robert Aldwinckle on forums Friday, May 20, 2016 1:02 PM Postscript
-
Both of those resolve no problem for me with either TechNet or MSDN brands.
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows Server] Datacenter Management
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. -
I did the same trace from Austin and I get to social.msdn in 8 hops
1 1 ms 1 ms 2 ms Linksys00733.attlocal.net [192.168.49.1] 2 55 ms 4 ms 4 ms 108-232-176-1.lightspeed.austtx.sbcglobal.net [108.232.176.1] 3 7 ms 5 ms 5 ms 71.149.77.78 4 7 ms 6 ms * 75.8.128.140 5 9 ms 9 ms 6 ms 12.81.225.241 6 14 ms 15 ms 15 ms ggr3.dlstx.ip.att.net [12.122.138.17] 7 12 ms 12 ms 11 ms ae7.dal33.ip4.gtt.net [199.229.231.25] 8 13 ms 12 ms 13 ms a184-29-153-88.deploy.static.akamaitechnologies.com [184.29.153.88]
TechNet does the same dance for me at *.msn.net
1 1 ms 1 ms 1 ms Linksys00733.attlocal.net [192.168.49.1] 2 5 ms 6 ms 4 ms 108-232-176-1.lightspeed.austtx.sbcglobal.net [108.232.176.1] 3 12 ms 6 ms 6 ms 71.149.77.78 4 * * * Request timed out. 5 10 ms 11 ms 9 ms 12.81.225.241 6 12 ms 14 ms 14 ms 12.122.85.197 7 * * * Request timed out. 8 69 ms 67 ms 67 ms be-61-0.ibr01.dfw05.ntwk.msn.net [104.44.8.124] 9 67 ms 68 ms 67 ms be-4-0.ibr02.dm2.ntwk.msn.net [104.44.4.11] 10 67 ms 67 ms 68 ms be-2-0.ibr01.dm3.ntwk.msn.net [104.44.4.84] 11 66 ms 67 ms 68 ms be-4-0.ibr02.den07.ntwk.msn.net [104.44.4.97] 12 66 ms 66 ms 66 ms be-1-0.ibr01.den07.ntwk.msn.net [104.44.4.58] 13 66 ms 65 ms 66 ms be-3-0.ibr01.cys01.ntwk.msn.net [104.44.4.112] 14 68 ms 66 ms 66 ms be-1-0.ibr02.cys01.ntwk.msn.net [104.44.4.98] 15 65 ms 66 ms 66 ms be-3-0.ibr01.co2.ntwk.msn.net [104.44.4.122] 16 64 ms 65 ms 65 ms ae71-0.co1-96c-1a.ntwk.msn.net [104.44.8.237] 17 * * * Request timed out. 18 * * * Request timed out.
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows Server] Datacenter Management
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. -
-
for me, I can open the forums but didn't see any post/thread updates beyond may 24, 2016. I have subscribed to feeds and from there I can individually open the posts but as soon as I go back to powershell forum, it just doesn't show anything beyond 24th may.
cheers..uc
-
for me, I can open the forums but didn't see any post/thread updates beyond may 24, 2016. I have subscribed to feeds and from there I can individually open the posts but as soon as I go back to powershell forum, it just doesn't show anything beyond 24th may.
cheers..uc
Yep, the forums have been having problems all week. See here for more detail:
EDIT: Actually, it seems like the issues have cleared up for now.
EDIT2: Or not.. Now that I look closer, it seems like threads from yesterday and at least part of Tuesday aren't showing up in the thread list yet.
- Edited by Mike Laughlin Thursday, May 26, 2016 12:04 PM
- Proposed as answer by Ed Price - MSFTMicrosoft employee Wednesday, June 15, 2016 10:12 PM
- Marked as answer by Ed Price - MSFTMicrosoft employee Friday, July 1, 2016 10:58 PM