RE: Can't see other computers/nodes on network!

Ok, the first thing I see is that the server isn't using the same DNS server
as the workstation, Server is using 127.0.0.1 and the workstation is using
192.168.0.10. Now I'm guessing that the reason you can still browse the
Internet on the server is that during the domain setup it setup DNS on the
server itself and it's probably configured to forward to either 192.168.0.10
or something on the Internet.

Yes, 192.168.0.10 which is the router, and the router forwards to the
appropriate remote ISP DNS servers for proper resolve.

Is the workstation a member of the same domain as the server (knight-tech2)?
Not sure what you mean there.

Do you have 2 NICs in the server by any chance, if not then no big deal?
Just 1.

You can also probable ping and get some degree of name resolution b/c you're
on a flat LAN meaning that everything on the 192.168.0.0/24 network can
broadcast for NetBIOS and they will get a response b/c there isn't anything
to stop them. Not a bad thing but not ideal either.

I understand that, I normally turn off any unused processes and features to
improve security and performance unless while troubleshooting.

In general terms the way this should work is that your server(s) provide
pretty much all your network services except (switching, routing (unless your
using ISA or RRAS)), so you want to configure DNS, DHCP (and WINS if you
really need it, if you are AD and W2K or higher you shouldn't need WINS). So
a client gets DHCP from the server and the DHCP info should include:

1) Default GW
2) DNS Server

The DHCP and DNS is handled via the router which has DHCP server built-in,
this is how the clients get their internal/LAN/private network IP address
assignments. 192.168.0.100, 192.168.0.101, etc.

Try creating a shared printer or share a directory and see if you can see
that by browsing \\servername\

This is exactly the problem I am trying to find solution for, I have folders
shared and can see them on the main server, however, the clients/workstations
cannot see the shares on the server, likewise the computers do not show up in
network neighborhood.

In other words, on server I see this:
knight-tech
knight-tech2
X:\Shared Folder
Y:\Shared Folder2
Z:\Shared Folder3

On client/workstation I see this:
Mshome
.

Relevant Pages

  • Re: Problem connection XP SP2 Workstation after installing SBS 2k3
    ... > server are pointing to the SBS internal IP address of the only DNS server. ... please refer to the following Microsoft ... > | Subject: Re: Problem connection XP SP2 Workstation after installing SBS ...
    (microsoft.public.windows.server.sbs)
  • Re: HP ML350 G5 SERVER + WINDOWS SBS 2003 R2 SP2
    ... This is the ipconfig from another workstation in the network. ... If you see the first attached file, it was the server and another ... workstation DHCP config, ...
    (microsoft.public.windows.server.sbs)
  • Re: DHCP setup
    ... It *could* be related to DNS since a mapped drive will probably depend on the DNS server to resolve a server name... ... Access to servers, using mapped drives, copy data etc. ... On the DHCP server console check the scope options, ...
    (microsoft.public.win2000.active_directory)
  • Re: Cannot get access to router on SBS server
    ... point the DNS server setting to the IP of the SBS ... calling CNetCommit::ValidateFulltimeConnectionProperties. ... Call to Reading web publishing selection returned ok. ...
    (microsoft.public.windows.server.sbs)
  • Re: DHCP not working right after server restore from backup
    ... The whole problem seemed to be linked to old information in both DHCP and ... But from your message (the part about the DNS) I got the bright idea ... Make sure you do not test from just one workstation. ... from the server then I know thew network is goofed up. ...
    (microsoft.public.windows.server.sbs)