• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

More general but similar to "VISTA box is 'isolated'"

BonzaiDuck

BonzaiDuck

Lifer
I came into this forum to resolve a problem I've only noticed with this new VISTA 64 configuration.

We have in the house a peer-to-peer LAN -- no domain controller. Two of the existing machines are downstairs with me: an XP system and a Win 2K Pro system -- the latter as a file-server for the household. It has a RAID5 array for sharing. We'll probably replace the Win 2K Pro with the newer MS home-server OS -- if I can get an OEM installation disc. The 2K Pro's sun has almost set, so to speak.

The VISTA machine and XP and Win 2K Pro systems are all downstairs, plugged into a gigabit switch. This switch is connected by a CAT-5e cable-drop through the wall to another twin switch upstairs. Upstairs, there are two more XP systems -- call 'em "Mom's."

The switch upstairs in turn connects everything to a Linksys 10/100 router-switch, in turn, connected to our shared cable-broadband modem. For various annoying reasons per the Linksys's firmware shortcomings, I keep DHCP active on the router, but I've assigned a separate part of the subnet to fixed IP addresses. All the computers are so configured with fixed IP addresses, and set up to use the provider's DNS server addresses together with the router's gateway address.

I have similarly assigned a fixed IP to the new VISTA machine. The Vista machine grabs internet access just fine.

All of the other systems "see" each other -- their icons show up mutually in "My Network Places" on each respective machine. the VISTA machine shows up in "network places" on the Win 2K Pro, and now I'm willing to bet that it also appears on the XP systems. But the VISTA system only sees itself -- while it's configured like the rest as part of the peer-to-peer workgroup and assigned to the proper workgroup name.

I want the VISTA machine to be able to share files from the Win 2K Pro server. There are also shared files on at least one other machine upstairs.

What do I have to do to make this happen? I'm wondering if the Win 2K Pro will be able to share to VISTA, but certainly the VISTA machine should be able to "see" that machine, and more certainly it should be able to "see" the XP systems.
 
Look for the LLTD update for the XP systems to make the Vista system 'see' them in the vista network browser.
It is possible you already have that update installed in XP in which case the
problem is something else.
http://en.wikipedia.org/wiki/Lltd

I don't know what the solution is for the W2K box; I'm not sure if they have a LLTD responder for it.

 
Thanks, Quixotic.

I'm not familiar with the LLTD acronym, but I'll read the links. I suspect, though, an inkling of what you refer to here.

Over a couple years'-worth of XP auto-updates, a patch would appear described as "letting XP share files with VISTA or 64-bit systems on a network."

Not that eager all that time to venture into VISTA or a 64-bit OS, I avoided installing the update.

Is that the one you're referring to? I need to take some time to read the links you've posted.

That still leaves me with a foreboding that the 2000-Pro system is s__outta-luck for having VISTA access that RAID5 array. But. . .. I'll find a way of dealing with that issue, as well.
 
Yes, that's essentially correct; AFAIK sometime around the release of Vista, LLTD was offered as an optional patch to permit XP systems to be seen on Vista's network browser.

I should have pointed out that it is really not necessary for networking to succeed, only for the network browser to see the system in the map of the workgroup.

I believe if you had the following systems each with a shared folder called "SHARE":
A Vista 192.168.100.1
B XP 192.168.100.2
C W2K 192.168.100.3

You could still, on any of the systems, explicitly select the "Map A Network Drive" option in explorer or maybe also elsewhere (control panel networking MAYBE?) and use the following UNC paths for direct access each system's share:
\\192.168.100.1\SHARE
\\192.168.100.2\SHARE
\\192.168.100.3\SHARE

Of course permute that depending on what your actual IP addresses are and what the names of the network shares are.

It should connect without the necessity of being able to "see" the other system in question in the network browse list, assuming the firewalls are permissive and the network sharing and client software for sharing are all enabled et. al.

That should be the case even for your W2K box AFAIK.

It will be easier if the owner of the system / shared resource is a username with the same name on each of the systems e.g. "BonzaiDuck" login name for each. You can connect to a share with different credentials (login / password) than your current login name, but I believe there may be a limit as to doing that more than once simultaneously with differing user names. e.g. not being logged in as Duck, but connected to system A as Goose and system B as Quail and system C as Merganzer.

If you "run as administrator" "cmd.exe" you should be able to use the "NET ....." command to do stuff like
NET VIEW
NET USE C: \\192.168.2.100\SHARE
etc.
NET /?
for help / info.
It may be a little different in Vista, but that's the general way it worked for XP/2K/NT.. just do it "as administrator" or you may not have permissions.

ipconfig /a
from the cmd.exe prompt will give you your IP address on your networking ports and stuff.


 
Yo! Don Quixote!!

I came back here and discovered your last post. This is very helpful, and even humbling.

I was using NetBeui protocol for my LAN back in '93/'94, and can't even remember how I made the migration to TCP/IP. But I almost imagine that back then, my younger and quicker little mind would have led me to make the "Map Network Drive" connection before giving up in puzzlement.

Us old people need "more help." We're sluggish shadows of our former selves. You've given it, and I'm sincerely grateful.

I just downloaded the LLTD Responder KB922120 file from Microsoft, and I'm going to poke around and see what develops with this experimental VISTA 64 box. I'll drop back to this thread to post an update of progress.

I should probably make a NotePad file of your message here, to have at my fingertips.

Thanks again.

BonzaiDuck
 
Yay-yowww!! I'm "in." Connection established on to the Win 2K Pro system after editing user info, shares and permissions on that system.

That's really the only system I need access to with the VISTA machine. Great.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top