2 replies
by lordinfidel
You have half of the battle down already by assigning static IPs to the servers.
First ping the servers by their IP, then machine name. If you get a reply (with the right ip) that is a good sign. If you don't get a reply check your tcp/ip settings first on the client machine. If when you pinged it with the machine name and you get the wrong ip, check your wins and dns. Also Make sure that they are on the same network and can talk to each other. All because the subnet mask matches does not mean they are on the same network.
Next... Can any other machines "see" the stand alone via network neighborhood. Check each clients computer to make sure they are a member of the domain/workgroup that the server is in. domains and workgoups do not rely on ip adresses. They utilize the browse list from the master browser. If the client machines are not registered with the master browser they can not get the browser list.
Next... Wins sucks in an tcp/ip routed network with dns. Get rid of it, unless your network is using legacy net bios. WINS in this sort of enviro is more trouble than it's worth. An why your at it, blow away the ME os and install w2k pro. Why go backwards.
Next use a unc path in a browser \\with.the.ip.address of the server. It should ask you for a user name and password to connect to the machine. You should be able to see and access the shares on that system.
I hope gives you some leads... And fyi- questions like this should be posed in the tech q&a section and assigned points.
Have fun and good luck.
Thanks, I will give all that a try...
(didn't realize the Q&A Option...new to site)
This discussion is closed to new replies.
Trending IT Employment posts
Sort by Trending