Re: Server not visible in network browser

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Hi Robert

Please see inline;

"Robert Li [MSFT]" <v-robeli@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:xPVAq2qoHHA.1144@xxxxxxxxxxxxxxxxxxxxxxxxx
Hi John,

Please take the following steps:

Step 1: Ping the server from client by FQDN, can this be successful>

ping myserver.mydomain.local

Pinging myserver.mydomain.local [192.168.16.2] with 32 bytes of data:

Reply from 192.168.16.2: bytes=32 time<1ms TTL=128
Reply from 192.168.16.2: bytes=32 time<1ms TTL=128
Reply from 192.168.16.2: bytes=32 time<1ms TTL=128
Reply from 192.168.16.2: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.16.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms


Step 2: Run nslookup server.domain.local from client, can this be
successfully?

nslookup myserver.mydomain.local

*** Can't find server name for address 192.168.16.2: Non-existent domain
*** Default servers are not available
Server: UnKnown
Address: 192.168.16.2

Name: myserver.mydomain.local
Address: 192.168.16.2


Step 3: Check if "TCP NETBIOS helper service " on server is set to
automatic.

Already set to automatic and running.


Step 4: Check the binding order.

a. Please open Control Panel -> network connections.
b. Click Advanced -> Advanced settings
c. Please confirm that in the adapters and bindings tab, the connections
should have the following order.
Server local Area Connection
Network Connection
[Remote Access connections]

Already fine.


Step 5: This behavior occurs when server message block (SMB) signing is
enabled and required on the domain controller that is running Windows
Server 2003. Please take the steps to disable the SMB signing on the
server:

1. Start-->Run-->Type ''''regedit'''' and press Enter.
2. Navigate to the following registry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\lanmanserver\Parameters
3. In the right panel, double-click ''''enablesecuritysignature''''. Set
the value data to ''''0''''
4. Navigate to the following registry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Lanmanworkstation\Param
eters\
5. In the right panel, double-click ''''enablesecuritysignature''''. Set
the value data to ''''0''''
6. Open a command prompt, type ''''gpupdate /force'''' and press Enter.

Done.

Still no luck.

Thanks

Regards


.

Relevant Pages

  • Re: Something like "ping" for windows messages.
    ... I'm pretty sure it's no where near that delay. ... the http server was being hammered and it didn't seem too bad. ... I've tried out my "ping" programme on Visual Studio. ... Apparently it doesn't scale past roughly 20 connections I ...
    (microsoft.public.vc.mfc)
  • 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)