Re: Strange!! Pinging but not accessible.

Hi Mike,
I followed as you said. Result is still negative.
I have capture some packets in Etheral.

Client ip:192.168.0.17
Server ip:192.168.0.8
Server Name:pg101

No. Time Source Destination
Protocol Info
693 33.395368 192.168.0.17 192.168.0.8 NBNS
Name query NB PG101<00>

Frame 693 (92 bytes on wire, 92 bytes captured)
Ethernet II, Src: Ibm_94:20:5e (00:0d:60:94:20:5e), Dst: Ibm_16:14:f7
(00:0d:60:16:14:f7)
Internet Protocol, Src: 192.168.0.17 (192.168.0.17), Dst: 192.168.0.8
(192.168.0.8)
User Datagram Protocol, Src Port: netbios-ns (137), Dst Port:
netbios-ns (137)
NetBIOS Name Service
Transaction ID: 0x9a9f
Flags: 0x0100 (Name query)
0... .... .... .... = Response: Message is a query
.000 0... .... .... = Opcode: Name query (0)
.... ..0. .... .... = Truncated: Message is not truncated
.... ...1 .... .... = Recursion desired: Do query recursively
.... .... ...0 .... = Broadcast: Not a broadcast packet
Questions: 1
Answer RRs: 0
Authority RRs: 0
Additional RRs: 0
Queries
PG101<00>: type NB, class IN
Name: PG101<00> (Workstation/Redirector)
Type: NB
Class: IN


No. Time Source Destination
Protocol Info
830 39.976156 192.168.0.8 192.168.0.17 ISAKMP
Identity Protection (Main Mode)

Frame 830 (530 bytes on wire, 530 bytes captured)
Ethernet II, Src: Ibm_16:14:f7 (00:0d:60:16:14:f7), Dst: Ibm_94:20:5e
(00:0d:60:94:20:5e)
Internet Protocol, Src: 192.168.0.8 (192.168.0.8), Dst: 192.168.0.17
(192.168.0.17)
User Datagram Protocol, Src Port: isakmp (500), Dst Port: isakmp (500)
Internet Security Association and Key Management Protocol
Initiator cookie: 2DEE200E3465FEF4
Responder cookie: 0000000000000000
Next payload: Security Association (1)
Version: 1.0
Exchange type: Identity Protection (Main Mode) (2)
Flags: 0x00
.... ...0 = Not encrypted
.... ..0. = No commit
.... .0.. = No authentication
Message ID: 0x00000000
Length: 488
Security Association payload
Next payload: Vendor ID (13)
Payload length: 356
Domain of interpretation: IPSEC (1)
Situation: IDENTITY (1)
Proposal payload # 1
Next payload: NONE (0)
Payload length: 344
Proposal number: 1
Protocol ID: ISAKMP (1)
SPI Size: 0
Proposal transforms: 4
Transform payload # 1
Next payload: Transform (3)
Payload length: 84
Transform number: 1
Transform ID: KEY_IKE (1)
Encryption-Algorithm (1): 3DES-CBC (5)
Hash-Algorithm (2): SHA (2)
Group-Description (4): Alternate 1024-bit MODP group
(2)
Authentication-Method (3): XAUTHInitPreShared (65001)
Life-Type (11): Seconds (1)
Life-Duration (12): Duration-Value (28800)
UNKNOWN-ATTRIBUTE-TYPE (16384): <too big (44 bytes)>
Transform payload # 2
Next payload: Transform (3)
Payload length: 84
Transform number: 2
Transform ID: KEY_IKE (1)
Encryption-Algorithm (1): 3DES-CBC (5)
Hash-Algorithm (2): MD5 (1)
Group-Description (4): Alternate 1024-bit MODP group
(2)
Authentication-Method (3): XAUTHInitPreShared (65001)
Life-Type (11): Seconds (1)
Life-Duration (12): Duration-Value (28800)
UNKNOWN-ATTRIBUTE-TYPE (16384): <too big (44 bytes)>
Transform payload # 3
Next payload: Transform (3)
Payload length: 84
Transform number: 3
Transform ID: KEY_IKE (1)
Encryption-Algorithm (1): DES-CBC (1)
Hash-Algorithm (2): SHA (2)
Group-Description (4): Default 768-bit MODP group (1)
Authentication-Method (3): XAUTHInitPreShared (65001)
Life-Type (11): Seconds (1)
Life-Duration (12): Duration-Value (28800)
UNKNOWN-ATTRIBUTE-TYPE (16384): <too big (44 bytes)>
Transform payload # 4
Next payload: NONE (0)
Payload length: 84
Transform number: 4
Transform ID: KEY_IKE (1)
Encryption-Algorithm (1): DES-CBC (1)
Hash-Algorithm (2): MD5 (1)
Group-Description (4): Default 768-bit MODP group (1)
Authentication-Method (3): XAUTHInitPreShared (65001)
Life-Type (11): Seconds (1)
Life-Duration (12): Duration-Value (28800)
UNKNOWN-ATTRIBUTE-TYPE (16384): <too big (44 bytes)>
Vendor ID payload
Next payload: Vendor ID (13)
Payload length: 24
Vendor ID: MS NT5 ISAKMPOAKLEY
Vendor ID payload
Next payload: Vendor ID (13)
Payload length: 20
Vendor ID: unknown vendor ID:
0x72872B95FCDA2EB708EFE322119B4971
Vendor ID payload
Next payload: Vendor ID (13)
Payload length: 20
Vendor ID: Microsoft L2TP/IPSec VPN Client
Vendor ID payload
Next payload: Vendor ID (13)
Payload length: 20
Vendor ID: draft-ietf-ipsec-nat-t-ike-02
Vendor ID payload
Next payload: NONE (0)
Payload length: 20
Vendor ID: unknown vendor ID:
0x26244D38EDDB61B3172A36E3D0CFB819

