Do workgroup machines have to be on the same subnet to see eachother?

[fbrdphreak]

Got two machines in one office, on a university network. Both running XP Pro SP2. Ran the Network Wizard on them, same workgroup name. File & Printer Sharing enabled. SImple file sharing disabled.

The two can ping eachother.

Machine#1 is on a 152.1.36 subnet, can see the workgroup, and can see itself.
Machine#2 is on a 152.1.35 subnet, can see the workgroup, but cannot see Machine#1.

Do they need to be on the same subnet? What else am I missing? Just need to share ONE folder.

Already got a user acct setup on the host machine (Machine#1) and the folder is shared with permission set to the user acct for Machine#2.

TIA

 

[spidey07]

yes. Unless there is a WINS server.

you could just put an entry in the LMHOSTS file. do a search for it and you're all set.

 

[fbrdphreak]

So just specify the IP of the other machine in the LMHOSTS file. Sounds like a plan.

Anything different I would have to do for Win2K? Trying a similar setup on our 2K Pro machines and they cant' even access the workgroup

 

[cross6]

without a router, you have to manually add routes to the machines

 

[fbrdphreak]

And if we were to enable the NetBEUI(SP?) protocol, that would automatically map out the IPs; right?

 

[spidey07]

If the machines are on different subnets then there is a router(s) between them and netbeui will not work. That is for a single LAN only as it uses broadcasts to locate resources.

Similarily netbios over TCP uses broadcasts to locate resources as well but you can manually map these resources to workgroup and machine names (netbios names) using an LMHOSTS file.

This approach is needed for all microsoft operating systems.

 

[ktwebb]

Different subnets means NetBEUI is out as Spidey said. LMHosts or even the hosts file is an easy enough workaround. I'd just get to it \\152.1.36.x but a static mapping via the lmhosts or hosts file will make it easier overall I suppose.

You do not have to add routes however as mentioned earlier.

 

[spidey07]

Originally posted by: ktwebb
Different subnets means NetBEUI is out as Spidey said. LMHosts or even the hosts file is an easy enough workaround. I'd just get to it \\152.1.36.x but a static mapping via the lmhosts or hosts file will make it easier overall I suppose.

You do not have to add routes however as mentioned earlier.

heh, thanks for the easier answer. why worry about names anyway if you're just moving files.

good catch.

 

[ktwebb]

Well I think it is easier for the average person to just use the NetBIOS names however this is windows and name resolution, without DNS or WINS, can be a........struggle. IP is pretty dependable.

 

[JackMDS]

Originally posted by: fbrdphreak
Machine#1 is on a 152.1.36 subnet, can see the workgroup, and can see itself.
Machine#2 is on a 152.1.35 subnet, can see the workgroup, but cannot see Machine#1.

Why they have to be on different subnets?

There are much better ways to exercise Masochism.

:sun:

 

[spidey07]

Originally posted by: JackMDS

Originally posted by: fbrdphreak
Machine#1 is on a 152.1.36 subnet, can see the workgroup, and can see itself.
Machine#2 is on a 152.1.35 subnet, can see the workgroup, but cannot see Machine#1.

Why they have to be on different subnets?

There are much better ways to exercise Masochism.

:sun:

"Got two machines in one office, on a university network"

A properly designed network will have different subnets within the same building. usually one per floor if it can be accomodated other wise with a large floor space (as is typical in a university) you have different subnets on the same floor.

A truly well designed network has a single subnet served by a single wiring closet. That VLAN does not exist anywhere else and is contained strictly withing that single wiring closet.

So, what subnet you are one depends entirely upon what wiring closet you get your connection from. Same closet? Same subnet. Different closet? different subnet.

 

[fbrdphreak]

Originally posted by: spidey07

Originally posted by: JackMDS

Originally posted by: fbrdphreak
Machine#1 is on a 152.1.36 subnet, can see the workgroup, and can see itself.
Machine#2 is on a 152.1.35 subnet, can see the workgroup, but cannot see Machine#1.

Why they have to be on different subnets?

There are much better ways to exercise Masochism.

:sun:

"Got two machines in one office, on a university network"

A properly designed network will have different subnets within the same building. usually one per floor if it can be accomodated other wise with a large floor space (as is typical in a university) you have different subnets on the same floor.

A truly well designed network has a single subnet served by a single wiring closet. That VLAN does not exist anywhere else and is contained strictly withing that single wiring closet.

So, what subnet you are one depends entirely upon what wiring closet you get your connection from. Same closet? Same subnet. Different closet? different subnet.

Eh, pretty much. They have a BUNCH of subnets dedicated to this one department, which is pretty much located in one building. There's no set criteria as to what devices located where go on what subnet, so its a big mess. I could probly move it to .36 subnet, I was wondering if that was the better thing to do; either way I'll use LMHOSTS and see if that works Thanks all!!