Re: VERY OT: IT's ALL GONE A BIT PC was: Slightly OT: Mackie Onyx Firewire system

Replies in line:


The probable reason your machines can't access the XP machine will be down to user access permissions.

Almost certainly.

The XP machine doesn't recognise the user who
is trying to connect.

Nope.

We made it all work perfectly well before using an XP laptop.

We're careful to use the same account names.

Windows XP Home uses the workgroup name: MSHOME
whilst Vista typically uses WORKGROUP by default.

Something those of us who used 'Windows for Workgroups' remember with a slight frisson of horror.

Cold sweats at night mate. Remember it well.


Why do Microsoft keep reminding us of their ghastly failures of days gone past?

So they can say: 'this is how ghastly it used to be, look how we've improved'. They can say it, but that doesn't necessarily make it true ;-)

It's a bit like David Bowie muttering into his microphone 'I once made a record about a gnome'...

How would he know you once made a record about a gnome? Did you? I wouldn't admit that in public, otherwise you'll end up like David Bowie. he once made a record about a gnome you know. He's never lived it down. Or are we getting into a whole new discussion about Linux here? LOL



User name FRED who has an
account on a machine in the MSHOME workgroup will not be recognised by a machine in the WORKGROUP workgroup as FRED. You might want to ensure that all your Vista and XP machines are members of the same Workgroup and that all the users and passwords on your whole network exist on at least the XP machine or all the machines as this will ensure some commonality in the absence of a full network domain, and then to ensure that they are all connected with unique IP addresses to the same network subnet (if they get their IP addresses from your router via DHCP this shouldn't be an issue).

No I don't.

I don't want to do this stuff anymore.

I gave it up three years ago.

I can 'hear' desperation in your reply. Go to a dimly lit room filled with the fragrance of perfumed candles and think happy thoughts. None of it is worth the stress.


If I do have to do it I want at least £20 an hour for doing it. (Plus meals and travel and hotel expenses)

At least double that hourly rate, otherwise you can come and work for me and I'll retire on what I charge for your services. :-)


What I want is a washing machine.

I bet Microsoft make Washing Machines. After all, they've just come up with a new coffeee table...


Nobody expects the users of washing machines and tumble driers to worry about filter mesh sizes and conditioner viscosity, that's 'for the professionals'. Why should I have to worry about network naming protocols because Microsoft have published yet another iteration of their rather expensive operating system?

Who the hell changes basic system settings at that level.

No one who has any semblance of sanity left. I do, but then I am a diode or two short of a 600w PSU anyway, so it doesn't matter really.


A new security system, yes. that's reasonable, if only because personal computer security is always rubbish and one day they might make it all go right, but changing names for no very good reason. It's like (to try and get on-topic for the group for a moment) Martin changing the body size, it's something that has happened about four times in 175 years and people are still talking about the last time...

They claim it's a whole new product but they're not actually fooling anyone who has ever had anything to do with real computers.

Yep. That sums it up nicely. MS-DOS 2.11 commands still work in the main. Bring back DOS and dBASE 3+


Additionally, because there is no local DNS server on your network

Who had a single class B or C network with a DNS server on it?

Most small businesses running Server 2003 or Small Business Server 2003. Local DNS and DNS forwarding.


Come to think of it, who, outside a major bank or public utility or ISP, runs their own DNS? I imagine BT do, but they're one of the few organisation in the world with a real live Class A address...

, all your
machines need to discover by other methods, the friendly names of your computers. This can take a bit longer than if using DNS. A quick way round this is to address each PC and shared folder by its IP address,

Except, like everyone else in the world, I use DHCP.

And what's more if I force an IP address the laptops becomes useless if I want to use the free WiFi point down at the pub.

Ah yes. The pub with free WiFi access. What a perfect concept. Where is this pub? Is it local? Can I go there now?


Well, unless I want to do deep surgury to the network settings every time I take it out of the house.

Microsoft are trying to make a 'one size fits all' networking system that includes everyone from home users to vast governmental ministries and reasonably obviously it just doesn't work at the extreme ends of the spectrum. The problem is that the majority of users are at the extreme ends of the spectrum.


Agreed. 100% correct on that, and that's exactly why I have some of my clients experiencing great difficulty in understanding why a £199 barely home spec Dell with 512MB RAM, Celeron and Vista Basic they've seen advertised on TV isn't suitable for the office.




.

Relevant Pages

  • Re: cannot see my computer in the network
    ... Do you have DNS setup correctly and what client are you using....you said ... workgroup group ....you mean it was a workgroup before...you turned it into ... > other computers on the network but I cannot see my server. ...
    (microsoft.public.win2000.networking)
  • Shift to Fedora 2 - Re: eth0 fails (inactive) on boot
    ... > How can I keep my network card from deactivating each time I ... HARDWARE TAB ... Primary DNS: 192.168.2.1 ... DNS Search Path: WORKGROUP ...
    (linux.redhat)
  • Re: Name resolution for local names using DHCP
    ... up as a Windows XP network, with workgroup name "MSHOME", and later I ... search line is handed out by your dhcp server and placed there by ... That allows dns to use dns nameservers without searching the domain first. ...
    (comp.os.linux.networking)
  • Re: DNS Problems
    ... >i may be barking up the wrng tree as i don't have a DNS server on my network ... >propagate through the network. ... Computers or shares are missing in My Network Places. ... I cannot locate other computers in the workgroup. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Network Neighborhood
    ... > inability to browse by using Network Neighborhood in Windows 95 or Windows ... > communicated effectively with the other workgroup computers. ... > not have a common networking protocol, a common workgroup, and common user ... the computer that is running Windows ...
    (microsoft.public.win2000.networking)