Please suggest me if you have any idea looking this log.
Thanks
Hari

Mike Shepperd wrote:
Make sure that the server and client(s) are only pointed to the internal DNS
Server for name resolution, then register your DNS records.
On a DC, run:
net stop netlogon & ipconfig /flusndns & ipconfig /registerdns & net start
netlogon

On a client, run:
ipconfig /flusndns & ipconfig /registerdns

Then check the DNS Console and make sure that it's showing accurate records
for each client and server.

Then try pinging the DC by FQDN from the client. If that's working, then
name resolution should be good.

--

Mike Shepperd
Sunfire Solutions LLC
Seattle, WA

[This posting is provided AS-IS, with no warranties and confers no rights]


<Hari.Maharjan@xxxxxxxxx> wrote in message
news:1166113882.127250.138690@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thanks Mike for quick response.

I have tried with \\192.168.0.8\netlogon, but I got message "No network
provider accepted the given network path".

I guess the problem is with DNS. From server I can ping client using
name. From client I can not ping using name(PG101). Is there any other
way to debug? I am installing WireShark.

Mike Shepperd wrote:
If they're not both pointed to the SBS machine for DNS (and if it's not
working right) then you may not be getting the Kerberos tickets you need
to
access resources on the server. Try connecting to the NETLOGON share by
IP
address (i.e. \\192.168.1.10\NETLOGON). That should bypass Kerberos and
use
NTLM.

I would capture the network traffic and see what's happening on the wire.
You can use netmon which ships with Windows, or better yet, go to
www.ethereal.com and download the latest version (which is now called
Wireshark) and capture the traffic when trying to connect to
\\dcname\share

Obviously the machines are online since they'll respond to a ping so it's
a
security or name resolution issue (quite possibly a combination of the
two).

--

Mike Shepperd
Sunfire Solutions LLC
Seattle, WA

[This posting is provided AS-IS, with no warranties and confers no
rights]


<Hari.Maharjan@xxxxxxxxx> wrote in message
news:1166111284.440746.241780@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi TechExperts,
Suddenly My SBS 2003 server become unaccessible. I can ping from Server
to client and client to server. I have internet in all clients, except
server. I have not enabled firewall . All clients and server are behind
the Netgear Firewall. I have checked application and system logs.
Nothing coming up!!

Your help is highly appreciated. Thanks!

Hari



.

Relevant Pages

  • Re: [NFS] [PATCH 008 of 11] knfsd: Prepare knfsd for support of rsize/wsize of up to 1MB, over TCP.
    ... svc_max_payloadto mean the maximum read/write block size. ... but is the maximum payload size. ... client that trying to send two full-sized payloads in the one request ... Greg Banks, R&D Software Engineer, SGI Australian Software Group. ...
    (Linux-Kernel)
  • Re: ordering of socket connections?
    ... Henry Townsend wrote: ... absolutely sent first in that the client does: ... The shutdown may result in the connection being broken down before any payload is transferred. ... But you don't wamt the closeto block, ...
    (comp.unix.programmer)
  • Re: Cant deserialize xsd:date attributes using Axis WSDL2Java classes
    ... When the client gets back a SOAP message, you could transform the SOAP via ... XSLT into something more edible for the code generated by wsdl2Java. ... You would just need to define an XSL document that transforms the server bad ...
    (comp.lang.java.programmer)
  • Re: Problems using zlib...
    ... Tom Harrington wrote: ... Don Bruder wrote: ... answers back with a gzipped payload - I can parse the headers and find ... How are you talking to this web server? ...
    (comp.sys.mac.programmer.help)
  • Re: remoting large amount of data and improving performance
    ... remote server for the sake of perfomance. ... > The "server" and "client" and client applications are on SAME computer. ... > form to transform them. ...
    (microsoft.public.dotnet.framework.remoting)
Loading