Network / Share Printer and folders: XP and ME

[Gunny_Snipes]

My wife has windows ME (it's not broken, so i'm not fixing it). I of course have XP.

We are both on the same internet connection using a 5 port hub. I would like a tutorial or some specific (meaning not general) instructions on how to accomplish this petty task.

I've tried starting from the begining with a few tutorials I've found.... But I get it wrong somehow as the words they are saying don't match what my PC is saying....


I hope you all can help me out.


Thanks TechIMO!

[Mickwish]

Easy. Helmig has a tutorial on this. Lots of pictures, too. Just follow his lead and it should be easy!

Cheers
Mick

[muno]

Why do they want to put the computers in the same workgroup?

Perhaps dvnt1 knows?

I've never had any of my computers in the same workgroup, and yet everything works perfectly.

I just don't understand the workgroup-mania, or that people suggest to install netbeui for lan.

[DVNT1]

Originally posted by muno
Why do they want to put the computers in the same workgroup?

Perhaps dvnt1 knows?...

Main reason IMO, it helps computers to show up "as expected" within the Network Neighborhood and My Network Places. To a very small degree, it also reduces the number of Browse Masters and related overhead on the network.

[Starfury_2260]

never works for me without having them in the same workgroup. course my network is comprised of 2 systems over crossover.

[muno]

Why doesn't it work for you? When I crosspatch two systems, they get ips via ms automatic_private_ip_addressing (range 169.254.x.y), after that I can just map or whatever other systems resources by using the ip.

Most would argue that 169.254.x.y range sucks, but I love it

[Mickwish]

Well, I wouldn't say it "sucks", but that range is not actually a C'class network range. It's actually windows private range, and is mainly used when no other suitable IP range can be found (eg if you unplug your network cable on a system that uses DHCP, it will default to that range). Not 100% sure, buit I think that range has some limitations as far as networking goes.

I'll see if can find more info on this.

Cheers
Mick

BTW, did gunny_snipes fix his original problem?

[Mickwish]

Ok, found some useful info (on M$'s site, even )

Now, it is worth noting that even after the machine comes up with an AutoNet address, it will still broadcast for a DHCP Server every three minutes or so, and if it does find one at that time, it will request an actual DHCP address from that DHCP Server. So, basically, this makes AutoNet a fall-back mechanism, in the event there actually is a DHCP Server on the segment, but it's temporarily down for whatever reason. If you bring a client onto the network, it will actually assign itself an AutoNet address and you'll still have some limited network connectivity. And then, of course, when your DHCP Server comes back online, it will, within a few minutes, grab an IP address from that server.

One important thing to remember is that AutoNet is really designed for small networks. We're talking about single-segment networks where you traditionally would have set static IP addresses. So it won't work properly if there are any routers involved; it's really not designed for that. If you've got a very small network or a home network, and you don't want to go to the trouble of setting up DHCP, and yet you don't want to have to set up static IP addresses, AutoNet is an ideal solution.

Routers are a problem with APIPA apparently. I use a software router, but it still wouldn't work with automatic addressing. So it is limited.

Cheers
Mick

edit: Yeah, it busts the URL up.

Try this:

http://support.microsoft.com/default.aspx?scid=%2Fservicedesks%2Fwebcasts%2Fen%2Fwc112399%2Fwct112399.asp

[muno]

I use sygate home network, and it works with 169.254.x.y range.

Of course, clients really receiving addresses from apipa will not have internet functionality (apipa only gives ip/mask, no gateway or dns servers).

//edit: Correct link
Fine..
Stupid board doesn't allow links

http://tinyurl.com/247kb