|
R. Giskard Reventlov wrote: They say
"They" are crazy. I've never had jet lag traveling within the US, even coast to coast. I imagine 6+ hours will definitely take a day or two.
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
RyanDev wrote: I've never had jet lag traveling within the US
Me either and I rarely get it going to the UK, always get it coming back. I even slept well on the plane - maybe that was the problem!!!
Probably be ok by Friday - until then, fuzzy, foggy brain and a nagging appetite.
|
|
|
|
|
Sleep if it is a night flight and stay awake on a day flight (as much as possible)
Then fight the urge to go to bed early the first evening what ever direction you fly.
Also try to eat at normal hours (normal in the new time zone).
|
|
|
|
|
RyanDev wrote: ... I've never had jet lag ...
I get a little jet lag even travelling one time zone.
My wife and I just went on a 6500 mile road trip to the East coast of the Untied Snakes and Maritime provinces of Canada (2 time zones) and had to adjust twice in both directions.
Probably one of the hindrances was television, since East coast television is an hour later than for Central time zone residents. We watch news and a late night talk show, so were adjusting to the local time properly, then the television stuff pushed us back the wrong way.
I'm retired. There's a nap for that...
- Harvey
|
|
|
|
|
|
I traveled to the far east on May 1 and got back to the midwest U.S. on Sunday May 15. This time of the year there is a 11 hour difference. Well I got in late on Sunday and went to work the next day, like it was nothing. I typically take a 2 hour nap after work, then eat dinner and whatnot. For 2 weeks was needing to set my alarm to go off at 8 PM because if I didn't, I'd sleep until 11 PM or later and have problems getting back to sleep before morning.
I am better now.
|
|
|
|
|
My worst jet lag was in 1972. I and some colleagues flew from South Africa via London (where we spent about a week) to New York (where we spent a few days) to Jacksonville in Florida (where we spent a few days) to Sydney in Assieland, with brief refueling stopovers in San Francisco, Hawaii and Fiji. A week later I had not yet adjusted to Sydney time, when we flew from Sydney to Johannesburg with brief refueling stopovers in Perth and Mauritius.
It took me a month to get my normal circadian rhythms back. That is when I realized: Circumnavigating the globe by jet really sucks big time!
Get me coffee and no one gets hurt!
|
|
|
|
|
This one has (so far) stumped folks over at the Microsoft "Community".
One of my Windows 10 boxes (x64, always updated, so whatever the latest build is) will not let me log in to any programs that reach out to login.live.com for authentication.
But only the desktop programs or programs that don't have the authentication built in. The "Store" programs log in with no problem, as does the OS itself. And online things work fine, like signing in to MSDN or whatever.
Running a desktop program, all I get is some variation of Can't reach that page or Something went wrong or Connection closed, depending on how the program is set up.
So...I can't log in to Visual Studio or TFS, I can't log in to desktop Skype, I can't log in to OneDrive, etc etc etc.
Except, and this is the killer, if I have Fiddler running and logging the traffic, all of the programs work just fine.
A) What kind of sense does it make to only allow login if there's a spy on the line?
B) Fiddler doesn't log anything "wrong" or even iffy. Just normal web requests and responses. (And a LOT of HTTP and HTML formatting errors like expecting X number bytes but receive 0, or unclosed quotations)
None of the usual diagnostics like sfc or dism pick up anything, of course.
|
|
|
|
|
Random guess: have you checked whether "Use TLS 1.0 / 1.1 / 1.2" is ticked in the "Advanced" page of your IE settings?
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Probably. I'm pretty sure I checked that somewhere along the line. I know for sure I never unchecked them for any reason. :p
|
|
|
|
|
Any PAC files[^] on your network? Or any chance you could be affected by the WPAD name collision vulnerability[^]?
If Fiddler's causing a "Schrödinger's Bug", you might need to get down and dirty with Wireshark[^] to track the problem down.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Pretty sure nothing of a proxy nature appears anywhere in my systems. I'll double check, and check the modem/router, too, to make sure they haven't "improved" it without telling me.
Still, since it's just this one computer with the problem, it shouldn't be the network. (An identical Win10 box doesn't have any issues.)
|
|
|
|
|
Quote: What kind of sense does it make to only allow login if there's a spy on the line?
We all behave better when we know someone is watching. 
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
Have you tried disabling the firewall and rebooting with it disabled? One of the people at work ran into an issue on Win7 where that was the only way to fix it. Something was preventing a program from binding to a socket that it needed, even though nobody was using it or had it reserved via the registry keys. It was some sort of new issue -- everything has been working fine for them, then poof, suddenly it stopped working fine.
We can program with only 1's, but if all you've got are zeros, you've got nothing.
|
|
|
|
|
Now that is something I haven't looked at. Ditto on the everything working fine, then not.
Thanks. We'll see what happens when I get home. 
edit: Nope. Didn't fix it. 
modified 2-Jun-16 8:38am.
|
|
|
|
|
One of the things I would check is potential DNS problem. Check the contents of your hosts file for example.
I'm retired. There's a nap for that...
- Harvey
|
|
|
|
|
Even with an empty HOSTS file, it does it. And it uses the same DNS servers as the other machine that works. I've done the whole \flushdns thing, too.
|
|
|
|
|
|
Uninstall Fiddler and - this is important - WinPCap. I bet you've found an incompatibility.
|
|
|
|
|
You mention Skype...Don't they somehow hijack browser content? (to inject call tags) Could it be a problem with the Skype account? I've seen stranger things... Good luck!
"Go forth into the source" - Neal Morse
|
|
|
|
|
Don't know about that, but...there are here versions of Skype (that I have, anyway). Two "native" Win10 versions, Skype for Business, and Skype Video -- both of which I have no problem logging in to, and the "desktop" version of Skype, which uses the reach out and touch live.com login.
|
|
|
|
|
is to receive a snack upside the head.
|
|
|
|
|
Well I'd just send them to boarding school but heh...
|
|
|
|
|
Food for thought, I guess.
|
|
|
|
|
If you order tacos but get tortilla chips, is it nacho lucky day?
Early today, I've got to take herself to the physioterrorist soon
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
