Screwy Network Issue - Help Please

[crabig]

OK, first things first. Windows Server is not my strong suit. When I first installed this setup, 18 months ago, all was working fine, but I had someone working for me to do the server setup, and all the clients were on XP.

Over the last two weeks, I have changed all the XP machines over to Windows 7 Professional.

There are four regular clients, one Windows 7 machine that is acting as a file server (everything is in the \Users\Public\Documents directory).

One machine running Server 2008 R2.

I am having an issue with the machines showing up in the Network Places under My Computer. The server and File server don't even see themselves in the network listing, and as far as the rest go, I have listed them below.

We have Server, File Server, and Machines A-D.

Server sees Machine B & Machine C
File Server sees Machine A, Machine B, & Machine C
Machine A sees itself, Machine B, Machine C, & Machine D
Machine B sees itself, Machine A, Machine C, & Machine D
Machine C sees itself, Machine A, Machine B, & Machine D
Machine D sees itself, Machine A, Machine B, & Machine C

The Server is the primary DNS for all other machines.

I can ping, and connect via Computer Name, so DNS is functional. I just can't see all the machines in the Network View. Also, there are two folders on the File Server that are shared amongst all users. One is Misc. Data, and the other is a Scans folder that files from their printer/scanner write to. If I enter the full path manually to map the network drives, the will connnect, but drop off after a while. I cannot Browse the network for them because the Server and File Server do not show up in the Network List.

I'm at a bit of a loss here on what may be going on, and would love an assist from some of the more knowledgeable network folks on the forum.

Thanks in advance.

 

[YeOldeStonecat]

Lets get some more details here...

First....is the server running active directory...meaning was DCPROMO run on it to make it a domain controller, and install DNS services?

If "no"...it is running in workgroup mode, basically it's just a workstation much like Windows 7 Professional. And we'll have to look at other approaches. Hopefully the answer is "no".

If "yes"...I need a few other questions answered.
*What exact TCP/IP settings does the server have for itself...IP4.
*Have the workstations been properly "joined to the domain"? Are they logging into the domain? Confirm not a local login.
*Is the server running DHCP? If so...what is it handing out to the clients? If not....if a router is running DHCP...fix that...get the router out of that job, let the server do its job, which is "run the network". DHCP is one of those things it should do, makes for better communication across active directory.
*IPCONFIG /ALL at a workstation...what is the output for IP4

A very old guide I wrote back in the server 03/early XP days...but most of it still holds true...
http://www.speedguide.net/articles/server-based-network-guide-1660

 

[Markverhyden]

Do you have network discovery turned on for the Server and File Server? Control Panel>Network and Sharing Center>Advanced sharing settings.

 

[Moltuae]

I am having an issue with the machines showing up in the Network Places under My Computer.

Why are you relying on them showing up in Network Places?

