win xp and server 2003

[Guest]

hello, can anyone correct me if i am wrong:
the primary ip of server 2003 and win xp must be on the same ip segment for
the win xp to be able to access share folder on the server?
i have tried with server2003 primary ip 192.168.x.x and win xp primary ip
192.22.x.x and secondary ip 192.168.x.x but no luck...it works if i set both
primary ip to the same segment.

any professional advise would be welcome.
thanks,

 

[Steve Winograd [MVP]]

hello, can anyone correct me if i am wrong:
the primary ip of server 2003 and win xp must be on the same ip segment for
the win xp to be able to access share folder on the server?
i have tried with server2003 primary ip 192.168.x.x and win xp primary ip
192.22.x.x and secondary ip 192.168.x.x but no luck...it works if i set both
primary ip to the same segment.

any professional advise would be welcome.
thanks,

Any two computers must be on the same IP segment (subnet) to
communicate using TCP/IP.

192.22.x.x. isn't a valid address for a LAN. Use 192.168.x.x. The
standard subnet for that subnet is 255.255.255.0.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com

 

[Ron Lowe]

hello, can anyone correct me if i am wrong:
the primary ip of server 2003 and win xp must be on the same ip segment
for
the win xp to be able to access share folder on the server?
i have tried with server2003 primary ip 192.168.x.x and win xp primary ip
192.22.x.x and secondary ip 192.168.x.x but no luck...it works if i set
both
primary ip to the same segment.

any professional advise would be welcome.
thanks,

For the machines to communicate with each other directly over TCP/IP on the
local network, they must all be in the same subnet. Then they will use a
mechanism called ARP to discover each other. If you want to use IP
addresses in different subnets, then you would normally have them on
different physical networks, and you then need to configure an IP
forwarding router to link the 2 subnets.

The Subnet Mask defines how much of the address
describes the Local Subnet.

The normal subnet mask for a 192.168 network is 255.255.255.0.

That means that for 2 machines to be on the same local subnet,
the first 3 octets must be the same.

For example, they must all be 192.168.0.x

If ( for example ) you wanted to communicate with a 192.22.x.x machine, you
would need to either:
-Set up a router and route to the 192.22.x.x subnet;
or
-Widen the subnet mask to 255.0.0.0
( because 192.168.x.x and 192.22.x.x are in the same subnet, if the mask is
255.0.0.0 )

BTW, 192.22 is not a good choice of address to use on a private LAN.
Use 192.168.x.x.

So in summary, if there is only one LAN segment ( ie no routers connecting
to remote subnets ) then use 192.168.0.x addresses all round would by my
advice.

 

[Guest]

sorry for the late response, i was away for a while.
the office network was divided into 2 subnets with 2 DSL lines to split the
load, my predecessor didn't have server2003 to worry about.
I guess to share the same file server i have to bring them under a same ip
segment.

many thanks,