problem with comptuers not able to see eachother on network

Posted on 2011-03-10
Medium Priority
Last Modified: 2012-05-11
I inherited a strange issue from a friend where the computers are connecting to a really basic file share on a computer acting as a server. The computer is running windows server but is not part of a domain. All of the workstations are not part of the domain either. Some of the pcs can connect to the shares via ip address however some can connect via name \\pebserver. Yet further some can connect by both. i think there is aproblem as when I configure the workstation to receive an address via dhcp I get

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\User2>ipconfig /all

Windows IP Configuration

        Host Name . . . . . . . . . . . . : jdgx280
        Primary Dns Suffix  . . . . . . . :
        Node Type . . . . . . . . . . . . : Broadcast
        IP Routing Enabled. . . . . . . . : Yes
        WINS Proxy Enabled. . . . . . . . : No
        DNS Suffix Search List. . . . . . : gateway.2wire.net

Ethernet adapter Wireless Network Connection 2:

        Media State . . . . . . . . . . . : Media disconnected
        Description . . . . . . . . . . . : Cisco Aironet 802.11a/b/g Wireless A
        Physical Address. . . . . . . . . : 00-40-96-AF-3F-DF

Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix  . : gateway.2wire.net
        Description . . . . . . . . . . . : Broadcom NetXtreme 57xx Gigabit Cont
        Physical Address. . . . . . . . . : 00-0F-1F-E2-B3-A3
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . :
        Subnet Mask . . . . . . . . . . . :
        Default Gateway . . . . . . . . . :
        DHCP Server . . . . . . . . . . . :
        DNS Servers . . . . . . . . . . . :
        Lease Obtained. . . . . . . . . . : Thursday, March 10, 2011 1:52:37 PM
        Lease Expires . . . . . . . . . . : Friday, March 11, 2011 1:52:37 PM

C:\Documents and Settings\User2>

Is it me or should the ip address of 192.168.1.X not match 192.168.10.X in terms of being in the same ip range

The computer I am connecting to is a windows 2003 server that is not part of a domain, none of the workstations are part of the domain either. I have added a user account user2 to the server and workstation and with the same password. I can see the shares and access them via ip address by going in my windows explorer but can't access by computer name

here is how the router is configured

Router/Gateway Address
Subnet Mask
Private Network DHCP Info  Range –
Allocated 2
Remaining 49

Here is what is in use as taken from router

Device Interface MAC Address IP Address
jdgx280 Port 4 00:0f:1f:e2:b3:a3 Device Details  
unknown00C09F38CD3E Port 4 00:c0:9f:38:cd:3e Device Details  Edit Name  
unknownE0CB4EA71A62 Port 4 e0:cb:4e:a7:1a:62 Device Details  Edit Name  
unknown0024E82183D2 Port 4 00:24:e8:21:83:d2 Device Details  Edit Name  
unknown000D569FB76C Port 4 00:0d:56:9f:b7:6c Device Details  Edit Name  

Question by:FASTECHS

Accepted Solution

discgman earned 668 total points
ID: 35099213
Why are the computers not part of the domain or same workgroup? Is it possible to add them to the group so at least they can talk to each other a bit easier? Anyway you can try one workstation and the file server and see if it helps?
LVL 18

Assisted Solution

by:Andrej Pirman
Andrej Pirman earned 668 total points
ID: 35099310

IP addresses 192.168.1.x and 192.168.10.x are in the subnet, defined by SUBNET MASK, which in your case is This subnet mask covers all IP addresses in range 192.168.x.x

Why your clients cannot access shares by name or IP?
Most probably the reason is in DNS server. I see it's pointing DNS to, which is your ROUTER, not the server!
I suggest you change:
- configure DHCP to deliver the following IP as PRIMARY DNS server to clients: (which is your SERVER, right?), and as secondary DNS you may enter either your router's IP, or your ISP's public DNS
- then setup DNS server role on your server, set it up to work with DHCP, and configure FORWARDERS. As forwarder DNS you may enter either your router's IP, or your ISP public DNS servers
- check it up that your new DNS server has A-records for itself (SERVERNAME pointing to
- you may run IPCONFIG /FLUSHDNS on server and clients to clear DNS cache

So, when your client will try to access \\SERVERNAME, it will first go to client's internal DNS cache to lookup IP for SERVERNAME. Since we cleared cache, it will go next step, to WINS resolver. If WINS is setup (under DHCP) to point to, then name is resolved.
If not, it will go to DNS server, configured on client NIC adapter. Since you changed DHCP settings to deliver your SERVER's IP as DNS, client's query will go t0 and ask:
"Hey, do you know on which IP is SERVERNAME located?"
And will lookup into its own DNS A-records, and will answer:
"Yes, I know. SERVERNAME is located on IP"
this response will then travel back to client and redirect to proper IP.

the other part:
If your client is having problems accessing server via IP, then check on client:
- is client a member of the same WORKGROUP as server?
- does client have "File and Printer Sharing" enabled under LAN connection properties?
- does client get TCP/IP settings from DHCP? If not, meaning it is static IP, make sure it has subnet mask entered properly, that is
- check under FIRWALL if "windows Networking" aka ports 139 and 445 are opened for local network AND LOCAL SUBNET

LVL 13

Assisted Solution

kdearing earned 664 total points
ID: 35100547
Sounds like you have 2 DHCP servers on the network.
Someone has installed another router (probably a basic wireless router from linksys, etc)

Featured Post

Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

This article explains the fundamentals of industrial networking which ultimately is the backbone network which is providing communications for process devices like robots and other not so interesting stuff.
LinkedIn blogging is great for networking, building up an audience, and expanding your influence as well. However, if you want to achieve these results, you need to work really hard to make your post worth liking and sharing. Here are 4 tips that ca…
In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're interested in additional methods for monitoring bandwidt…
Michael from AdRem Software outlines event notifications and Automatic Corrective Actions in network monitoring. Automatic Corrective Actions are scripts, which can automatically run upon discovery of a certain undesirable condition in your network.…

607 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question