routing and remote access server is blocking printer pings

Discussion in 'Microsoft Windows 2000 Enable' started by jeff_pelech@portalberni.ca, Dec 31, 2008.

  1. Guest

    OK, I have a Windows 2000 Server with 2 nics running Routing and Remote
    Access. 1 nic is set to 192.168.5.x and the other is set to 192.168.1.x. On
    the 5.x side on the client computers, I can ping and connect to any computer
    on the 1.x side. But not a single computer on the 5.x side can ping or
    connect to any printer on the 1.x side. What's going on? Thanks.
     
    , Dec 31, 2008
    #1
    1. Advertisements

  2. Guest

    Here is data from a frame in Network Monitor for Win2K Server. I was trying
    a tracert command from 5.1 to 1.67 and the command only makes it as far as
    the router itself (5.8) then requests time out.

    283 35.656250 001A64A0616A LOCAL NBT NS: Query req. for *<00...(15)>
    192.168.5.1 192.168.1.67 IP
    Frame: Base frame properties
    Frame: Time of capture = 1/2/2009 9:42:46.468
    Frame: Time delta from previous physical frame: 78125 microseconds
    Frame: Frame number: 283
    Frame: Total frame length: 92 bytes
    Frame: Capture frame length: 92 bytes
    Frame: Frame data: Number of data bytes remaining = 92 (0x005C)
    ETHERNET: ETYPE = 0x0800 : Protocol = IP: DOD Internet Protocol
    ETHERNET: Destination address : 00104B6AE205
    ETHERNET: .......0 = Individual address
    ETHERNET: ......0. = Universally administered address
    ETHERNET: Source address : 001A64A0616A
    ETHERNET: .......0 = No routing information present
    ETHERNET: ......0. = Universally administered address
    ETHERNET: Frame Length : 92 (0x005C)
    ETHERNET: Ethernet Type : 0x0800 (IP: DOD Internet Protocol)
    ETHERNET: Ethernet Data: Number of data bytes remaining = 78 (0x004E)
    IP: ID = 0x25EB; Proto = UDP; Len: 78
    IP: Version = 4 (0x4)
    IP: Header Length = 20 (0x14)
    IP: Precedence = Routine
    IP: Type of Service = Normal Service
    IP: Total Length = 78 (0x4E)
    IP: Identification = 9707 (0x25EB)
    IP: Flags Summary = 0 (0x0)
    IP: .......0 = Last fragment in datagram
    IP: ......0. = May fragment datagram if necessary
    IP: Fragment Offset = 0 (0x0) bytes
    IP: Time to Live = 128 (0x80)
    IP: Protocol = UDP - User Datagram
    IP: Checksum = 0x8D1F
    IP: Source Address = 192.168.5.1
    IP: Destination Address = 192.168.1.67
    IP: Data: Number of data bytes remaining = 58 (0x003A)
    UDP: Src Port: NETBIOS Name Service, (137); Dst Port: NETBIOS Name Service
    (137); Length = 58 (0x3A)
    UDP: Source Port = NETBIOS Name Service
    UDP: Destination Port = NETBIOS Name Service
    UDP: Total length = 58 (0x3A) bytes
    UDP: UDP Checksum = 0x4E4E
    UDP: Data: Number of data bytes remaining = 50 (0x0032)
    NBT: NS: Query req. for *<00...(15)>
    NBT: Transaction ID = 59979 (0xEA4B)
    NBT: Flags Summary = 0x0000 - Req.; Query; Success
    NBT: 0............... = Request
    NBT: .0000........... = Query
    NBT: .....0.......... = Non-authoritative Answer
    NBT: ......0......... = Datagram not truncated
    NBT: .......0........ = Recursion not desired
    NBT: ........0....... = Recursion not available
    NBT: .........0...... = Reserved
    NBT: ..........0..... = Reserved
    NBT: ...........0.... = Not a broadcast packet
    NBT: ............0000 = Success
    NBT: Question Count = 1 (0x1)
    NBT: Answer Count = 0 (0x0)
    NBT: Name Service Count = 0 (0x0)
    NBT: Additional Record Count = 0 (0x0)
    NBT: Question Name = *<00...(15)>
    NBT: Question Type = Node Status Request
    NBT: Question Class = Internet Class
    00000: 00 10 4B 6A E2 05 00 1A 64 A0 61 6A 08 00 45 00 ..Kjâ...d aj..E.
    00010: 00 4E 25 EB 00 00 80 11 8D 1F C0 A8 05 01 C0 A8 .N%ë..?.Â.ˬ..ˬ
    00020: 01 43 00 89 00 89 00 3A 4E 4E EA 4B 00 00 00 01 .C.?.?.:NNêK....
    00030: 00 00 00 00 00 00 20 43 4B 41 41 41 41 41 41 41 ...... CKAAAAAAA
    00040: 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 AAAAAAAAAAAAAAAA
    00050: 41 41 41 41 41 41 41 00 00 21 00 01 AAAAAAA..!..


    "" wrote:

    > OK, I have a Windows 2000 Server with 2 nics running Routing and Remote
    > Access. 1 nic is set to 192.168.5.x and the other is set to 192.168.1.x. On
    > the 5.x side on the client computers, I can ping and connect to any computer
    > on the 1.x side. But not a single computer on the 5.x side can ping or
    > connect to any printer on the 1.x side. What's going on? Thanks.
     
    , Jan 2, 2009
    #2
    1. Advertisements

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. Amika

    Server/Client access

    Amika, Nov 5, 2003, in forum: Microsoft Windows 2000 Enable
    Replies:
    1
    Views:
    486
    Mohanchand Koduri [MSFT]
    Jan 2, 2004
  2. BS

    remote desktop - how can I enable it on Win2000 server

    BS, Jan 12, 2004, in forum: Microsoft Windows 2000 Enable
    Replies:
    2
    Views:
    73,435
    Marc Reynolds [MSFT]
    Jan 15, 2004
  3. Guest

    Remote Access Connection Manager Problem

    Guest, Oct 26, 2006, in forum: Microsoft Windows 2000 Enable
    Replies:
    1
    Views:
    508
    Guest
    Oct 26, 2006
  4. martin

    for baudoin: truly charming nntp server access - corhi - (1/1)

    martin, Mar 27, 2007, in forum: Microsoft Windows 2000 Enable
    Replies:
    0
    Views:
    593
    martin
    Mar 27, 2007
  5. Daniel

    Media Copies in Remote Storage Manager for Windows 2000 Server

    Daniel, Jun 26, 2008, in forum: Microsoft Windows 2000 Enable
    Replies:
    0
    Views:
    1,598
    Daniel
    Jun 26, 2008
Loading...

Share This Page