Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×
It's funny.  Laugh. Operating Systems Software The Internet Windows

Vista Bug Costs Users In Swedish Town Their Internet 644

Lund, Sweden refuses to work around a Vista bug, so people who live there must choose between Vista and internet access. It's nice to see the right people being held accountable for a change.
This discussion has been archived. No new comments can be posted.

Vista Bug Costs Users In Swedish Town Their Internet

Comments Filter:
  • Tests? (Score:3, Interesting)

    by El Lobo ( 994537 ) on Sunday September 02, 2007 @10:30AM (#20441049)
    The university I work for in Sweden began testing with Vista when it was the called Longhorn. We discovered some bugs with the communication between Vista and some of our servers (running Solaris) back in 2004. The bug repports were submited to MS back then and the thing was fixed on the next Longhorn beta "release". It seems it's easier for some not to test and cry out like a baby when it's too late.
  • by The tECHIDNA ( 677584 ) * on Sunday September 02, 2007 @10:33AM (#20441099) Homepage
    It's nice to see the right people being held accountable for a change.

    Nice bit of flamebait there.

    Yeah, I know it's /. , so the majority of folks will be going "HAHA ST00P1D MICRO$OFT LUSERS PWNED LOLZ!1!!eleventyone!"

    Once everybody gets that out of their system, IMHO Lundis Energi is really being a bunch of assholes, and I have no sympathy for them, as it makes them seem like a company run by a bunch of 15-year-olds who've just discovered Ubuntu.

    They find a bug (or rather, the users did) in newly-released software that doesn't play nice with their Linux-based server. Rather than you know, cooporate with Microsoft to help diagnose the problem, they're essentially saying to their users "We think you're a bunch of losers (LUSERS HAHA!!1!), so ya'll use the OS we want and tell you to use! If you don't like it, kiss our asses! And Micro$oft can kiss our ass too until they fix the bug!"

    Because, after all, bugs never, ever happen on any software ever, and developers psychically know what exactly a bug does without any reporting by end-users whatsoever.

    Now if they have a policy of "NOT Windows Vista compatible right now" clearly stated to their users, then that's understandable. But eventually, most folks will move to Vista (like it or not), so this bug needs to be squashed on whomever's end.

    I'll end my rant with this:
    how in the hell is Lundis Energi so sure it's not a bug on their software?

    (sarcasm) Oh right, it's Microsoft, so it MUST be them. (/sarcasm)
  • by mikael_j ( 106439 ) on Sunday September 02, 2007 @10:34AM (#20441107)

    I do tech support and when Internet Explorer 7 came out we noticed that it didn't really get along with the NAT routers we send out to our customers (they sometimes need to do a very very small amount of configuring), I'm not entirely certain of what the problem is but there is no problem with IE5/6, FF, Safari, Opera or even links, but IE7 is a no-go. It took the manufacturer a good three months to come up with a new firmware that addressed the problem, and until then we had to teach hundreds/thousands of customers how to use telnet (and how to install it if they were running Vista, the telnet client is disabled by default). Good times...

    Oh well, at least it's not Windows 9x, I have to give MS some credit for eventually killing off all support for that branch as our superiors decided that since MS no longer supported 95/98/ME in any way then neither should we. :-)

    /Mikael

  • by chasingsol ( 743706 ) on Sunday September 02, 2007 @10:44AM (#20441209)
    I'm using a couple of Vista boxes on my local LAN with a home brewed CentOS router running ISC dhcpd 3.0.5. No problems with obtaining an IP address at all. Sounds like the flaming is misguided this time for a change. Perhaps Lund is using an ancient version of dhcpd?
  • by topham ( 32406 ) on Sunday September 02, 2007 @11:07AM (#20441471) Homepage

    Bad news guys; Microsoft isn't the one with a bug causing the problem. Poor implementation yes, bug no.

    For some bizarre reason Vista expects the address returned from the DHCP server to be broadcast, instead of sent via unicast packet. This is permitted in the specs and supporting the broadcast flag on the server is suggested. ("SHOULD", not "MUST" in the spec.).

    When researching this I found 2 network types which required this, Infinibad and 1394 (Firewire). It looks to me like Microsoft picked the one which would (theoretically atleast) work on all network types, instead of only on a few.

    Of course, this is a typical bad decision as it means that responses from a DHCP server with a lot of Vista clients will flood the network with broadcast responses, but hey, they arent know for making good decisions.

     
  • by thomasdz ( 178114 ) on Sunday September 02, 2007 @11:35AM (#20441793)
    It's not a bug in Vista... they just turned on a flag that is already defined in the standard. The problem is that many many servers didn't implement the standard fully. Who's fault is that? I'd say it's the software that doesn't fully support the standard. Guess what...that's not Vista in this case. Vista has some other network problems, but this isn't one of them.

    Cisco's IOS has had the option of turning on the DHCP broadcast flag on its router client since v12.2 and I'm guessing (can't find a specific reference) that the Cisco IOS DHCP Server probably has also supported it since then... so it's been supported by the major network router manufacturer for many many years.

    The D-Links and the Linksys' (yeah, I know they're Cisco now) routers don't support it either, so it isn't just Linux DHCP servers
  • by AndyCR ( 1091663 ) on Sunday September 02, 2007 @12:04PM (#20442137) Homepage

    Either MS broke Vista or the TCP/IP stack is less functional than before.
    Ding, we have a winner. Vista's networking stack is indeed less functional than XP's. Why? Simple. XP's was borrowed from BSD; Vista's is Microsoft's own, untested stack. See http://www.twit.tv/sn51 [www.twit.tv] for details.
  • by Niten ( 201835 ) on Sunday September 02, 2007 @12:50PM (#20442661)

    You're fooling yourself if you think that any version of Windows is more user-friendly than Ubuntu.

  • Re:router (Score:3, Interesting)

    by Spazmania ( 174582 ) on Sunday September 02, 2007 @01:00PM (#20442785) Homepage
    Do you think MS is not able to follow the standards?

    If you were paying attention, you'd know that MS did follow the standards. The problem started when MS implemented an option component of the DHCP standard and didn't design in a fallback to the mandatory components (not conservative in what you send.) The problem was then complete when the Linux-side DHCP server refused to respond to packets with the optional flag set instead of doing its best to respond in the way it understood (not liberal in what you accept.)

    Had either side followed this golden rule in network protocol implementation then things would have simply worked.
  • Re:router (Score:3, Interesting)

    by Spazmania ( 174582 ) on Sunday September 02, 2007 @01:10PM (#20442917) Homepage
    So you think that "perfectly acceptable to ignore non-standard requests" means the same thing as "not object to technical errors where the meaning is still clear"? I question your reading comprehension skills.
  • Re:router (Score:3, Interesting)

    by arth1 ( 260657 ) on Sunday September 02, 2007 @01:25PM (#20443103) Homepage Journal
    Do anyone have details on the problem?
    The problems I know of with Microsoft's implementations of DHCP are:
    1. Not honouring the DHCP server when it tells you not to try to update the DNS itself. This is no big problem if you set up the DNS server to not accept customer DNS update requests. It's just extra traffic.
    2. Not handling proxy settings returned by the DHCP server correctly ("Proxy auto-configuration") -- the proxy string has to have a newline or cr added to the end. Example, for ISC dhcpd:
      option prxy code 252 = text;
      option prxy "http://proxy.server.invalid/proxy.pac\n";
      Without the trailing \n (or \r), Windows doesn't fetch the autoconfiguration script -- it's like it doesn't understand null-terminated strings.
      This can be a real problem if a non-transparent proxy servder has to be used.
    3. It doesn't set its name to what's returned by the DHCP server. Very few dhcp clients do, though -- the average linux dhcp client won't do this by default either, although a couple of them at least can do so.
    4. It ignores the lease time and sends renew requests way too often, whether needed or not. Which is not really a problem, just a nuisance.
    5. If receiving DHCP info for multiple interfaces, Windows will concatenate the DNS search list, without removing duplicates. Now this can be more of a problem, if you expect "foo" to resolve to "foo.bar.invalid"'s IP address, but there's a "foo.invalid" too, and "invalid" happens to be inserted before "bar.invalid" in the concatenated search list.

    However, these seem all to be present in both Vista, XP and W2k, so they shouldn't be the issue here. Anyone know what the incompatibility is?

    Regards,
    --
    *Art
  • Re:router (Score:1, Interesting)

    by Anonymous Coward on Sunday September 02, 2007 @01:59PM (#20443471)
    The bug in Vista is that it sends somewhat broken DHCP requests that Lund Energi's DHCP server refuses to reply to.
    From what I can tell, this is misinformation. What happens is that Lund has TWO DHCP servers, and Vista, as a "security feature", shuts down an interface if more than one DHCP server replies to its request.
  • Re:router (Score:3, Interesting)

    by Ash Vince ( 602485 ) on Sunday September 02, 2007 @07:09PM (#20446257) Journal
    I only just realised when reading your post I used to help admin a network setup in a similar manner.

    We set it up like this because we had collision problems due to using very old, non switching hubs and being right on the limit of how many hubs (4 in a row) and users we could have. So it made sense to drop a linux router in the middle of the network and only allow traffic through the router that actually needed to get to the other side. The only upstream connection however was on one side of the router, this was also another linux router doing NAT translation. We could have used hubs with more ports but that would have pushed us over the 100m limit between any two hubs.

    This network is actually still in place as it would cost quite alot to upgrade all the hubs to proper switches and they are also awkwardly placed in terms of access. It is certainly not an ideal network but we did build it unpaid 10 years ago with no real funding.

    The idea was to enable an entire council estate (American translation = Housing Project) to have a cheap shared internet connection. Please bare in mind that this was in the days when the best home connection available was an ISDN line and the alternative was modem, phoneline and paying per minute you were connected. Back then we had over 100 people sharing the ISDN line for £5 per month each. Sure during peak times it was slow, but it was better than anything else available for the cost. And as it was always on if you did want to download anything huge you could just wait until 4am.

    That network is still in place as some people still use it but now they share an ADSL line instead. It is still very low bandwidth but for people on a low income who are not likely to use it heavily anyway it is perfect.
  • by Goaway ( 82658 ) on Sunday September 02, 2007 @07:50PM (#20446603) Homepage
    Uh, I think you're a bit confused here. Ubuntu is the one that keeps calling home with a list of all your installed software. How else do you think it finds updates?
  • by Tanuki64 ( 989726 ) on Monday September 03, 2007 @02:18AM (#20448971)
    It is very interesting how the ISP is blamed here. He could, he should, yada yada. M$ delivered a broken configurations and the ISP has to fix this. Generally not wrong. However, as Linux user I wonder a bit, why he should do this? I have enough examples where ISP refuse to support Linux. If it works, fine. If not, problem of the user. I never heard similar ISP blaming comments about this in any forum. More likely: "Oh yeah, Linux is the outsider, only 0.00001% of all user use it, heh heh heh."

    And how often do I hear about the superiority of Windoze. When some WiFi card does not work under Linux: Linux is not fit for the general desktop. If some WiFi card does not work under Vista: The stupid manufacturer was not able to deliver proper drivers on time.

    I begin to think the only reason that Windoze works at all is because everybody bends over for M$ and paves their path.

    Sorry, but even if those voices, which say the ISP could have acted on behalf of their customers, are right, and they are, I still deem them hypocrites.
  • by CrazedWalrus ( 901897 ) on Monday September 03, 2007 @03:24AM (#20449297) Journal
    Heh -- I was just talking to my dad, who bought a Vista laptop recently. I asked him his thoughts, and they went something like this:

    "Well, I can't log into work because the VPN software isn't compatible with Vista. I can't do anything with it because it tells me I'm not the administrator. But I AM the administrator! It's MY COMPUTER! And it keeps telling me I'm not authorized to do things. It's also taking some time to get used to because they changed where things are and I have to go hunting around for things I used to be able to do."

    "Dad, why don't you try out Ubuntu?"

    "Nah - I don't want to spend all that time trying to figure out something new."

    "Dad - you're already spending time trying to figure out something new, and it's broken to boot."

    "Linux is too confusing. I'll just wait til they fix Vista."

    Damn. I think people don't listen to themselves sometimes. They get it into their heads that something is going to be hard, and so they won't ever try it out, even when it wouldn't be any harder than what they're doing now. Maybe it's the "Devil You Know" aspect, but I somehow doubt it.

He has not acquired a fortune; the fortune has acquired him. -- Bion

Working...