Win98 and WinMe clients can ping, but not browse Server 2003?

[Luke122]

Hey there everyone,

I've just added a Win2003 server to an existing domain as a file
server. I created a shared folder, setup the appropriate permissions,
and pointed the users login scripts to map the share as a network
drive.


It's been working fine for a few weeks, but over the weekend something
went wrong. The Win98 and WinMe clients (only a handful on the network,
but they are still in use) can ping the IP of the 2003 server, but not
browse to it or access the shares. The WinXP clients are working just
fine, which makes me think it's not a DNS issue. However, when the
older clients try to ping the server name (Server2.. so original I
know) they get "host not found", which leads me back to DNS.


Even when trying to browse by the IP address (start, run, \\10.1.1.154)
they get an error saying that it cannot be found (even though they can
ping it successfully!!!). I'm losing my mind here..


Any suggestions anyone?

 

[smashp]

use WINS

 

[NogginBoink]

1) ensure the Server service is started on the w2k3 server

2) ensure the windows firewall on the server is either disabled or you've allowed the appropriate traffic through.

3) get rid of Win9x and move to a real operating system. 😀

 

[NogginBoink]

Originally posted by: smashp
use WINS

He's using the server's IP address at the run line; no name resolution is needed at all in this scenario. WINS won't help. Even if it were a name resolution issue, if the client and server are on the same subnet the clients should be able to resolve the name through broadcast resolution.

WINS is evil and must be stopped! The fewer implementations of WINS in this world the happier Jesus will be.

 

[Luke122]

Server service is running.

Firewall is disabled.

Moving off of 9x is in progress, but it was working until this weekend, and no changes were made over the weekend that I'm aware of at this time.

It was suggested that perhaps having dual nic's in the server box could be part of the issue, so i'm doing some testing on that now.

 

[NogginBoink]

Originally posted by: Luke122
Server service is running.

Firewall is disabled.

Moving off of 9x is in progress, but it was working until this weekend, and no changes were made over the weekend that I'm aware of at this time.

It was suggested that perhaps having dual nic's in the server box could be part of the issue, so i'm doing some testing on that now.

Well, you're using the IP address of the server from the client, so that's not likey.

Ensure the NICs on the server each belong to a different subnet and that only one has a default gateway.

 

[Luke122]

I've got it working now..

Supposedly (and this sounds strange to me, but it works..) there is an issue with the TCP stack in older versions of windows. Having dual nics in the server caused the older clients to default to the nic with the lower value MAC. (The two nic's have sequential MAC's)

I disabled the second nic (mac ending in 8D), hardcoded the IP to the remaining one (mac ending in 8C), updated the DNS again (and restarted the service), then disabled and re-enabled NetBios over TCP.

Works now. I'm pretty confused by the whole thing, so i'll be doing more research on this oddball issue, and hopefully it's something that not too many people would have to deal with.

 

[smashp]

Originally posted by: NogginBoink

Originally posted by: smashp
use WINS

He's using the server's IP address at the run line; no name resolution is needed at all in this scenario. WINS won't help. Even if it were a name resolution issue, if the client and server are on the same subnet the clients should be able to resolve the name through broadcast resolution.

WINS is evil and must be stopped! The fewer implementations of WINS in this world the happier Jesus will be.

this coming from someone who thinks Windows 2003 has a "windows firewall"

It is only implemented with duel nics and the use or ras