Just connect to them directly: \\COMPUTER_NAME, or better still \\IP_ADDRESS (assuming you've configured static IPs for them).

If I enter the full path manually to map the network drives, the will connnect, but drop off after a while.

Do they drop off after a reboot?

I never rely on mapping -- I find it very unreliable. After a reboot, Windows often attempts to remap the drive before the network connection is properly established. I always script it instead, with something like this:

@echo off

SET ROUTER=192.168.0.1

:: Wait for the LAN connection to be established
:checknet
Ping %ROUTER% -n 1 -w 1000 >nul
if errorlevel 1 (
	goto :checknet
)


:: Remap network folders
net use X: "\\192.168.0.200\Shared_01" /user:user_name password /persistent:no
net use Y: "\\192.168.0.200\Shared_02" /user:user_name password /persistent:no
net use Z: "\\192.168.0.200\Shared_03" /user:user_name password /persistent:no

The '/persistent:no' helps prevent the annoying "Windows could not reconnect all drives" error at login.

 

[crabig]

Lets get some more details here...


http://www.speedguide.net/articles/server-based-network-guide-1660

Yes, the server is running as domain controller. It was before the workstations were upgraded.

Running IP v4. Was going to switch over to v6, but not until I get all other issues straight.
Workstations are logging into the domain. I've actually disabled the local logins, as that caused a few messes when we first set this up on XP.
Server is not running DHCP. All machines on the network have static addresses.

Output from ipconfig /all:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Administrator>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : FILES
Primary Dns Suffix . . . . . . . : putchallc.net
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : putchallc.net

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme 57xx Gigabit Controlle
r
Physical Address. . . . . . . . . : 00-19-B9-1F-32-28
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::3c95:c105:9765:6f40%11(Preferred)
IPv4 Address. . . . . . . . . . . : 202.20.66.194(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.192
Default Gateway . . . . . . . . . : 202.20.66.254
DHCPv6 IAID . . . . . . . . . . . : 234887609
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-F8-6C-75-00-19-B9-1F-32-28

DNS Servers . . . . . . . . . . . : 202.20.66.193
8.8.4.4
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{461E30B2-E765-468E-84DD-100472F292BF}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter 6TO4 Adapter:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2002:ca14:42c2::ca14:42c2(Preferred)
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 202.20.66.193
8.8.4.4
NetBIOS over Tcpip. . . . . . . . : Disabled

C:\Users\Administrator>

 

[crabig]

Do you have network discovery turned on for the Server and File Server? Control Panel>Network and Sharing Center>Advanced sharing settings.

I have made sure Network Discovery is on for all workstations.

 

[jbartlett323]

Yes, the server is running as domain controller. It was before the workstations were upgraded.

Running IP v4. Was going to switch over to v6, but not until I get all other issues straight.
Workstations are logging into the domain. I've actually disabled the local logins, as that caused a few messes when we first set this up on XP.
Server is not running DHCP. All machines on the network have static addresses.

*snip*
Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme 57xx Gigabit Controlle
r
Physical Address. . . . . . . . . : 00-19-B9-1F-32-28
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::3c95:c105:9765:6f40%11(Preferred)
IPv4 Address. . . . . . . . . . . : 202.20.66.194(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.192
Default Gateway . . . . . . . . . : 202.20.66.254
DHCPv6 IAID . . . . . . . . . . . : 234887609
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-F8-6C-75-00-19-B9-1F-32-28

DNS Servers . . . . . . . . . . . : 202.20.66.193
8.8.4.4
NetBIOS over Tcpip. . . . . . . . : Enabled

*snip*

Ok, first as StoneCat said, get everything running DHCP. Unless there is a really good reason not to (like all workstations are servers and have to be accessed as such, or a really screwy net config like at my local UPS Store) it will help with internal discovery.

Next, what kind of an IP schema is that? Looks External, definitely not the standard interanl 192's, 10's, or 172 networks. Might look into that, although I dont remember the subnetting specifics...

And now, DNS server.... Should only be pointed at the local server (or 127.0.0.1), no secondary of Google's externals. The DNS server should relay to Google's external (or whatever your perfferred DNS server).

As for the actual problem, when the mapped drives disconnect, are you getting the little red "x" and assuming they lost connection, or are you actually clicking them and getting "Location Not Found". I assume the latter, but I have to ask as I have known too many people to rely on that lying red "x" that usually means nothing at all.... I never, ever depend on Network Discovery either, as it has always had faults, issues, and otherwise crappy usage. Mapping drives, or UNC shortcuts is the only way to go in a Domain environment.

Oh, and your already running IPv6, says so right up there^ If you didn't specifically disable it on all workstation (or via Group Policy) it is used by default on all Vista and newer windows OS's...

 

[YeOldeStonecat]

IPv4 Address. . . . . . . . . . . : 202.20.66.194(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.192
Default Gateway . . . . . . . . . : 202.20.66.254


DNS Servers . . . . . . . . . . . : 202.20.66.193
8.8.4.4

Got me scratching my head there. And making me do a whole bunch of

and again.
That's a public IP address. Although with a /29 subnet...small range...but...weird. Not the usual private range.
A Windows server...a domain controller...on a public IP like that (if it is on one).

First thing I'd be doing is a data backup, wipe, fresh rebuild, all new passwords for all user accounts.

Where's the NAT? The private IP range for the network?

Is this server multi-homed? (if so..second NIC should have show up in the ipconfig info).

I notice a trend towards a block of public IPs...noting the default gateway. And noticing the DNS is 1x number different (last octet).

As stated above...a domain controller should only look at itself for DNS...nothing else...except certain cases with additional DCs on the same LAN..but even then sites 'n services should do it.

 

[Markverhyden]

I have made sure Network Discovery is on for all workstations.

By workstations does that include the Server 2008 and the Windows 7 file sharing box?

Also, a bit of advice that I always use. Never publish the public IP's of equipment you are responsible for.

Looks like YeOldeStonecat commented on the other networking points.

 

[crabig]

Ok, first as StoneCat said, get everything running DHCP. Unless there is a really good reason not to (like all workstations are servers and have to be accessed as such, or a really screwy net config like at my local UPS Store) it will help with internal discovery.

The accounting package they are running requires static IP addresses for all workstations.

Next, what kind of an IP schema is that? Looks External, definitely not the standard interanl 192's, 10's, or 172 networks. Might look into that, although I dont remember the subnetting specifics...

The IP schema was setup by the Server technician I hired to install the server. It worked fine for a year and a half before this upgrade.

And now, DNS server.... Should only be pointed at the local server (or 127.0.0.1), no secondary of Google's externals. The DNS server should relay to Google's external (or whatever your perfferred DNS server).

So let me get this straight, on the DC, and on the workstations, the only DNS server should be the DC?

As for the actual problem, when the mapped drives disconnect, are you getting the little red "x" and assuming they lost connection, or are you actually clicking them and getting "Location Not Found". I assume the latter, but I have to ask as I have known too many people to rely on that lying red "x" that usually means nothing at all.... I never, ever depend on Network Discovery either, as it has always had faults, issues, and otherwise crappy usage. Mapping drives, or UNC shortcuts is the only way to go in a Domain environment.

Correct. When I click on the mapped drive with the red X showing, I get "Location Not Found". If I right click and disconnect it, I can re-map it in a few seconds, but I don't want to be doing that on a daily basis, if I can help it.

Oh, and your already running IPv6, says so right up there^ If you didn't specifically disable it on all workstation (or via Group Policy) it is used by default on all Vista and newer windows OS's...

Correct. I should have stated that I have not actively done anything to setup IPv6.

Thanks for the help. I've done this type thing on UNIX servers for years, but Windows Server is a whole new ball game.

 

[crabig]

Got me scratching my head there. And making me do a whole bunch of

and again.
That's a public IP address. Although with a /29 subnet...small range...but...weird. Not the usual private range.
A Windows server...a domain controller...on a public IP like that (if it is on one).

First thing I'd be doing is a data backup, wipe, fresh rebuild, all new passwords for all user accounts.

Where's the NAT? The private IP range for the network?

Is this server multi-homed? (if so..second NIC should have show up in the ipconfig info).

I notice a trend towards a block of public IPs...noting the default gateway. And noticing the DNS is 1x number different (last octet).

As stated above...a domain controller should only look at itself for DNS...nothing else...except certain cases with additional DCs on the same LAN..but even then sites 'n services should do it.

This is a private IP range. The public address is stored only on the Uverse box that connects to the outside world. The guy I hired to setup this server a year and a half ago chose the internal IP range.

 

[YeOldeStonecat]

So what is 202.20.66.193 ? I know you called it DNS...but physically..what is at that IP address?
Same question for 202.20.66.254. (what you called the gateway).
I'm thinking the UVerse gateway is just doing public IP passthrough.

Never ran into an accounting package that required static IPs from the clients...and I've done a lottt of different accounting packages. But you can still do DHCP reservations from the server so the clients always get the same IP.

Can you post an IPCONFIG /ALL from a workstation?

 

[jbartlett323]

This is a private IP range. The public address is stored only on the Uverse box that connects to the outside world. The guy I hired to setup this server a year and a half ago chose the internal IP range.

Um, no its not. Your Server guy didn't do it right. see wikipedia: http://en.wikipedia.org/wiki/Private_network
192'2, 10's, and 172's are private ranges, all else are public. For a year and a half, your client has been lucky no one on the net has used those addy's, else things would be really screwy. Like StoneCat said, I bet its just doing Public IP Passthrough.

Yes, your Servers and workstations should only point to the DC for DNS, as DNS is a requirement for AD to work correctly, and using your server as an internal DNS cache only makes sense.

I would be interested as to what your DNS and Gateway physically are also.

I have never encountered an accounting software that requires static's either. And where I'm sure I have seen nowhere near as many as StoneCat, I have seen a more than a couple. Can we get a brand name for that software, so we all know what to avoid in the future?

And as for your mapped drive problem, have you tried having the mappings deleted and remapped via a login script? Sometimes when stuff does this, refreshing the connection is all you have to do, and if it auto-maps every morning, then it refreshes regularly. Also, if you set a login script, all they have to do if the drive is lost is logoff/logon or reboot to get em back. Not a great solution, true, but good work-around for the short term, and good to have setup going forward too.

 

[Markverhyden]

FYI there are some software packages that require a public IP address on the server. Not many but I have run into that on occasion. Had to do with MAC address binding for security.

 

[YeOldeStonecat]

FYI there are some software packages that require a public IP address on the server. Not many but I have run into that on occasion. Had to do with MAC address binding for security.

I've seen some software that binds use accounts to the MAC address of the workstations...yeah. (old versions of Club Connect golf resort software for example).

AT&T "gateways" have the last octet as .254. notice what this setup has from his IPCONFIG.
DNS...name resolution...likely drive mapping issues. may work sometimes cuz it's falling back to broadcasts. Workstations should only see the IP of domain controller(s) for their DNS server. Domain Controller itself must look at itself for DNS. DNS is the foundation of Active Directory. Improper setup of IP addressing on a network...specifically DNS...and your active directory is broken, the whole house falls down without that foundation.