Re: My Computers HATE each other

From: Miha Pihler (mihap-news_at_atlantis.si)
Date: 07/31/04 

Date: Sat, 31 Jul 2004 23:06:36 +0200

Hi Sam,

server and client are on different subnets according to your IP
configuration....

IP Address. . . . . . . . . . . . : 192.168.0.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0

IP Address. . . . . . . . . . . . : 192.168.219.198
Subnet Mask . . . . . . . . . . . : 255.255.255.0
You have few options.

One is eg. to change 192.168.219.198 to e.g. 192.168.0.198. The most
important thing here is that 192.168.0. part is same ob both servers --
change only last par number of IP number (last - 4th bit).

Second option is to change subnet mask on all your computers from
255.255.255.0 to 255.255.0.0, and then your two computers will again see
each other.

Last thing you can do is use default gateway -- device that will act as a
router between network 192.168.0.x and 192.168.219.x

I hope this helps,

Mike

"Sam" <noluckschmuckNOSPAM@ev1.net> wrote in message
news:netng0hsckv8noobqlqgks5bmufhl43m7n@4ax.com...
>
> Hi,
>
> I've got a pair of computers, each one with Albatron KX600-Pro system
boards,
> and AMD Barton processors. One has Windows 2003 Server (Enterprise
Edition)
> loaded on it (acting as the server), the other with Windows 2000
Professional
> (acting as the client). The server has the Intel PRO/100 S Server Adapter
(PCI),
> the client has the AirLink 10/100 PCI network adapter. They are linked
with
> a LinkSys 10/100 S Port WorkGroup Switch.
>
> I can get the IP addresses for each with the IPConfig /all command.
> Both the server and the client can ping themselves with their own
respective
> IP addresses (as well as localhost), but they cannot ping each other.
>
> I can run the diagnostic tool with the Intel card. The card passes all six
> of the first set of tests (EEPROM, Control Registers, Interrupt, PHY
Loopback,
> MAC Loopback, Link), but when I run the advanced test (for
sender/responder),
> it searches for a responder, but cannot find one. The lights on both of
the
> cards flash during the process, as well as on the LinkSys Switch, so a
signal
> OF SOME KIND is being sent and received.
>
> I've tried using a different switch (Intellinet Ethernet switch),
> and changed out the cabling, with the same results.
>
> I assigned a static IP address to the client, as there is no communication
> with the server for IP address assignment with DHCP.
>
> Here is the client IPConfig:
> -*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
> Windows 2000 IP Configuration
> Host Name . . . . . . . . . . . . : binford-1a
> Primary DNS Suffix . . . . . . . :
> Node Type . . . . . . . . . . . . : Broadcast
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
>
> Ethernet adapter Local Area Connection 4:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : VIA VT6105 Rhine III Fast Ethernet
Adapter
> Physical Address. . . . . . . . . : 00-40-F4-96-EE-A6
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.0.1
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . :
> DNS Servers . . . . . . . . . . . :
> -*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
>
>
> Here is the server IPConfig:
> -*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
> Windows IP Configuration
> Host Name . . . . . . . . . . . . : wsvr-2003e-01
> Primary Dns Suffix . . . . . . . : DNS-Domain-01.com
> Node Type . . . . . . . . . . . . : Unknown
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : DNS-Domain-01.com
>
> Ethernet adapter Local Area Connection 2:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Intel(R) PRO/100 S Server Adapter
> Physical Address. . . . . . . . . : 00-02-B3-F0-92-E4
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.219.198
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . :
> DNS Servers . . . . . . . . . . . : 192.168.219.198
> -*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
>
>
>
> Here is where the server pings itself:
> -*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
> Pinging 192.168.219.198 with 32 bytes of data:
>
> Reply from 192.168.219.198: bytes=32 time<1ms TTL=128
> Reply from 192.168.219.198: bytes=32 time<1ms TTL=128
> Reply from 192.168.219.198: bytes=32 time<1ms TTL=128
> Reply from 192.168.219.198: bytes=32 time<1ms TTL=128
>
> Ping statistics for 192.168.219.198:
> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> Approximate round trip times in milli-seconds:
> Minimum = 0ms, Maximum = 0ms, Average = 0ms
> -*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
>
>
> Here is where the server pings the client:
> -*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
> Pinging 192.168.0.1 with 32 bytes of data:
>
> Destination host unreachable.
> Destination host unreachable.
> Destination host unreachable.
> Destination host unreachable.
>
> Ping statistics for 192.168.0.1:
> Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
> -*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
>
>
>
> Here is where the client pings itself (with localhost):
> -*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
> Pinging binford-1a [127.0.0.1] with 32 bytes of data:
>
> Reply from 127.0.0.1: bytes=32 time<10ms TTL=128
> Reply from 127.0.0.1: bytes=32 time<10ms TTL=128
> Reply from 127.0.0.1: bytes=32 time<10ms TTL=128
> Reply from 127.0.0.1: bytes=32 time<10ms TTL=128
>
> Ping statistics for 127.0.0.1:
> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> Approximate round trip times in milli-seconds:
> Minimum = 0ms, Maximum = 0ms, Average = 0ms
> -*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
>
>
> Here is where the client pings itself (with assigned static IP address):
> -*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
> Pinging 192.168.0.1 with 32 bytes of data:
>
> Reply from 192.168.0.1: bytes=32 time<10ms TTL=128
> Reply from 192.168.0.1: bytes=32 time<10ms TTL=128
> Reply from 192.168.0.1: bytes=32 time<10ms TTL=128
> Reply from 192.168.0.1: bytes=32 time<10ms TTL=128
>
> Ping statistics for 192.168.0.1:
> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> Approximate round trip times in milli-seconds:
> Minimum = 0ms, Maximum = 0ms, Average = 0ms
> -*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
>
>
> Here is where the client pings the server (by assigned static IP address):
> -*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
>
> Pinging 192.168.219.198 with 32 bytes of data:
>
> Destination host unreachable.
> Destination host unreachable.
> Destination host unreachable.
> Destination host unreachable.
>
> Ping statistics for 192.168.219.198:
> Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
> Approximate round trip times in milli-seconds:
> Minimum = 0ms, Maximum = 0ms, Average = 0ms
> -*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
>
>
>
> Here is the result for NetDiag on the server:
> -*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
> ....................................
>
> Computer Name: WSVR-2003E-01
> DNS Host Name: wsvr-2003e-01.DNS-Domain-01.com
> System info : Windows 2000 Server (Build 3790)
> Processor : x86 Family 6 Model 8 Stepping 0, AuthenticAMD
> List of installed hotfixes :
> KB819696
> KB823182
> KB823353
> KB823559
> KB824105
> KB824141
> KB825119
> KB828035
> KB828741
> KB832894
> KB835732
> KB837001
> KB839643
> KB839645
> KB840315
> KB840374
> Q147222
> Q828026
>
>
> Netcard queries test . . . . . . . : Passed
>
>
>
> Per interface results:
>
> Adapter : Local Area Connection 2
>
> Netcard queries test . . . : Passed
>
> Host Name. . . . . . . . . : wsvr-2003e-01
> IP Address . . . . . . . . : 192.168.219.198
> Subnet Mask. . . . . . . . : 255.255.255.0
> Default Gateway. . . . . . :
> Dns Servers. . . . . . . . : 192.168.219.198
>
>
> AutoConfiguration results. . . . . . : Passed
>
> Default gateway test . . . : Skipped
> [WARNING] No gateways defined for this adapter.
>
> NetBT name test. . . . . . : Passed
> [WARNING] At least one of the <00> 'WorkStation Service', <03>
'Messenger
> Service', <20> 'WINS' names is missing.
> No remote names have been found.
>
> WINS service test. . . . . : Skipped
> There are no WINS servers configured for this interface.
>
>
> Global results:
>
>
> Domain membership test . . . . . . : Passed
>
>
> NetBT transports test. . . . . . . : Passed
> List of NetBt transports currently configured:
> NetBT_Tcpip_{AA1F16CA-1C54-4C27-AA4B-1738A28F14B2}
> 1 NetBt transport currently configured.
>
>
> Autonet address test . . . . . . . : Passed
>
>
> IP loopback ping test. . . . . . . : Passed
>
>
> Default gateway test . . . . . . . : Failed
>
> [FATAL] NO GATEWAYS ARE REACHABLE.
> You have no connectivity to other network segments.
> If you configured the IP protocol manually then
> you need to add at least one valid gateway.
>
>
> NetBT name test. . . . . . . . . . : Passed
> [WARNING] You don't have a single interface with the <00> 'WorkStation
Service',
> <03> 'Messenger Service', <20> 'WINS' names defined.
>
>
> Winsock test . . . . . . . . . . . : Passed
>
>
> DNS test . . . . . . . . . . . . . : Passed
> PASS - All the DNS entries for DC are registered on DNS server
'192.168.219.198'.
>
>
> Redir and Browser test . . . . . . : Passed
> List of NetBt transports currently bound to the Redir
> NetBT_Tcpip_{AA1F16CA-1C54-4C27-AA4B-1738A28F14B2}
> The redir is bound to 1 NetBt transport.
>
> List of NetBt transports currently bound to the browser
> NetBT_Tcpip_{AA1F16CA-1C54-4C27-AA4B-1738A28F14B2}
> The browser is bound to 1 NetBt transport.
>
>
> DC discovery test. . . . . . . . . : Passed
>
>
> DC list test . . . . . . . . . . . : Passed
>
>
> Trust relationship test. . . . . . : Skipped
>
>
> Kerberos test. . . . . . . . . . . : Passed
>
>
> LDAP test. . . . . . . . . . . . . : Failed
> [FATAL] Cannot do NTLM authenticated ldap_bind to
'wsvr-2003e-01.DNS-Domain-01.com':
> Timeout.
> [FATAL] No LDAP servers work in the domain 'DNS-DMN-NETBIOS'.
>
>
> Bindings test. . . . . . . . . . . : Passed
>
>
> WAN configuration test . . . . . . : Skipped
> No active remote access connections.
>
>
> Modem diagnostics test . . . . . . : Passed
>
> IP Security test . . . . . . . . . : Skipped
>
> Note: run "netsh ipsec dynamic show /?" for more detailed information
>
>
> The command completed successfully
> -*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
>
>
> Can anyone clue me in as to what is wrong with this picture?
>
>
> TIA.
>
>
> - Sam

Relevant Pages

  • RE: cannot connect computer
    ... if I type in the url of the server i get through ok. ... client computer to SBS domain. ... | I am unable to ping the sbs server by ip or name. ...
    (microsoft.public.windows.server.sbs)
  • 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: Unable to ping client2
    ... I understand that the server box can not ping one ... client workstation after upgraded to SBS 2003 SP1. ... Reboot the SBS Server. ... On the client workstation, run "ipconfig /release" and then run ...
    (microsoft.public.windows.server.sbs)
  • Re: ISA Problem
    ... is the machine you are physically sitting at when you ping. ... Microsoft Internet Security & Acceleration Server: ... Original Client IP Client IP Client Username Client Agent Authenticated ... Client Service Server Name Referring Server Destination Host Name ...
    (microsoft.public.isa)
  • Re: Server Cannot See Clients
    ... Try to connect using the client PC's IP address. ... - Turn of your Internal firewalls during testing ... > The clients can access the server and each other without any problems. ... > List of NetBt transports currently bound to the Redir ...
    (microsoft.public.win2000.networking)