Re: 2003 R2 SP2 problem (DNS?)



Hi Jeremy,

All settings are default. No, I can't do a net use or even ping to the
DC by name or even IP - net use \\192.168.1.254 /u:administrator fails
with a "System error 1231. The network location cannot be reached". as
does net use \\192.168.1.254. Gives the same error and there is no
password prompt. However, I can ping by IP.

Found this on the net and tried it. The key did not exist on the DC so
I created it, but it did with 0 value on the second server.

HKLM\System\CurrentControlSet\Services\NetBT\Parameters\SMBDeviceEnabled
- Change the value of SMBDeviceEnabled to "1"

BTW, these are virtual machines so it can't be a hardware problem, and
there is nothing out of the ordinary with the virtual network. 2000
Server, etc, works fine.

Thanks,

Peter


On Sat, 21 Apr 2007 21:51:37 +1000, "Jeremy"
<jeremy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

You wont be able to ping "east" unless the DNS suffix on the machine is
test.net. Double check the SMB Signing settings on each server to ensure
they are compatible, also check the LMAuthentication level and make sure
they can agree on an authentication protocol.

Can you do a net use to the DC with domain credentials?

i.e. net use \\dc.east.test.net /user:east\administrator

This will prove if both authentication and SMB are working.

Cheers,
Jeremy.

"PMK" <expat_th-usenet@xxxxxxxx> wrote in message
news:vftj23hbkkc30g6k026o3chm26f4hfbv5v@xxxxxxxxxx
Hi,

I've done this countless times on 2000 server but it is not working on
2003 Enterprise Server R2 SP2.

Set up a DC for a new domain, east.test.net, 192.168.1.254 including
DNS server with reverse lookup zone. DCDIAG and NETDIAG don't show any
errors. I can ping east and east.test.net from this DC. Firewall is
off.

Install same software on another server. Firewall off. Join workgroup
(can't join domain). Set DNS server to 192.168.1.254. Can ping
east.test.net but not just the name "east". Error is "Ping request
could not find host east. Please check the name and try again"

Can't join the domain. If I try to join, I do get the name/password
prompt then "The network location could not be reached."

Help would be most appreciated.

Peter
8756c5
.



Relevant Pages

  • Re: Windows 2003 Server works fine but cannot be pinged
    ... Check TCP/IP settings. ... Make sure that server doesn't have ICF enabled. ... ICF will stop any incoming traffic (including ping to the server) by ... Can you ping e.g. default gateway? ...
    (microsoft.public.windows.server.general)
  • Re: RDP can not logon error
    ... Tracert & Ping to dc on the same subnet as the server that is having trouble. ... No network provider accepted the given network path.. ... Starting test: CrossRefValidation ...
    (microsoft.public.windows.server.general)
  • Re: Cannot connect to Server
    ... Test 1 - the clients can ping one anotehr ... gpupdate/force - reboot both client and server - ping to server from client ... Suggestion 2 - ping to server works when running safe mode with networking ...
    (microsoft.public.windows.server.sbs)
  • Re: The specified network name is nolonger available
    ... My server is named FS1. ... > ping \\fs1 and I will get a successful return. ... I still can access the drives marked ... What is the point in these permissions as they can be bypassed by mapping ...
    (microsoft.public.win2000.networking)
  • Re: RDP can not logon error
    ... ping and tracert to the dc in that remote site (where this system ... Tracert & Ping to dc on the same subnet as the server that is having ... No network provider accepted the given network path.. ... Starting test: CrossRefValidation ...
    (microsoft.public.windows.server.general)