should my local domain have a .local ending?

[c10chevy4x4]

I have a peer-to-peer server workstation setup with the workstation connected to the domain for file sharing purposes (mapped drive). the domain is listed as domain.local;

I"m trying to run down a problem where the server does not show up/can't be pinged from teh workstation and wondering if the .local ending is somehow messing things up. I went into DNS and changed servers PTR record and took off the .local from the domain (now reads 'computername.domain' instead of 'computername.domain.local') and I can now ping the server from teh workstation, but the server still does not show up when browsing 'entire network' ->'microsoft network'.

any one with ideas??? to make it more difficult, neither the server or workstation shows up on the server when browsing thenetwork!

[r8500]

did this ever work?

[c10chevy4x4]

no, I've have not gotten around to trying to make it work until now.

when I use to have a NT4 server, everything worked fine, but that would a couple of motherboards ago.

[r8500]

Then go through the sticky at the top of this section. Read through those, and make sure that everything is set up correrctly.

[c10chevy4x4]

I applied the browsing regedit tip BipolarBill noted and the browsing does speed up, but does not change the original problem.

any other ideas?
thanks, P

[kwebb]

I have a peer-to-peer server workstation setup with the workstation connected to the domain for file sharing purposes

Elaborate on that first. Is it a peer to peer LAN or are you using a domain model? As written that doesn't make much sense.

[c10chevy4x4]

the server and the XP machine are both connected to the internet router which is how the mapped drive is shared. the XP machine is connected to the server's domain. it may be more appropriate to say the XP machine does not surf the web 'through' the server (which has only 1 NIC installed).

my mistake, it was peer-to-peer until I joined it to the domain this morning.

domain it is!