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

Ok, so when you are on a workstation and you go to \\knight-tech\ you don't
see anything?

or you should see:

\\knight-tech\share1
\\knight-tech\share2
\\knight-tech\share3

Now from the server if you type \\workstation_name\ you should see what ever
shares you have created for example:

\\workstation_name\Knight_memos
\\workstation_name\Knight_Projects
etc.

I read some of your post to Doug and it seems like you are a little unclear
on the difference between some of the products (Server, XP Pro, XP Home,
etc). While for the most part the differences are not that much it's
important to understand as each is designed for a type of use in mind.

Server is designed as a platform for delivering services (www, FTP, File &
Print, Streaming Media and SECURITY). I capitalized security b/c aside from
performance tuning to provide services, providing an extensible security
platform is the primary role of a server compared to a workstation with a
file share.

A quick note on the difference between a Domain vs. a Workgroup, in a domain
all computers share a common security infrastructure (Active Directroy) where
accounts (computer and user) are centralized and accessible on anywhere in
the domain. In a workgroup, security accounts computer and users are only
exist locally and security is managed on each computer, this is fine if you
have 5 XP workstations in a workgroup, but problematic if you have 500 in an
office building.

Workstation (XP Pro & Home Ed.) is designed to be a rich multimedia and
application environment with broad support for a variety of devices. Desktop
applcation performance is at its peak here but network operations and
background processes are not as efficient.

The difference between XP Pro and XP Home, well I'm probably not the guy to
best explain it but it is my understanding that it has more to do with
licensing of "enterprise" feaures than anything. For instance XP Home Ed.
does not include the integrated terminal services CAL the Pro includes, what
else is different I couldn't really say.

Now as to your seeing MSHOME in the Network Neighborhood that your XP
workstation in a workgroup, so I think that answers my question as to whether
its in a domain or not.
--
James E. Price III
Fairway Consulting Group, Inc.
O: 954-727-5126
C: 305-970-4902
E: jprice@xxxxxxxxxx
W: www.fcgroup.us


"Knight Technologies" wrote:

> 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: Paradigms II
    ... > are not about trying to circumvent security. ... > (server or workstation); however, they can be easily adapted to any other ... > to have at least a vague idea what security, and a secure environment, ...
    (comp.security.misc)
  • Re: Event ID 5719: No Windows NT or Windows 2000 Domain Controller is available for domain .
    ... In my experience what you have done with security policy should ... The workstation gets its networking information from DHCP that, ... updates DNS. ... I don't believe the problem to be at the server end though. ...
    (microsoft.public.win2000.security)
  • Re: Re-Post - "the trust relationship between this workstation and
    ... There were no logged events in either the DC or workstation. ... DC/DNS Server - DCDiag ... Attr: subschemaSubentry ... only problem is adding a new user account on the station. ...
    (microsoft.public.windows.server.active_directory)
  • Re: "Classic logon" screen in XP does not remeber the user name
    ... I went to the workstation. ... does not show up on the server when I log onto the ... When you are done configuring Local Security Policy run the ... "Local security policy does not allow interactive login on this ...
    (microsoft.public.windowsxp.security_admin)