No Connection on some xp clients

G

Guest

We have a small network of 30 users, 8 are Winxp, these clients have been
connecting to a NT4(sp6a) server for awhile now.
2 weeks ago, I added a W2K standard server. I set it up to handel DNS
(forwarded to my isp) and i set it up to be the dhcp server (shut this
service down on the NT4 server). Everything ran fine for a few weeks, and
today two clients no longer see the NT4 server. they can ping it, but no
other traffic. I added Netbui to these machines and still no change.

Any other suggestions?

Chris
 
H

Herb Martin

Chris said:
We have a small network of 30 users, 8 are Winxp, these clients have been
connecting to a NT4(sp6a) server for awhile now.
2 weeks ago, I added a W2K standard server. I set it up to handel DNS
(forwarded to my isp) and i set it up to be the dhcp server (shut this
service down on the NT4 server). Everything ran fine for a few weeks, and
today two clients no longer see the NT4 server. they can ping it, but no
other traffic.

What does "see" mean? Most people mean "cannot
see it in Network Neighborhood which is NEVER a
DNS issue. That's NetBIOS (not NetBEUI) and usually
a missing WINS server.

If you have more than one subnet and you mean browsing
is not working then it is the lack of WINS server (or
an incorrect configuration on some of the WINS clients).

ALL machine (including "servers") must be WINS clients
if you use a WINS server for this.

Things to check:

1) Clients using STRICTLY the internal DNS server
(and do not have the ISP listed -- the forwarding takes
care of Internet resolution.)

2) NT server is registered with the DNS (manually or
automatically) in the correct zone

3) NT server and all machines use the same workgroup
name (until you have a domain then they use the
same NetBIOS workgroup/domain name.)

4) Can you ping? By name or just by number?
Name failure argues for a name resolution problem.

5) Can you do a direct "net view" and/or "net use" from
the command line -- by name or only by number?
I added Netbui to these machines and still no change.

Odd, but this would just hide the real problem had it
worked.

This argues for the WINS/NetBIOS issue too (by the way)
since NetBEUIE is NOT routable -- on a single subnetwork,
IP and NetBEUI work about the same for name resolution
etc.
 
G

Guest

"See" translates to does not connect to. Either printers or shares.

I dill look at the wins and see if there are issues there.

Chris
 
G

Guest

OK,
It appears to be on the NT4 side, this server looks to two wins servers.
both of these servers have the names and correct IP addresses of the failed
clients listed. However when I try to search in Network Neighborhood off of
the NT4 desktop, it does not find the workstations.

I can ping in both directions using the ip address.

You asked about the error, if you try a search from My Network Places, you
get no results when you double click on a mapping you get a message returned
that says the path cannot be found.
 
H

Herb Martin

Chris said:
OK,
It appears to be on the NT4 side, this server looks to two wins servers.
both of these servers have the names and correct IP addresses of the failed
clients listed. However when I try to search in Network Neighborhood off of
the NT4 desktop, it does not find the workstations.

But are the servers (anything offering shares) all listed?

I don't see you mention a Domain or DCs -- you cannot
browse across subnets without a DC -- if you have them
then the PDC (NT4) must be listed (be a WINS client
in it's own NIC properties) but realistically every
machine needs to be a WINS client, including the WINS
server etc.
I can ping in both directions using the ip address.

How about name? If not we are experiencing at least
some kind of Name Resolution problem.

You asked about the error, if you try a search from My Network Places, you
get no results when you double click on a mapping you get a message returned
that says the path cannot be found.

What mapping? Sounds like your NetBIOS name
resolution but DNS could be involved also.....

My bet is clients on the same subnet as a server
can connect (broadcast name resolution) and those
on the opposite subnet have the problem.

Since you can ping it is not a routing problem.
 
G

Guest

Herb Martin said:
But are the servers (anything offering shares) all listed?

Yes there are servers and workstations with shares that can be connected to
from here (winnt4 server network neighborhood)
I don't see you mention a Domain or DCs -- you cannot
browse across subnets without a DC -- if you have them
then the PDC (NT4) must be listed (be a WINS client
in it's own NIC properties) but realistically every
machine needs to be a WINS client, including the WINS
server etc.

There are no DC's All computers are in a single workgroup.
All pc's are in the same subnet.
All machines are wins clients, the WinNT 4 had an old wins server listed as
2nd, I updated that to the current ones. This did not fix the problem

How about name? If not we are experiencing at least
some kind of Name Resolution problem.

This may be a lead - I can ping by name from client to server. I cannot ping
by name from the WinNT4 server to the clients. Ping returns "bad ip address
clientname"
What mapping? Sounds like your NetBIOS name
resolution but DNS could be involved also.....

My bet is clients on the same subnet as a server
can connect (broadcast name resolution) and those
on the opposite subnet have the problem.

All computers are on the same subnet.
 
H

Herb Martin

But are the servers (anything offering shares) all listed?
Yes there are servers and workstations with shares that can be connected to
from here (winnt4 server network neighborhood)

Ok, well are there any with shares that are missing...
(No server shows up in browsing unless at least one
non-hidden share is made available...)
There are no DC's All computers are in a single workgroup.
All pc's are in the same subnet.
All machines are wins clients, the WinNT 4 had an old wins server listed as
2nd, I updated that to the current ones. This did not fix the problem

WINS is irrelevant in a single subnet network unless
reducing broadcasts is extremely important. (Most
small networks it doesn't matter much.)
This may be a lead - I can ping by name from client to server. I cannot ping
by name from the WinNT4 server to the clients. Ping returns "bad ip address
clientname"

Ok, we have an IP range or subnet mask problem
probably (ok it might be routing too but unlikely).

Sounds like the machines (while on the same physical
segment) have IP addresses from different (sub)networks.

Check all your IP addresses and subnet masks. Make
sure no machine is set to automatic unless you have
DHCP and then make sure it is getting an address.

Post here you IPCONFIG from a CLIENT and a SERVER
which have the problem when talking to each other.

Don't edit it -- cut and paste the text directly from the
cmd prompt:

ipconfig /all
 
G

Guest

Herb Martin said:
Ok, well are there any with shares that are missing...
(No server shows up in browsing unless at least one
non-hidden share is made available...)


WINS is irrelevant in a single subnet network unless
reducing broadcasts is extremely important. (Most
small networks it doesn't matter much.)


Ok, we have an IP range or subnet mask problem
probably (ok it might be routing too but unlikely).

Sounds like the machines (while on the same physical
segment) have IP addresses from different (sub)networks.

Check all your IP addresses and subnet masks. Make
sure no machine is set to automatic unless you have
DHCP and then make sure it is getting an address.

Post here you IPCONFIG from a CLIENT and a SERVER
which have the problem when talking to each other.

Don't edit it -- cut and paste the text directly from the
cmd prompt:

ipconfig /all

XP Client

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

Windows IP Configuration

Host Name . . . . . . . . . . . . : marketlap6138
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 3Com 3C920 Integrated Fast
Ethernet
Controller (3C905C-TX Compatible)
Physical Address. . . . . . . . . : 00-08-74-E2-E6-0B
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.0.1.30
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 10.0.0.1

C:\Documents and Settings\meteor>I could not figur out how to copy from the dos prompt on WinNT4:

so here:
ip address: 10.0.1.6
Subnet Mask 255.255.0.0
Gateway 10.0.0.1
primary wins 10.0.1.11
secondary Wins 10.0.1.8

If you can tell me how to capture from the dos prompt I will give it a go.

Chris
 
H

Herb Martin

If you can tell me how to capture from the dos prompt I will give it a go.

We will work with what is below, assuming you
made no significant typos (worst would be an
assumption about the subnet Mask where it read
on way and you unconsciously typed what you
expect -- I have done it and it is not that uncommon.)

But, for copying (if we or you need it in the future)
there are two ways:

1) Alt-space for the system menu (or click on the
left title bar box to get it.) Edit is down the
menu a bit (E), Mark and Copy but this is the
hard way even though it always works with
not setup.

2) Use that same system menu to bring up Properties,
and set the Options: Set QuickEdit mode and
likely Insert. While you are at it set your
scrollback screen buffer to >1000 lines on layout
and your colors to something decent in Colors,
e.g., bright yellow text on dark blue is most readable
for most people -- and it reminds you that you have
setup the command prompt.

Best is to perform actions #2 on the SHORTCUT or
save the settings for the "Shortcut that started this"
window. Nice thing about #1 is you can do it on
someone else's machine without prep.

XP Client
C:\Documents and Settings\meteor>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : marketlap6138
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 3Com 3C920 Integrated Fast
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.0.1.30
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 10.0.0.1
C:\Documents and Settings\meteor>
ip address: 10.0.1.6
Subnet Mask 255.255.0.0
Gateway 10.0.0.1
primary wins 10.0.1.11
secondary Wins 10.0.1.8

I don't see you DNS server settings -- whether
they are set to Internal DNS servers (if you have
them) or to external -- note it is always wrong
to mix the two settings on a single client...

The node type on the XP client implies you have
a WINS server, but it doesn't show the address(es).

The WINS server addresses on the other machine,
show TWO WINS servers so we must wonder if
all of the machines are set as clients AND if these
two WINS servers are REPLICATING.

This is my current guess (not replicating and/or
not all are set to the same two or set at all) since
you seem to have a Name resolution error, BUT
if you truly only have one subnet the BROADCAST
should eventually take over and resolve the server
names.

Ok, we really need the exact symptoms from the
same machines. (and you might as well cut and
paste the settings while you are at it since that
eliminates mistyping and the omission of important
info.)

Perform these tests as well (and report results):

ping servername
ping IP.adress.Of.Server
e.g.,: ping 10.0.1.6

net view \\Servername
net view \\IP.adress.Of.Server
e.g.,: net view \\10.0.1.6

You might also try nslookup IF you are using an
internal DNS server:

nslookup ServerName

(you may get a bogus DNS server error immediately
after the command (first first lines) but down below
you will get the (good) results or the real error.

That early error is an NSLookup artifact. Ignore it
(or just report the whole thing by pasting so we can
show you where the important stuff is.)
 
E

Eugene Taylor

You can also pipe the contents to a text file using the ipconfig >ip.txt
this will pipe the output to a txt file that you can then open using notepad
or your favorite editor.
 
G

Guest

OK - slight change:
The server I was on was old,and ready to be upgraded (to W2k). So we
installed a new server Everything is good with the XP clients now but.

Another older Citrix server cannot connect to the new NT server. The
problems seem to be the same as the issues from xpclient to winnt4.

So below are the test results you had suggested but from Citrix (apprisent)
and W2K (meteornt2).

Reports from Citrix Server

Windows NT IP Configuration

Host Name . . . . . . . . . : apprisent.mtr2.com
DNS Servers . . . . . . . . : 216.24.175.3
216.24.175.2
Node Type . . . . . . . . . : Hybrid
NetBIOS Scope ID. . . . . . : 1688
IP Routing Enabled. . . . . : Yes
WINS Proxy Enabled. . . . . : No
NetBIOS Resolution Uses DNS : No

Ethernet adapter El90x2:

Description . . . . . . . . : 3Com EtherLink PCI
Physical Address. . . . . . : 00-10-4B-C8-1E-0E
DHCP Enabled. . . . . . . . : No
IP Address. . . . . . . . . : 10.0.1.8
Subnet Mask . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . : 10.0.0.1
Primary WINS Server . . . . : 10.0.1.6
Secondary WINS Server . . . : 10.0.1.150


C:\WTSRV\Profiles\ADMINI~1>ping meteornt2

Pinging meteornt2 [10.0.1.6] with 32 bytes of data:

Reply from 10.0.1.6: bytes=32 time<10ms TTL=128
Reply from 10.0.1.6: bytes=32 time<10ms TTL=128
Reply from 10.0.1.6: bytes=32 time<10ms TTL=128
Reply from 10.0.1.6: bytes=32 time<10ms TTL=128


C:\WTSRV\Profiles\ADMINI~1>ping 10.0.1.6

Pinging 10.0.1.6 with 32 bytes of data:

Reply from 10.0.1.6: bytes=32 time<10ms TTL=128
Reply from 10.0.1.6: bytes=32 time<10ms TTL=128
Reply from 10.0.1.6: bytes=32 time<10ms TTL=128
Reply from 10.0.1.6: bytes=32 time<10ms TTL=128

C:\WTSRV\Profiles\ADMINI~1>net view \\meteornt2
System error 51 has occurred.

The remote computer is not available.

C:\WTSRV\Profiles\ADMINI~1>net view \\10.0.1.6
System error 53 has occurred.

The network path was not found.





Meteornt2

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

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : meteornt2
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Netelligent 10/100TX PCI
Embedded UT
P/AUI Controller
Physical Address. . . . . . . . . : 00-50-8B-55-2D-02
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.0.1.6
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 10.0.0.1
DNS Servers . . . . . . . . . . . : 216.24.175.3
216.24.175.2
Primary WINS Server . . . . . . . : 10.0.1.6


C:\Documents and Settings\Administrator>ping apprisent

Pinging apprisent [10.0.1.8] with 32 bytes of data:

Reply from 10.0.1.8: bytes=32 time<10ms TTL=128
Reply from 10.0.1.8: bytes=32 time<10ms TTL=128
Reply from 10.0.1.8: bytes=32 time<10ms TTL=128
Reply from 10.0.1.8: bytes=32 time<10ms TTL=128

Ping statistics for 10.0.1.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Documents and Settings\Administrator>ping 10.0.1.8

Pinging 10.0.1.8 with 32 bytes of data:

Reply from 10.0.1.8: bytes=32 time<10ms TTL=128
Reply from 10.0.1.8: bytes=32 time<10ms TTL=128
Reply from 10.0.1.8: bytes=32 time<10ms TTL=128
Reply from 10.0.1.8: bytes=32 time<10ms TTL=128

Ping statistics for 10.0.1.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Documents and Settings\Administrator>net view \\apprisent
System error 53 has occurred.

The network path was not found.

C:\Documents and Settings\Administrator>net view \\10.0.1.8
System error 53 has occurred.

The network path was not found.

Sorry about the change in direction.

Chris
 
H

Herb Martin

C:\WTSRV\Profiles\ADMINI~1>net view \\meteornt2
System error 51 has occurred.

The remote computer is not available.

There is such an error in Win2000/XP for DNS names
of exactly 16 characters (doesn't apply here) but that
can be fixed by SERVICE PACKS.

But this does bring up the question of what service
pack you have deployed? Since you are on the
Internet it is essential that you apply (practically)
ever service pack and hot fix.

You might also have disable NetBIOS to cause this
error but I doubt you would do that (and so seldom
mention this.)
C:\WTSRV\Profiles\ADMINI~1>net view \\10.0.1.6
System error 53 has occurred.

The network path was not found.

That looks like the Server service is NOT running.

And this KB seems to agree:
http://support.microsoft.com/default.aspx?scid=kb;en-us;259878

This would not be odd if you turned it off (it's own
by default) or if the W2K (meteornt2) is running a
firewall which prevents the Server service ports
from being available to clients.

You can check the first easily by typing at the CMD
prompt:

Net Start

(on meteornt2) and looking for "Server" (simply
that) in the lower part or by checking in your Services
console.

You might also type "Net Share" and prove to yourself
that you have SOMETHING shared -- machines do not
appear in browsers unless at least one non-hidden share
is offered.

Name resolution is not a problem for you apparently
since you pings work fine by Name.

--
Herb Martin


Chris said:
OK - slight change:
The server I was on was old,and ready to be upgraded (to W2k). So we
installed a new server Everything is good with the XP clients now but.

Another older Citrix server cannot connect to the new NT server. The
problems seem to be the same as the issues from xpclient to winnt4.

So below are the test results you had suggested but from Citrix (apprisent)
and W2K (meteornt2).

Reports from Citrix Server

Windows NT IP Configuration

Host Name . . . . . . . . . : apprisent.mtr2.com
DNS Servers . . . . . . . . : 216.24.175.3
216.24.175.2
Node Type . . . . . . . . . : Hybrid
NetBIOS Scope ID. . . . . . : 1688
IP Routing Enabled. . . . . : Yes
WINS Proxy Enabled. . . . . : No
NetBIOS Resolution Uses DNS : No

Ethernet adapter El90x2:

Description . . . . . . . . : 3Com EtherLink PCI
Physical Address. . . . . . : 00-10-4B-C8-1E-0E
DHCP Enabled. . . . . . . . : No
IP Address. . . . . . . . . : 10.0.1.8
Subnet Mask . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . : 10.0.0.1
Primary WINS Server . . . . : 10.0.1.6
Secondary WINS Server . . . : 10.0.1.150


C:\WTSRV\Profiles\ADMINI~1>ping meteornt2

Pinging meteornt2 [10.0.1.6] with 32 bytes of data:

Reply from 10.0.1.6: bytes=32 time<10ms TTL=128
Reply from 10.0.1.6: bytes=32 time<10ms TTL=128
Reply from 10.0.1.6: bytes=32 time<10ms TTL=128
Reply from 10.0.1.6: bytes=32 time<10ms TTL=128


C:\WTSRV\Profiles\ADMINI~1>ping 10.0.1.6

Pinging 10.0.1.6 with 32 bytes of data:

Reply from 10.0.1.6: bytes=32 time<10ms TTL=128
Reply from 10.0.1.6: bytes=32 time<10ms TTL=128
Reply from 10.0.1.6: bytes=32 time<10ms TTL=128
Reply from 10.0.1.6: bytes=32 time<10ms TTL=128

C:\WTSRV\Profiles\ADMINI~1>net view \\meteornt2
System error 51 has occurred.

The remote computer is not available.

C:\WTSRV\Profiles\ADMINI~1>net view \\10.0.1.6
System error 53 has occurred.

The network path was not found.





Meteornt2

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

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : meteornt2
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Netelligent 10/100TX PCI
Embedded UT
P/AUI Controller
Physical Address. . . . . . . . . : 00-50-8B-55-2D-02
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.0.1.6
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 10.0.0.1
DNS Servers . . . . . . . . . . . : 216.24.175.3
216.24.175.2
Primary WINS Server . . . . . . . : 10.0.1.6


C:\Documents and Settings\Administrator>ping apprisent

Pinging apprisent [10.0.1.8] with 32 bytes of data:

Reply from 10.0.1.8: bytes=32 time<10ms TTL=128
Reply from 10.0.1.8: bytes=32 time<10ms TTL=128
Reply from 10.0.1.8: bytes=32 time<10ms TTL=128
Reply from 10.0.1.8: bytes=32 time<10ms TTL=128

Ping statistics for 10.0.1.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Documents and Settings\Administrator>ping 10.0.1.8

Pinging 10.0.1.8 with 32 bytes of data:

Reply from 10.0.1.8: bytes=32 time<10ms TTL=128
Reply from 10.0.1.8: bytes=32 time<10ms TTL=128
Reply from 10.0.1.8: bytes=32 time<10ms TTL=128
Reply from 10.0.1.8: bytes=32 time<10ms TTL=128

Ping statistics for 10.0.1.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Documents and Settings\Administrator>net view \\apprisent
System error 53 has occurred.

The network path was not found.

C:\Documents and Settings\Administrator>net view \\10.0.1.8
System error 53 has occurred.

The network path was not found.

Sorry about the change in direction.

Chris




Herb Martin said:
go.

We will work with what is below, assuming you
made no significant typos (worst would be an
assumption about the subnet Mask where it read
on way and you unconsciously typed what you
expect -- I have done it and it is not that uncommon.)

But, for copying (if we or you need it in the future)
there are two ways:

1) Alt-space for the system menu (or click on the
left title bar box to get it.) Edit is down the
menu a bit (E), Mark and Copy but this is the
hard way even though it always works with
not setup.

2) Use that same system menu to bring up Properties,
and set the Options: Set QuickEdit mode and
likely Insert. While you are at it set your
scrollback screen buffer to >1000 lines on layout
and your colors to something decent in Colors,
e.g., bright yellow text on dark blue is most readable
for most people -- and it reminds you that you have
setup the command prompt.

Best is to perform actions #2 on the SHORTCUT or
save the settings for the "Shortcut that started this"
window. Nice thing about #1 is you can do it on
someone else's machine without prep.




I don't see you DNS server settings -- whether
they are set to Internal DNS servers (if you have
them) or to external -- note it is always wrong
to mix the two settings on a single client...

The node type on the XP client implies you have
a WINS server, but it doesn't show the address(es).

The WINS server addresses on the other machine,
show TWO WINS servers so we must wonder if
all of the machines are set as clients AND if these
two WINS servers are REPLICATING.

This is my current guess (not replicating and/or
not all are set to the same two or set at all) since
you seem to have a Name resolution error, BUT
if you truly only have one subnet the BROADCAST
should eventually take over and resolve the server
names.

Ok, we really need the exact symptoms from the
same machines. (and you might as well cut and
paste the settings while you are at it since that
eliminates mistyping and the omission of important
info.)

Perform these tests as well (and report results):

ping servername
ping IP.adress.Of.Server
e.g.,: ping 10.0.1.6

net view \\Servername
net view \\IP.adress.Of.Server
e.g.,: net view \\10.0.1.6

You might also try nslookup IF you are using an
internal DNS server:

nslookup ServerName

(you may get a bogus DNS server error immediately
after the command (first first lines) but down below
you will get the (good) results or the real error.

That early error is an NSLookup artifact. Ignore it
(or just report the whole thing by pasting so we can
show you where the important stuff is.)
 
G

Guest

Herb Martin said:
There is such an error in Win2000/XP for DNS names
of exactly 16 characters (doesn't apply here) but that
can be fixed by SERVICE PACKS.

But this does bring up the question of what service
pack you have deployed? Since you are on the
Internet it is essential that you apply (practically)
ever service pack and hot fix.

SP6 - I will do any hot fixes I can find.
You might also have disable NetBIOS to cause this
error but I doubt you would do that (and so seldom
mention this.)

I do not think I did - I see it bound to the Wins Client under the adaptor
bindings. Is there another place to see it?
That looks like the Server service is NOT running.

And this KB seems to agree:
http://support.microsoft.com/default.aspx?scid=kb;en-us;259878

This would not be odd if you turned it off (it's own
by default) or if the W2K (meteornt2) is running a
firewall which prevents the Server service ports
from being available to clients.

You can check the first easily by typing at the CMD
prompt:

Net Start

It is running - see output.

C:\Documents and Settings\Administrator>net start
These Windows 2000 services are started:

Alerter
Automatic Updates
COM+ Event System
Computer Browser
DHCP Client
DHCP Server
Distributed File System
Distributed Link Tracking Client
Distributed Transaction Coordinator
DNS Client
Event Log
File Server for Macintosh
IPSEC Policy Agent
License Logging Service
Logical Disk Manager
McAfee Framework Service
Messenger
Network Associates McShield
Network Associates Task Manager
Network Connections
NT LM Security Support Provider
Plug and Play
Print Server for Macintosh
Print Spooler
Protected Storage
Remote Access Connection Manager
Remote Procedure Call (RPC)
Remote Registry Service
Removable Storage
RunAs Service
Security Accounts Manager
Server
System Event Notification
Task Scheduler
TCP/IP NetBIOS Helper Service
Telephony
Terminal Services
UltraBac Management Service
UltraBac Scheduler
Windows Internet Name Service (WINS)
Windows Management Instrumentation
Windows Management Instrumentation Driver Extensions
Workstation

The command completed successfully.
(on meteornt2) and looking for "Server" (simply
that) in the lower part or by checking in your Services
console.

You might also type "Net Share" and prove to yourself
that you have SOMETHING shared -- machines do not
appear in browsers unless at least one non-hidden share
is offered.

I do see my shares listed when I run this command.
Name resolution is not a problem for you apparently
since you pings work fine by Name.

--
Herb Martin


Chris said:
OK - slight change:
The server I was on was old,and ready to be upgraded (to W2k). So we
installed a new server Everything is good with the XP clients now but.

Another older Citrix server cannot connect to the new NT server. The
problems seem to be the same as the issues from xpclient to winnt4.

So below are the test results you had suggested but from Citrix (apprisent)
and W2K (meteornt2).

Reports from Citrix Server

Windows NT IP Configuration

Host Name . . . . . . . . . : apprisent.mtr2.com
DNS Servers . . . . . . . . : 216.24.175.3
216.24.175.2
Node Type . . . . . . . . . : Hybrid
NetBIOS Scope ID. . . . . . : 1688
IP Routing Enabled. . . . . : Yes
WINS Proxy Enabled. . . . . : No
NetBIOS Resolution Uses DNS : No

Ethernet adapter El90x2:

Description . . . . . . . . : 3Com EtherLink PCI
Physical Address. . . . . . : 00-10-4B-C8-1E-0E
DHCP Enabled. . . . . . . . : No
IP Address. . . . . . . . . : 10.0.1.8
Subnet Mask . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . : 10.0.0.1
Primary WINS Server . . . . : 10.0.1.6
Secondary WINS Server . . . : 10.0.1.150


C:\WTSRV\Profiles\ADMINI~1>ping meteornt2

Pinging meteornt2 [10.0.1.6] with 32 bytes of data:

Reply from 10.0.1.6: bytes=32 time<10ms TTL=128
Reply from 10.0.1.6: bytes=32 time<10ms TTL=128
Reply from 10.0.1.6: bytes=32 time<10ms TTL=128
Reply from 10.0.1.6: bytes=32 time<10ms TTL=128


C:\WTSRV\Profiles\ADMINI~1>ping 10.0.1.6

Pinging 10.0.1.6 with 32 bytes of data:

Reply from 10.0.1.6: bytes=32 time<10ms TTL=128
Reply from 10.0.1.6: bytes=32 time<10ms TTL=128
Reply from 10.0.1.6: bytes=32 time<10ms TTL=128
Reply from 10.0.1.6: bytes=32 time<10ms TTL=128

C:\WTSRV\Profiles\ADMINI~1>net view \\meteornt2
System error 51 has occurred.

The remote computer is not available.

C:\WTSRV\Profiles\ADMINI~1>net view \\10.0.1.6
System error 53 has occurred.

The network path was not found.





Meteornt2

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

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : meteornt2
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Netelligent 10/100TX PCI
Embedded UT
P/AUI Controller
Physical Address. . . . . . . . . : 00-50-8B-55-2D-02
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.0.1.6
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 10.0.0.1
DNS Servers . . . . . . . . . . . : 216.24.175.3
216.24.175.2
Primary WINS Server . . . . . . . : 10.0.1.6


C:\Documents and Settings\Administrator>ping apprisent

Pinging apprisent [10.0.1.8] with 32 bytes of data:

Reply from 10.0.1.8: bytes=32 time<10ms TTL=128
Reply from 10.0.1.8: bytes=32 time<10ms TTL=128
Reply from 10.0.1.8: bytes=32 time<10ms TTL=128
Reply from 10.0.1.8: bytes=32 time<10ms TTL=128

Ping statistics for 10.0.1.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Documents and Settings\Administrator>ping 10.0.1.8

Pinging 10.0.1.8 with 32 bytes of data:

Reply from 10.0.1.8: bytes=32 time<10ms TTL=128
Reply from 10.0.1.8: bytes=32 time<10ms TTL=128
Reply from 10.0.1.8: bytes=32 time<10ms TTL=128
Reply from 10.0.1.8: bytes=32 time<10ms TTL=128

Ping statistics for 10.0.1.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Documents and Settings\Administrator>net view \\apprisent
System error 53 has occurred.

The network path was not found.

C:\Documents and Settings\Administrator>net view \\10.0.1.8
System error 53 has occurred.

The network path was not found.

Sorry about the change in direction.

Chris




Herb Martin said:
If you can tell me how to capture from the dos prompt I will give it a go.

We will work with what is below, assuming you
made no significant typos (worst would be an
assumption about the subnet Mask where it read
on way and you unconsciously typed what you
expect -- I have done it and it is not that uncommon.)

But, for copying (if we or you need it in the future)
there are two ways:

1) Alt-space for the system menu (or click on the
left title bar box to get it.) Edit is down the
menu a bit (E), Mark and Copy but this is the
hard way even though it always works with
not setup.

2) Use that same system menu to bring up Properties,
and set the Options: Set QuickEdit mode and
likely Insert. While you are at it set your
scrollback screen buffer to >1000 lines on layout
and your colors to something decent in Colors,
e.g., bright yellow text on dark blue is most readable
for most people -- and it reminds you that you have
setup the command prompt.

Best is to perform actions #2 on the SHORTCUT or
save the settings for the "Shortcut that started this"
window. Nice thing about #1 is you can do it on
someone else's machine without prep.


XP Client
C:\Documents and Settings\meteor>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : marketlap6138
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 3Com 3C920 Integrated Fast
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.0.1.30
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 10.0.0.1

C:\Documents and Settings\meteor>
ip address: 10.0.1.6
Subnet Mask 255.255.0.0
Gateway 10.0.0.1
primary wins 10.0.1.11
secondary Wins 10.0.1.8

I don't see you DNS server settings -- whether
they are set to Internal DNS servers (if you have
them) or to external -- note it is always wrong
to mix the two settings on a single client...

The node type on the XP client implies you have
a WINS server, but it doesn't show the address(es).

The WINS server addresses on the other machine,
show TWO WINS servers so we must wonder if
all of the machines are set as clients AND if these
two WINS servers are REPLICATING.

This is my current guess (not replicating and/or
not all are set to the same two or set at all) since
you seem to have a Name resolution error, BUT
if you truly only have one subnet the BROADCAST
should eventually take over and resolve the server
names.

Ok, we really need the exact symptoms from the
same machines. (and you might as well cut and
paste the settings while you are at it since that
eliminates mistyping and the omission of important
info.)

Perform these tests as well (and report results):

ping servername
ping IP.adress.Of.Server
e.g.,: ping 10.0.1.6

net view \\Servername
net view \\IP.adress.Of.Server
e.g.,: net view \\10.0.1.6

You might also try nslookup IF you are using an
internal DNS server:

nslookup ServerName

(you may get a bogus DNS server error immediately
after the command (first first lines) but down below
you will get the (good) results or the real error.

That early error is an NSLookup artifact. Ignore it
(or just report the whole thing by pasting so we can
show you where the important stuff is.)

--
Herb Martin




:

But are the servers (anything offering shares) all listed?

Yes there are servers and workstations with shares that can be
connected
to
from here (winnt4 server network neighborhood)

Ok, well are there any with shares that are missing...
(No server shows up in browsing unless at least one
non-hidden share is made available...)

There are no DC's All computers are in a single workgroup.
All pc's are in the same subnet.
All machines are wins clients, the WinNT 4 had an old wins server
listed
as
2nd, I updated that to the current ones. This did not fix the problem

WINS is irrelevant in a single subnet network unless
reducing broadcasts is extremely important. (Most
small networks it doesn't matter much.)

I can ping in both directions using the ip address.

How about name? If not we are experiencing at least
some kind of Name Resolution problem.

This may be a lead - I can ping by name from client to server. I
cannot
ping
by name from the WinNT4 server to the clients. Ping returns "bad ip
address
clientname"

Ok, we have an IP range or subnet mask problem
probably (ok it might be routing too but unlikely).

Sounds like the machines (while on the same physical
segment) have IP addresses from different (sub)networks.

Check all your IP addresses and subnet masks. Make
sure no machine is set to automatic unless you have
DHCP and then make sure it is getting an address.

Post here you IPCONFIG from a CLIENT and a SERVER
which have the problem when talking to each other.

Don't edit it -- cut and paste the text directly from the
cmd prompt:

ipconfig /all
 
G

Guest

Just another note.

There are common servers on the network that both (apprisent and meteornt2)
can access. I run net view //meteornt2a and I see the shares it offers.

from the run menu: I run: \\meteornt2a\support and I get that share to open
from each server.

Do yu think there is a problem with the names? (meteornt2 and meteornt2a) I
flipflopped the names when I made the change the old server was appended with
the "a".

Chris

Chris said:
Herb Martin said:
There is such an error in Win2000/XP for DNS names
of exactly 16 characters (doesn't apply here) but that
can be fixed by SERVICE PACKS.

But this does bring up the question of what service
pack you have deployed? Since you are on the
Internet it is essential that you apply (practically)
ever service pack and hot fix.

SP6 - I will do any hot fixes I can find.
You might also have disable NetBIOS to cause this
error but I doubt you would do that (and so seldom
mention this.)

I do not think I did - I see it bound to the Wins Client under the adaptor
bindings. Is there another place to see it?
That looks like the Server service is NOT running.

And this KB seems to agree:
http://support.microsoft.com/default.aspx?scid=kb;en-us;259878

This would not be odd if you turned it off (it's own
by default) or if the W2K (meteornt2) is running a
firewall which prevents the Server service ports
from being available to clients.

You can check the first easily by typing at the CMD
prompt:

Net Start

It is running - see output.

C:\Documents and Settings\Administrator>net start
These Windows 2000 services are started:

Alerter
Automatic Updates
COM+ Event System
Computer Browser
DHCP Client
DHCP Server
Distributed File System
Distributed Link Tracking Client
Distributed Transaction Coordinator
DNS Client
Event Log
File Server for Macintosh
IPSEC Policy Agent
License Logging Service
Logical Disk Manager
McAfee Framework Service
Messenger
Network Associates McShield
Network Associates Task Manager
Network Connections
NT LM Security Support Provider
Plug and Play
Print Server for Macintosh
Print Spooler
Protected Storage
Remote Access Connection Manager
Remote Procedure Call (RPC)
Remote Registry Service
Removable Storage
RunAs Service
Security Accounts Manager
Server
System Event Notification
Task Scheduler
TCP/IP NetBIOS Helper Service
Telephony
Terminal Services
UltraBac Management Service
UltraBac Scheduler
Windows Internet Name Service (WINS)
Windows Management Instrumentation
Windows Management Instrumentation Driver Extensions
Workstation

The command completed successfully.
(on meteornt2) and looking for "Server" (simply
that) in the lower part or by checking in your Services
console.

You might also type "Net Share" and prove to yourself
that you have SOMETHING shared -- machines do not
appear in browsers unless at least one non-hidden share
is offered.

I do see my shares listed when I run this command.
Name resolution is not a problem for you apparently
since you pings work fine by Name.

--
Herb Martin


Chris said:
OK - slight change:
The server I was on was old,and ready to be upgraded (to W2k). So we
installed a new server Everything is good with the XP clients now but.

Another older Citrix server cannot connect to the new NT server. The
problems seem to be the same as the issues from xpclient to winnt4.

So below are the test results you had suggested but from Citrix (apprisent)
and W2K (meteornt2).

Reports from Citrix Server

Windows NT IP Configuration

Host Name . . . . . . . . . : apprisent.mtr2.com
DNS Servers . . . . . . . . : 216.24.175.3
216.24.175.2
Node Type . . . . . . . . . : Hybrid
NetBIOS Scope ID. . . . . . : 1688
IP Routing Enabled. . . . . : Yes
WINS Proxy Enabled. . . . . : No
NetBIOS Resolution Uses DNS : No

Ethernet adapter El90x2:

Description . . . . . . . . : 3Com EtherLink PCI
Physical Address. . . . . . : 00-10-4B-C8-1E-0E
DHCP Enabled. . . . . . . . : No
IP Address. . . . . . . . . : 10.0.1.8
Subnet Mask . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . : 10.0.0.1
Primary WINS Server . . . . : 10.0.1.6
Secondary WINS Server . . . : 10.0.1.150


C:\WTSRV\Profiles\ADMINI~1>ping meteornt2

Pinging meteornt2 [10.0.1.6] with 32 bytes of data:

Reply from 10.0.1.6: bytes=32 time<10ms TTL=128
Reply from 10.0.1.6: bytes=32 time<10ms TTL=128
Reply from 10.0.1.6: bytes=32 time<10ms TTL=128
Reply from 10.0.1.6: bytes=32 time<10ms TTL=128


C:\WTSRV\Profiles\ADMINI~1>ping 10.0.1.6

Pinging 10.0.1.6 with 32 bytes of data:

Reply from 10.0.1.6: bytes=32 time<10ms TTL=128
Reply from 10.0.1.6: bytes=32 time<10ms TTL=128
Reply from 10.0.1.6: bytes=32 time<10ms TTL=128
Reply from 10.0.1.6: bytes=32 time<10ms TTL=128

C:\WTSRV\Profiles\ADMINI~1>net view \\meteornt2
System error 51 has occurred.

The remote computer is not available.

C:\WTSRV\Profiles\ADMINI~1>net view \\10.0.1.6
System error 53 has occurred.

The network path was not found.





Meteornt2

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

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : meteornt2
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Netelligent 10/100TX PCI
Embedded UT
P/AUI Controller
Physical Address. . . . . . . . . : 00-50-8B-55-2D-02
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.0.1.6
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 10.0.0.1
DNS Servers . . . . . . . . . . . : 216.24.175.3
216.24.175.2
Primary WINS Server . . . . . . . : 10.0.1.6


C:\Documents and Settings\Administrator>ping apprisent

Pinging apprisent [10.0.1.8] with 32 bytes of data:

Reply from 10.0.1.8: bytes=32 time<10ms TTL=128
Reply from 10.0.1.8: bytes=32 time<10ms TTL=128
Reply from 10.0.1.8: bytes=32 time<10ms TTL=128
Reply from 10.0.1.8: bytes=32 time<10ms TTL=128

Ping statistics for 10.0.1.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Documents and Settings\Administrator>ping 10.0.1.8

Pinging 10.0.1.8 with 32 bytes of data:

Reply from 10.0.1.8: bytes=32 time<10ms TTL=128
Reply from 10.0.1.8: bytes=32 time<10ms TTL=128
Reply from 10.0.1.8: bytes=32 time<10ms TTL=128
Reply from 10.0.1.8: bytes=32 time<10ms TTL=128

Ping statistics for 10.0.1.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Documents and Settings\Administrator>net view \\apprisent
System error 53 has occurred.

The network path was not found.

C:\Documents and Settings\Administrator>net view \\10.0.1.8
System error 53 has occurred.

The network path was not found.

Sorry about the change in direction.

Chris




:

If you can tell me how to capture from the dos prompt I will give it a go.

We will work with what is below, assuming you
made no significant typos (worst would be an
assumption about the subnet Mask where it read
on way and you unconsciously typed what you
expect -- I have done it and it is not that uncommon.)

But, for copying (if we or you need it in the future)
there are two ways:

1) Alt-space for the system menu (or click on the
left title bar box to get it.) Edit is down the
menu a bit (E), Mark and Copy but this is the
hard way even though it always works with
not setup.

2) Use that same system menu to bring up Properties,
and set the Options: Set QuickEdit mode and
likely Insert. While you are at it set your
scrollback screen buffer to >1000 lines on layout
and your colors to something decent in Colors,
e.g., bright yellow text on dark blue is most readable
for most people -- and it reminds you that you have
setup the command prompt.

Best is to perform actions #2 on the SHORTCUT or
save the settings for the "Shortcut that started this"
window. Nice thing about #1 is you can do it on
someone else's machine without prep.


XP Client
C:\Documents and Settings\meteor>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : marketlap6138
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 3Com 3C920 Integrated Fast
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.0.1.30
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 10.0.0.1

C:\Documents and Settings\meteor>
ip address: 10.0.1.6
Subnet Mask 255.255.0.0
Gateway 10.0.0.1
primary wins 10.0.1.11
secondary Wins 10.0.1.8

I don't see you DNS server settings -- whether
they are set to Internal DNS servers (if you have
them) or to external -- note it is always wrong
to mix the two settings on a single client...

The node type on the XP client implies you have
a WINS server, but it doesn't show the address(es).

The WINS server addresses on the other machine,
show TWO WINS servers so we must wonder if
all of the machines are set as clients AND if these
two WINS servers are REPLICATING.

This is my current guess (not replicating and/or
not all are set to the same two or set at all) since
you seem to have a Name resolution error, BUT
if you truly only have one subnet the BROADCAST
should eventually take over and resolve the server
names.

Ok, we really need the exact symptoms from the
same machines. (and you might as well cut and
paste the settings while you are at it since that
eliminates mistyping and the omission of important
info.)

Perform these tests as well (and report results):

ping servername
ping IP.adress.Of.Server
e.g.,: ping 10.0.1.6

net view \\Servername
net view \\IP.adress.Of.Server
e.g.,: net view \\10.0.1.6

You might also try nslookup IF you are using an
internal DNS server:

nslookup ServerName

(you may get a bogus DNS server error immediately
after the command (first first lines) but down below
you will get the (good) results or the real error.

That early error is an NSLookup artifact. Ignore it
(or just report the whole thing by pasting so we can
show you where the important stuff is.)

--
Herb Martin




:

But are the servers (anything offering shares) all listed?

Yes there are servers and workstations with shares that can be
connected
to
from here (winnt4 server network neighborhood)

Ok, well are there any with shares that are missing...
(No server shows up in browsing unless at least one
non-hidden share is made available...)

There are no DC's All computers are in a single workgroup.
All pc's are in the same subnet.
All machines are wins clients, the WinNT 4 had an old wins server
listed
as
2nd, I updated that to the current ones. This did not fix the problem

WINS is irrelevant in a single subnet network unless
reducing broadcasts is extremely important. (Most
small networks it doesn't matter much.)

I can ping in both directions using the ip address.

How about name? If not we are experiencing at least
some kind of Name Resolution problem.

This may be a lead - I can ping by name from client to server. I
cannot
ping
by name from the WinNT4 server to the clients. Ping returns "bad ip
address
clientname"

Ok, we have an IP range or subnet mask problem
probably (ok it might be routing too but unlikely).

Sounds like the machines (while on the same physical
segment) have IP addresses from different (sub)networks.

Check all your IP addresses and subnet masks. Make
sure no machine is set to automatic unless you have
DHCP and then make sure it is getting an address.

Post here you IPCONFIG from a CLIENT and a SERVER
which have the problem when talking to each other.

Don't edit it -- cut and paste the text directly from the
cmd prompt:

ipconfig /all
 
E

Eugene Taylor

What is the pysical layout are they on different switches? Are they on
different subnets?
Chris said:
Herb Martin said:
There is such an error in Win2000/XP for DNS names
of exactly 16 characters (doesn't apply here) but that
can be fixed by SERVICE PACKS.

But this does bring up the question of what service
pack you have deployed? Since you are on the
Internet it is essential that you apply (practically)
ever service pack and hot fix.

SP6 - I will do any hot fixes I can find.
You might also have disable NetBIOS to cause this
error but I doubt you would do that (and so seldom
mention this.)

I do not think I did - I see it bound to the Wins Client under the adaptor
bindings. Is there another place to see it?
That looks like the Server service is NOT running.

And this KB seems to agree:
http://support.microsoft.com/default.aspx?scid=kb;en-us;259878

This would not be odd if you turned it off (it's own
by default) or if the W2K (meteornt2) is running a
firewall which prevents the Server service ports
from being available to clients.

You can check the first easily by typing at the CMD
prompt:

Net Start

It is running - see output.

C:\Documents and Settings\Administrator>net start
These Windows 2000 services are started:

Alerter
Automatic Updates
COM+ Event System
Computer Browser
DHCP Client
DHCP Server
Distributed File System
Distributed Link Tracking Client
Distributed Transaction Coordinator
DNS Client
Event Log
File Server for Macintosh
IPSEC Policy Agent
License Logging Service
Logical Disk Manager
McAfee Framework Service
Messenger
Network Associates McShield
Network Associates Task Manager
Network Connections
NT LM Security Support Provider
Plug and Play
Print Server for Macintosh
Print Spooler
Protected Storage
Remote Access Connection Manager
Remote Procedure Call (RPC)
Remote Registry Service
Removable Storage
RunAs Service
Security Accounts Manager
Server
System Event Notification
Task Scheduler
TCP/IP NetBIOS Helper Service
Telephony
Terminal Services
UltraBac Management Service
UltraBac Scheduler
Windows Internet Name Service (WINS)
Windows Management Instrumentation
Windows Management Instrumentation Driver Extensions
Workstation

The command completed successfully.
(on meteornt2) and looking for "Server" (simply
that) in the lower part or by checking in your Services
console.

You might also type "Net Share" and prove to yourself
that you have SOMETHING shared -- machines do not
appear in browsers unless at least one non-hidden share
is offered.

I do see my shares listed when I run this command.
Name resolution is not a problem for you apparently
since you pings work fine by Name.

--
Herb Martin


Chris said:
OK - slight change:
The server I was on was old,and ready to be upgraded (to W2k). So we
installed a new server Everything is good with the XP clients now but.

Another older Citrix server cannot connect to the new NT server. The
problems seem to be the same as the issues from xpclient to winnt4.

So below are the test results you had suggested but from Citrix (apprisent)
and W2K (meteornt2).

Reports from Citrix Server

Windows NT IP Configuration

Host Name . . . . . . . . . : apprisent.mtr2.com
DNS Servers . . . . . . . . : 216.24.175.3
216.24.175.2
Node Type . . . . . . . . . : Hybrid
NetBIOS Scope ID. . . . . . : 1688
IP Routing Enabled. . . . . : Yes
WINS Proxy Enabled. . . . . : No
NetBIOS Resolution Uses DNS : No

Ethernet adapter El90x2:

Description . . . . . . . . : 3Com EtherLink PCI
Physical Address. . . . . . : 00-10-4B-C8-1E-0E
DHCP Enabled. . . . . . . . : No
IP Address. . . . . . . . . : 10.0.1.8
Subnet Mask . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . : 10.0.0.1
Primary WINS Server . . . . : 10.0.1.6
Secondary WINS Server . . . : 10.0.1.150


C:\WTSRV\Profiles\ADMINI~1>ping meteornt2

Pinging meteornt2 [10.0.1.6] with 32 bytes of data:

Reply from 10.0.1.6: bytes=32 time<10ms TTL=128
Reply from 10.0.1.6: bytes=32 time<10ms TTL=128
Reply from 10.0.1.6: bytes=32 time<10ms TTL=128
Reply from 10.0.1.6: bytes=32 time<10ms TTL=128


C:\WTSRV\Profiles\ADMINI~1>ping 10.0.1.6

Pinging 10.0.1.6 with 32 bytes of data:

Reply from 10.0.1.6: bytes=32 time<10ms TTL=128
Reply from 10.0.1.6: bytes=32 time<10ms TTL=128
Reply from 10.0.1.6: bytes=32 time<10ms TTL=128
Reply from 10.0.1.6: bytes=32 time<10ms TTL=128

C:\WTSRV\Profiles\ADMINI~1>net view \\meteornt2
System error 51 has occurred.

The remote computer is not available.

C:\WTSRV\Profiles\ADMINI~1>net view \\10.0.1.6
System error 53 has occurred.

The network path was not found.





Meteornt2

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

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : meteornt2
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Netelligent 10/100TX PCI
Embedded UT
P/AUI Controller
Physical Address. . . . . . . . . : 00-50-8B-55-2D-02
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.0.1.6
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 10.0.0.1
DNS Servers . . . . . . . . . . . : 216.24.175.3
216.24.175.2
Primary WINS Server . . . . . . . : 10.0.1.6


C:\Documents and Settings\Administrator>ping apprisent

Pinging apprisent [10.0.1.8] with 32 bytes of data:

Reply from 10.0.1.8: bytes=32 time<10ms TTL=128
Reply from 10.0.1.8: bytes=32 time<10ms TTL=128
Reply from 10.0.1.8: bytes=32 time<10ms TTL=128
Reply from 10.0.1.8: bytes=32 time<10ms TTL=128

Ping statistics for 10.0.1.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Documents and Settings\Administrator>ping 10.0.1.8

Pinging 10.0.1.8 with 32 bytes of data:

Reply from 10.0.1.8: bytes=32 time<10ms TTL=128
Reply from 10.0.1.8: bytes=32 time<10ms TTL=128
Reply from 10.0.1.8: bytes=32 time<10ms TTL=128
Reply from 10.0.1.8: bytes=32 time<10ms TTL=128

Ping statistics for 10.0.1.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Documents and Settings\Administrator>net view \\apprisent
System error 53 has occurred.

The network path was not found.

C:\Documents and Settings\Administrator>net view \\10.0.1.8
System error 53 has occurred.

The network path was not found.

Sorry about the change in direction.

Chris




:

If you can tell me how to capture from the dos prompt I will give
it a
go.
We will work with what is below, assuming you
made no significant typos (worst would be an
assumption about the subnet Mask where it read
on way and you unconsciously typed what you
expect -- I have done it and it is not that uncommon.)

But, for copying (if we or you need it in the future)
there are two ways:

1) Alt-space for the system menu (or click on the
left title bar box to get it.) Edit is down the
menu a bit (E), Mark and Copy but this is the
hard way even though it always works with
not setup.

2) Use that same system menu to bring up Properties,
and set the Options: Set QuickEdit mode and
likely Insert. While you are at it set your
scrollback screen buffer to >1000 lines on layout
and your colors to something decent in Colors,
e.g., bright yellow text on dark blue is most readable
for most people -- and it reminds you that you have
setup the command prompt.

Best is to perform actions #2 on the SHORTCUT or
save the settings for the "Shortcut that started this"
window. Nice thing about #1 is you can do it on
someone else's machine without prep.


XP Client
C:\Documents and Settings\meteor>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : marketlap6138
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 3Com 3C920 Integrated Fast
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.0.1.30
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 10.0.0.1

C:\Documents and Settings\meteor>
ip address: 10.0.1.6
Subnet Mask 255.255.0.0
Gateway 10.0.0.1
primary wins 10.0.1.11
secondary Wins 10.0.1.8

I don't see you DNS server settings -- whether
they are set to Internal DNS servers (if you have
them) or to external -- note it is always wrong
to mix the two settings on a single client...

The node type on the XP client implies you have
a WINS server, but it doesn't show the address(es).

The WINS server addresses on the other machine,
show TWO WINS servers so we must wonder if
all of the machines are set as clients AND if these
two WINS servers are REPLICATING.

This is my current guess (not replicating and/or
not all are set to the same two or set at all) since
you seem to have a Name resolution error, BUT
if you truly only have one subnet the BROADCAST
should eventually take over and resolve the server
names.

Ok, we really need the exact symptoms from the
same machines. (and you might as well cut and
paste the settings while you are at it since that
eliminates mistyping and the omission of important
info.)

Perform these tests as well (and report results):

ping servername
ping IP.adress.Of.Server
e.g.,: ping 10.0.1.6

net view \\Servername
net view \\IP.adress.Of.Server
e.g.,: net view \\10.0.1.6

You might also try nslookup IF you are using an
internal DNS server:

nslookup ServerName

(you may get a bogus DNS server error immediately
after the command (first first lines) but down below
you will get the (good) results or the real error.

That early error is an NSLookup artifact. Ignore it
(or just report the whole thing by pasting so we can
show you where the important stuff is.)

--
Herb Martin




:

But are the servers (anything offering shares) all listed?

Yes there are servers and workstations with shares that can be
connected
to
from here (winnt4 server network neighborhood)

Ok, well are there any with shares that are missing...
(No server shows up in browsing unless at least one
non-hidden share is made available...)

There are no DC's All computers are in a single workgroup.
All pc's are in the same subnet.
All machines are wins clients, the WinNT 4 had an old wins server
listed
as
2nd, I updated that to the current ones. This did not fix the problem

WINS is irrelevant in a single subnet network unless
reducing broadcasts is extremely important. (Most
small networks it doesn't matter much.)

I can ping in both directions using the ip address.

How about name? If not we are experiencing at least
some kind of Name Resolution problem.

This may be a lead - I can ping by name from client to server. I
cannot
ping
by name from the WinNT4 server to the clients. Ping returns
"bad
ip
address
clientname"

Ok, we have an IP range or subnet mask problem
probably (ok it might be routing too but unlikely).

Sounds like the machines (while on the same physical
segment) have IP addresses from different (sub)networks.

Check all your IP addresses and subnet masks. Make
sure no machine is set to automatic unless you have
DHCP and then make sure it is getting an address.

Post here you IPCONFIG from a CLIENT and a SERVER
which have the problem when talking to each other.

Don't edit it -- cut and paste the text directly from the
cmd prompt:

ipconfig /all
 
G

Guest

They are on the same switch (all three) and all share the same subnet.



Eugene Taylor said:
What is the pysical layout are they on different switches? Are they on
different subnets?
Chris said:
Herb Martin said:
C:\WTSRV\Profiles\ADMINI~1>net view \\meteornt2
System error 51 has occurred.

The remote computer is not available.

There is such an error in Win2000/XP for DNS names
of exactly 16 characters (doesn't apply here) but that
can be fixed by SERVICE PACKS.

But this does bring up the question of what service
pack you have deployed? Since you are on the
Internet it is essential that you apply (practically)
ever service pack and hot fix.

SP6 - I will do any hot fixes I can find.
You might also have disable NetBIOS to cause this
error but I doubt you would do that (and so seldom
mention this.)

I do not think I did - I see it bound to the Wins Client under the adaptor
bindings. Is there another place to see it?
C:\WTSRV\Profiles\ADMINI~1>net view \\10.0.1.6
System error 53 has occurred.

The network path was not found.

That looks like the Server service is NOT running.

And this KB seems to agree:
http://support.microsoft.com/default.aspx?scid=kb;en-us;259878

This would not be odd if you turned it off (it's own
by default) or if the W2K (meteornt2) is running a
firewall which prevents the Server service ports
from being available to clients.

You can check the first easily by typing at the CMD
prompt:

Net Start

It is running - see output.

C:\Documents and Settings\Administrator>net start
These Windows 2000 services are started:

Alerter
Automatic Updates
COM+ Event System
Computer Browser
DHCP Client
DHCP Server
Distributed File System
Distributed Link Tracking Client
Distributed Transaction Coordinator
DNS Client
Event Log
File Server for Macintosh
IPSEC Policy Agent
License Logging Service
Logical Disk Manager
McAfee Framework Service
Messenger
Network Associates McShield
Network Associates Task Manager
Network Connections
NT LM Security Support Provider
Plug and Play
Print Server for Macintosh
Print Spooler
Protected Storage
Remote Access Connection Manager
Remote Procedure Call (RPC)
Remote Registry Service
Removable Storage
RunAs Service
Security Accounts Manager
Server
System Event Notification
Task Scheduler
TCP/IP NetBIOS Helper Service
Telephony
Terminal Services
UltraBac Management Service
UltraBac Scheduler
Windows Internet Name Service (WINS)
Windows Management Instrumentation
Windows Management Instrumentation Driver Extensions
Workstation

The command completed successfully.
(on meteornt2) and looking for "Server" (simply
that) in the lower part or by checking in your Services
console.

You might also type "Net Share" and prove to yourself
that you have SOMETHING shared -- machines do not
appear in browsers unless at least one non-hidden share
is offered.

I do see my shares listed when I run this command.
Name resolution is not a problem for you apparently
since you pings work fine by Name.

--
Herb Martin


OK - slight change:
The server I was on was old,and ready to be upgraded (to W2k). So we
installed a new server Everything is good with the XP clients now but.

Another older Citrix server cannot connect to the new NT server. The
problems seem to be the same as the issues from xpclient to winnt4.

So below are the test results you had suggested but from Citrix
(apprisent)
and W2K (meteornt2).

Reports from Citrix Server

Windows NT IP Configuration

Host Name . . . . . . . . . : apprisent.mtr2.com
DNS Servers . . . . . . . . : 216.24.175.3
216.24.175.2
Node Type . . . . . . . . . : Hybrid
NetBIOS Scope ID. . . . . . : 1688
IP Routing Enabled. . . . . : Yes
WINS Proxy Enabled. . . . . : No
NetBIOS Resolution Uses DNS : No

Ethernet adapter El90x2:

Description . . . . . . . . : 3Com EtherLink PCI
Physical Address. . . . . . : 00-10-4B-C8-1E-0E
DHCP Enabled. . . . . . . . : No
IP Address. . . . . . . . . : 10.0.1.8
Subnet Mask . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . : 10.0.0.1
Primary WINS Server . . . . : 10.0.1.6
Secondary WINS Server . . . : 10.0.1.150


C:\WTSRV\Profiles\ADMINI~1>ping meteornt2

Pinging meteornt2 [10.0.1.6] with 32 bytes of data:

Reply from 10.0.1.6: bytes=32 time<10ms TTL=128
Reply from 10.0.1.6: bytes=32 time<10ms TTL=128
Reply from 10.0.1.6: bytes=32 time<10ms TTL=128
Reply from 10.0.1.6: bytes=32 time<10ms TTL=128


C:\WTSRV\Profiles\ADMINI~1>ping 10.0.1.6

Pinging 10.0.1.6 with 32 bytes of data:

Reply from 10.0.1.6: bytes=32 time<10ms TTL=128
Reply from 10.0.1.6: bytes=32 time<10ms TTL=128
Reply from 10.0.1.6: bytes=32 time<10ms TTL=128
Reply from 10.0.1.6: bytes=32 time<10ms TTL=128

C:\WTSRV\Profiles\ADMINI~1>net view \\meteornt2
System error 51 has occurred.

The remote computer is not available.

C:\WTSRV\Profiles\ADMINI~1>net view \\10.0.1.6
System error 53 has occurred.

The network path was not found.





Meteornt2

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

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : meteornt2
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Netelligent 10/100TX PCI
Embedded UT
P/AUI Controller
Physical Address. . . . . . . . . : 00-50-8B-55-2D-02
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.0.1.6
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 10.0.0.1
DNS Servers . . . . . . . . . . . : 216.24.175.3
216.24.175.2
Primary WINS Server . . . . . . . : 10.0.1.6


C:\Documents and Settings\Administrator>ping apprisent

Pinging apprisent [10.0.1.8] with 32 bytes of data:

Reply from 10.0.1.8: bytes=32 time<10ms TTL=128
Reply from 10.0.1.8: bytes=32 time<10ms TTL=128
Reply from 10.0.1.8: bytes=32 time<10ms TTL=128
Reply from 10.0.1.8: bytes=32 time<10ms TTL=128

Ping statistics for 10.0.1.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Documents and Settings\Administrator>ping 10.0.1.8

Pinging 10.0.1.8 with 32 bytes of data:

Reply from 10.0.1.8: bytes=32 time<10ms TTL=128
Reply from 10.0.1.8: bytes=32 time<10ms TTL=128
Reply from 10.0.1.8: bytes=32 time<10ms TTL=128
Reply from 10.0.1.8: bytes=32 time<10ms TTL=128

Ping statistics for 10.0.1.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Documents and Settings\Administrator>net view \\apprisent
System error 53 has occurred.

The network path was not found.

C:\Documents and Settings\Administrator>net view \\10.0.1.8
System error 53 has occurred.

The network path was not found.

Sorry about the change in direction.

Chris




:

If you can tell me how to capture from the dos prompt I will give it a
go.

We will work with what is below, assuming you
made no significant typos (worst would be an
assumption about the subnet Mask where it read
on way and you unconsciously typed what you
expect -- I have done it and it is not that uncommon.)

But, for copying (if we or you need it in the future)
there are two ways:

1) Alt-space for the system menu (or click on the
left title bar box to get it.) Edit is down the
menu a bit (E), Mark and Copy but this is the
hard way even though it always works with
not setup.

2) Use that same system menu to bring up Properties,
and set the Options: Set QuickEdit mode and
likely Insert. While you are at it set your
scrollback screen buffer to >1000 lines on layout
and your colors to something decent in Colors,
e.g., bright yellow text on dark blue is most readable
for most people -- and it reminds you that you have
setup the command prompt.

Best is to perform actions #2 on the SHORTCUT or
save the settings for the "Shortcut that started this"
window. Nice thing about #1 is you can do it on
someone else's machine without prep.


XP Client
C:\Documents and Settings\meteor>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : marketlap6138
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 3Com 3C920 Integrated Fast
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.0.1.30
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 10.0.0.1

C:\Documents and Settings\meteor>
ip address: 10.0.1.6
Subnet Mask 255.255.0.0
Gateway 10.0.0.1
primary wins 10.0.1.11
secondary Wins 10.0.1.8

I don't see you DNS server settings -- whether
they are set to Internal DNS servers (if you have
them) or to external -- note it is always wrong
to mix the two settings on a single client...

The node type on the XP client implies you have
a WINS server, but it doesn't show the address(es).

The WINS server addresses on the other machine,
show TWO WINS servers so we must wonder if
all of the machines are set as clients AND if these
two WINS servers are REPLICATING.

This is my current guess (not replicating and/or
not all are set to the same two or set at all) since
you seem to have a Name resolution error, BUT
if you truly only have one subnet the BROADCAST
should eventually take over and resolve the server
names.

Ok, we really need the exact symptoms from the
same machines. (and you might as well cut and
paste the settings while you are at it since that
eliminates mistyping and the omission of important
info.)

Perform these tests as well (and report results):

ping servername
ping IP.adress.Of.Server
e.g.,: ping 10.0.1.6

net view \\Servername
net view \\IP.adress.Of.Server
e.g.,: net view \\10.0.1.6

You might also try nslookup IF you are using an
internal DNS server:

nslookup ServerName

(you may get a bogus DNS server error immediately
after the command (first first lines) but down below
you will get the (good) results or the real error.

That early error is an NSLookup artifact. Ignore it
(or just report the whole thing by pasting so we can
show you where the important stuff is.)

--
Herb Martin




:

But are the servers (anything offering shares) all listed?

Yes there are servers and workstations with shares that can be
connected
to
from here (winnt4 server network neighborhood)

Ok, well are there any with shares that are missing...
(No server shows up in browsing unless at least one
non-hidden share is made available...)

There are no DC's All computers are in a single workgroup.
All pc's are in the same subnet.
All machines are wins clients, the WinNT 4 had an old wins server
listed
as
2nd, I updated that to the current ones. This did not fix the
problem

WINS is irrelevant in a single subnet network unless
reducing broadcasts is extremely important. (Most
small networks it doesn't matter much.)

I can ping in both directions using the ip address.

How about name? If not we are experiencing at least
some kind of Name Resolution problem.

This may be a lead - I can ping by name from client to server. I
cannot
ping
by name from the WinNT4 server to the clients. Ping returns "bad
ip
address
clientname"

Ok, we have an IP range or subnet mask problem
probably (ok it might be routing too but unlikely).

Sounds like the machines (while on the same physical
segment) have IP addresses from different (sub)networks.

Check all your IP addresses and subnet masks. Make
sure no machine is set to automatic unless you have
DHCP and then make sure it is getting an address.

Post here you IPCONFIG from a CLIENT and a SERVER
which have the problem when talking to each other.

Don't edit it -- cut and paste the text directly from the
cmd prompt:

ipconfig /all
 
H

Herb Martin

Chris said:
They are on the same switch (all three) and all share the same subnet.

Is this a true switch (and not one of those 10/100 Mbps
speed CHANGING hubs where the advertisers write
"switch" on the box) ?

(Even those hubs, but especially) Since switches
have to send broadcasts to every leg and this doesn't
always work right.

Even those 10/100 Mbps hums occasionally mess
up from he 10 to the 100 Mbps side -- they are
a bridge in between and maybe the 9x machines
have old NICs?

One thing you want to do is concentrate on using
the simple diagnostic tools mostly (at least until
they give consistent reliable results): ping,
"net view", "net use", nslookup, etc


--
Herb Martin

Eugene Taylor said:
What is the pysical layout are they on different switches? Are they on
different subnets?
Chris said:
:

C:\WTSRV\Profiles\ADMINI~1>net view \\meteornt2
System error 51 has occurred.

The remote computer is not available.

There is such an error in Win2000/XP for DNS names
of exactly 16 characters (doesn't apply here) but that
can be fixed by SERVICE PACKS.

But this does bring up the question of what service
pack you have deployed? Since you are on the
Internet it is essential that you apply (practically)
ever service pack and hot fix.

SP6 - I will do any hot fixes I can find.


You might also have disable NetBIOS to cause this
error but I doubt you would do that (and so seldom
mention this.)

I do not think I did - I see it bound to the Wins Client under the adaptor
bindings. Is there another place to see it?


C:\WTSRV\Profiles\ADMINI~1>net view \\10.0.1.6
System error 53 has occurred.

The network path was not found.

That looks like the Server service is NOT running.

And this KB seems to agree:
http://support.microsoft.com/default.aspx?scid=kb;en-us;259878

This would not be odd if you turned it off (it's own
by default) or if the W2K (meteornt2) is running a
firewall which prevents the Server service ports
from being available to clients.

You can check the first easily by typing at the CMD
prompt:

Net Start

It is running - see output.

C:\Documents and Settings\Administrator>net start
These Windows 2000 services are started:

Alerter
Automatic Updates
COM+ Event System
Computer Browser
DHCP Client
DHCP Server
Distributed File System
Distributed Link Tracking Client
Distributed Transaction Coordinator
DNS Client
Event Log
File Server for Macintosh
IPSEC Policy Agent
License Logging Service
Logical Disk Manager
McAfee Framework Service
Messenger
Network Associates McShield
Network Associates Task Manager
Network Connections
NT LM Security Support Provider
Plug and Play
Print Server for Macintosh
Print Spooler
Protected Storage
Remote Access Connection Manager
Remote Procedure Call (RPC)
Remote Registry Service
Removable Storage
RunAs Service
Security Accounts Manager
Server
System Event Notification
Task Scheduler
TCP/IP NetBIOS Helper Service
Telephony
Terminal Services
UltraBac Management Service
UltraBac Scheduler
Windows Internet Name Service (WINS)
Windows Management Instrumentation
Windows Management Instrumentation Driver Extensions
Workstation

The command completed successfully.

(on meteornt2) and looking for "Server" (simply
that) in the lower part or by checking in your Services
console.

You might also type "Net Share" and prove to yourself
that you have SOMETHING shared -- machines do not
appear in browsers unless at least one non-hidden share
is offered.

I do see my shares listed when I run this command.


Name resolution is not a problem for you apparently
since you pings work fine by Name.

--
Herb Martin


OK - slight change:
The server I was on was old,and ready to be upgraded (to W2k). So we
installed a new server Everything is good with the XP clients now but.

Another older Citrix server cannot connect to the new NT server. The
problems seem to be the same as the issues from xpclient to winnt4.

So below are the test results you had suggested but from Citrix
(apprisent)
and W2K (meteornt2).

Reports from Citrix Server

Windows NT IP Configuration

Host Name . . . . . . . . . : apprisent.mtr2.com
DNS Servers . . . . . . . . : 216.24.175.3
216.24.175.2
Node Type . . . . . . . . . : Hybrid
NetBIOS Scope ID. . . . . . : 1688
IP Routing Enabled. . . . . : Yes
WINS Proxy Enabled. . . . . : No
NetBIOS Resolution Uses DNS : No

Ethernet adapter El90x2:

Description . . . . . . . . : 3Com EtherLink PCI
Physical Address. . . . . . : 00-10-4B-C8-1E-0E
DHCP Enabled. . . . . . . . : No
IP Address. . . . . . . . . : 10.0.1.8
Subnet Mask . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . : 10.0.0.1
Primary WINS Server . . . . : 10.0.1.6
Secondary WINS Server . . . : 10.0.1.150


C:\WTSRV\Profiles\ADMINI~1>ping meteornt2

Pinging meteornt2 [10.0.1.6] with 32 bytes of data:

Reply from 10.0.1.6: bytes=32 time<10ms TTL=128
Reply from 10.0.1.6: bytes=32 time<10ms TTL=128
Reply from 10.0.1.6: bytes=32 time<10ms TTL=128
Reply from 10.0.1.6: bytes=32 time<10ms TTL=128


C:\WTSRV\Profiles\ADMINI~1>ping 10.0.1.6

Pinging 10.0.1.6 with 32 bytes of data:

Reply from 10.0.1.6: bytes=32 time<10ms TTL=128
Reply from 10.0.1.6: bytes=32 time<10ms TTL=128
Reply from 10.0.1.6: bytes=32 time<10ms TTL=128
Reply from 10.0.1.6: bytes=32 time<10ms TTL=128

C:\WTSRV\Profiles\ADMINI~1>net view \\meteornt2
System error 51 has occurred.

The remote computer is not available.

C:\WTSRV\Profiles\ADMINI~1>net view \\10.0.1.6
System error 53 has occurred.

The network path was not found.





Meteornt2

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

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : meteornt2
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Netelligent 10/100TX PCI
Embedded UT
P/AUI Controller
Physical Address. . . . . . . . . : 00-50-8B-55-2D-02
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.0.1.6
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 10.0.0.1
DNS Servers . . . . . . . . . . . : 216.24.175.3
216.24.175.2
Primary WINS Server . . . . . . . : 10.0.1.6


C:\Documents and Settings\Administrator>ping apprisent

Pinging apprisent [10.0.1.8] with 32 bytes of data:

Reply from 10.0.1.8: bytes=32 time<10ms TTL=128
Reply from 10.0.1.8: bytes=32 time<10ms TTL=128
Reply from 10.0.1.8: bytes=32 time<10ms TTL=128
Reply from 10.0.1.8: bytes=32 time<10ms TTL=128

Ping statistics for 10.0.1.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Documents and Settings\Administrator>ping 10.0.1.8

Pinging 10.0.1.8 with 32 bytes of data:

Reply from 10.0.1.8: bytes=32 time<10ms TTL=128
Reply from 10.0.1.8: bytes=32 time<10ms TTL=128
Reply from 10.0.1.8: bytes=32 time<10ms TTL=128
Reply from 10.0.1.8: bytes=32 time<10ms TTL=128

Ping statistics for 10.0.1.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Documents and Settings\Administrator>net view \\apprisent
System error 53 has occurred.

The network path was not found.

C:\Documents and Settings\Administrator>net view \\10.0.1.8
System error 53 has occurred.

The network path was not found.

Sorry about the change in direction.

Chris




:

If you can tell me how to capture from the dos prompt I will
give
it a
go.

We will work with what is below, assuming you
made no significant typos (worst would be an
assumption about the subnet Mask where it read
on way and you unconsciously typed what you
expect -- I have done it and it is not that uncommon.)

But, for copying (if we or you need it in the future)
there are two ways:

1) Alt-space for the system menu (or click on the
left title bar box to get it.) Edit is down the
menu a bit (E), Mark and Copy but this is the
hard way even though it always works with
not setup.

2) Use that same system menu to bring up Properties,
and set the Options: Set QuickEdit mode and
likely Insert. While you are at it set your
scrollback screen buffer to >1000 lines on layout
and your colors to something decent in Colors,
e.g., bright yellow text on dark blue is most readable
for most people -- and it reminds you that you have
setup the command prompt.

Best is to perform actions #2 on the SHORTCUT or
save the settings for the "Shortcut that started this"
window. Nice thing about #1 is you can do it on
someone else's machine without prep.


XP Client
C:\Documents and Settings\meteor>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : marketlap6138
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 3Com 3C920
Integrated
Fast
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.0.1.30
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 10.0.0.1

C:\Documents and Settings\meteor>
ip address: 10.0.1.6
Subnet Mask 255.255.0.0
Gateway 10.0.0.1
primary wins 10.0.1.11
secondary Wins 10.0.1.8

I don't see you DNS server settings -- whether
they are set to Internal DNS servers (if you have
them) or to external -- note it is always wrong
to mix the two settings on a single client...

The node type on the XP client implies you have
a WINS server, but it doesn't show the address(es).

The WINS server addresses on the other machine,
show TWO WINS servers so we must wonder if
all of the machines are set as clients AND if these
two WINS servers are REPLICATING.

This is my current guess (not replicating and/or
not all are set to the same two or set at all) since
you seem to have a Name resolution error, BUT
if you truly only have one subnet the BROADCAST
should eventually take over and resolve the server
names.

Ok, we really need the exact symptoms from the
same machines. (and you might as well cut and
paste the settings while you are at it since that
eliminates mistyping and the omission of important
info.)

Perform these tests as well (and report results):

ping servername
ping IP.adress.Of.Server
e.g.,: ping 10.0.1.6

net view \\Servername
net view \\IP.adress.Of.Server
e.g.,: net view \\10.0.1.6

You might also try nslookup IF you are using an
internal DNS server:

nslookup ServerName

(you may get a bogus DNS server error immediately
after the command (first first lines) but down below
you will get the (good) results or the real error.

That early error is an NSLookup artifact. Ignore it
(or just report the whole thing by pasting so we can
show you where the important stuff is.)

--
Herb Martin




:

But are the servers (anything offering shares) all listed?

Yes there are servers and workstations with shares that can be
connected
to
from here (winnt4 server network neighborhood)

Ok, well are there any with shares that are missing...
(No server shows up in browsing unless at least one
non-hidden share is made available...)

There are no DC's All computers are in a single workgroup.
All pc's are in the same subnet.
All machines are wins clients, the WinNT 4 had an old wins server
listed
as
2nd, I updated that to the current ones. This did not fix the
problem

WINS is irrelevant in a single subnet network unless
reducing broadcasts is extremely important. (Most
small networks it doesn't matter much.)

I can ping in both directions using the ip address.

How about name? If not we are experiencing at least
some kind of Name Resolution problem.

This may be a lead - I can ping by name from client to
server.
I
cannot
ping
by name from the WinNT4 server to the clients. Ping
returns
"bad
ip
address
clientname"

Ok, we have an IP range or subnet mask problem
probably (ok it might be routing too but unlikely).

Sounds like the machines (while on the same physical
segment) have IP addresses from different (sub)networks.

Check all your IP addresses and subnet masks. Make
sure no machine is set to automatic unless you have
DHCP and then make sure it is getting an address.

Post here you IPCONFIG from a CLIENT and a SERVER
which have the problem when talking to each other.

Don't edit it -- cut and paste the text directly from the
cmd prompt:

ipconfig /all
 
G

Guest

Problem Solved!
Well I paid the $ and called Microsoft, it turns out that the original setup
had a Scope ID. Odly enough the NT 4 server did not mind connecting with the
W2K server (which does not use a Scope ID) but the NT4 Terminal Server did
have a problem connecting to the W2K server.

Remove the Scope ID from all servers and clients and they all work together
just fine.

Thank you for all of your help.

Chris

Herb Martin said:
Chris said:
They are on the same switch (all three) and all share the same subnet.

Is this a true switch (and not one of those 10/100 Mbps
speed CHANGING hubs where the advertisers write
"switch" on the box) ?

(Even those hubs, but especially) Since switches
have to send broadcasts to every leg and this doesn't
always work right.

Even those 10/100 Mbps hums occasionally mess
up from he 10 to the 100 Mbps side -- they are
a bridge in between and maybe the 9x machines
have old NICs?

One thing you want to do is concentrate on using
the simple diagnostic tools mostly (at least until
they give consistent reliable results): ping,
"net view", "net use", nslookup, etc


--
Herb Martin

Eugene Taylor said:
What is the pysical layout are they on different switches? Are they on
different subnets?


:

C:\WTSRV\Profiles\ADMINI~1>net view \\meteornt2
System error 51 has occurred.

The remote computer is not available.

There is such an error in Win2000/XP for DNS names
of exactly 16 characters (doesn't apply here) but that
can be fixed by SERVICE PACKS.

But this does bring up the question of what service
pack you have deployed? Since you are on the
Internet it is essential that you apply (practically)
ever service pack and hot fix.

SP6 - I will do any hot fixes I can find.


You might also have disable NetBIOS to cause this
error but I doubt you would do that (and so seldom
mention this.)

I do not think I did - I see it bound to the Wins Client under the adaptor
bindings. Is there another place to see it?


C:\WTSRV\Profiles\ADMINI~1>net view \\10.0.1.6
System error 53 has occurred.

The network path was not found.

That looks like the Server service is NOT running.

And this KB seems to agree:
http://support.microsoft.com/default.aspx?scid=kb;en-us;259878

This would not be odd if you turned it off (it's own
by default) or if the W2K (meteornt2) is running a
firewall which prevents the Server service ports
from being available to clients.

You can check the first easily by typing at the CMD
prompt:

Net Start

It is running - see output.

C:\Documents and Settings\Administrator>net start
These Windows 2000 services are started:

Alerter
Automatic Updates
COM+ Event System
Computer Browser
DHCP Client
DHCP Server
Distributed File System
Distributed Link Tracking Client
Distributed Transaction Coordinator
DNS Client
Event Log
File Server for Macintosh
IPSEC Policy Agent
License Logging Service
Logical Disk Manager
McAfee Framework Service
Messenger
Network Associates McShield
Network Associates Task Manager
Network Connections
NT LM Security Support Provider
Plug and Play
Print Server for Macintosh
Print Spooler
Protected Storage
Remote Access Connection Manager
Remote Procedure Call (RPC)
Remote Registry Service
Removable Storage
RunAs Service
Security Accounts Manager
Server
System Event Notification
Task Scheduler
TCP/IP NetBIOS Helper Service
Telephony
Terminal Services
UltraBac Management Service
UltraBac Scheduler
Windows Internet Name Service (WINS)
Windows Management Instrumentation
Windows Management Instrumentation Driver Extensions
Workstation

The command completed successfully.

(on meteornt2) and looking for "Server" (simply
that) in the lower part or by checking in your Services
console.

You might also type "Net Share" and prove to yourself
that you have SOMETHING shared -- machines do not
appear in browsers unless at least one non-hidden share
is offered.

I do see my shares listed when I run this command.


Name resolution is not a problem for you apparently
since you pings work fine by Name.

--
Herb Martin


OK - slight change:
The server I was on was old,and ready to be upgraded (to W2k). So we
installed a new server Everything is good with the XP clients now but.

Another older Citrix server cannot connect to the new NT server. The
problems seem to be the same as the issues from xpclient to winnt4.

So below are the test results you had suggested but from Citrix
(apprisent)
and W2K (meteornt2).

Reports from Citrix Server

Windows NT IP Configuration

Host Name . . . . . . . . . : apprisent.mtr2.com
DNS Servers . . . . . . . . : 216.24.175.3
216.24.175.2
Node Type . . . . . . . . . : Hybrid
NetBIOS Scope ID. . . . . . : 1688
IP Routing Enabled. . . . . : Yes
WINS Proxy Enabled. . . . . : No
NetBIOS Resolution Uses DNS : No

Ethernet adapter El90x2:

Description . . . . . . . . : 3Com EtherLink PCI
Physical Address. . . . . . : 00-10-4B-C8-1E-0E
DHCP Enabled. . . . . . . . : No
IP Address. . . . . . . . . : 10.0.1.8
Subnet Mask . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . : 10.0.0.1
Primary WINS Server . . . . : 10.0.1.6
Secondary WINS Server . . . : 10.0.1.150


C:\WTSRV\Profiles\ADMINI~1>ping meteornt2

Pinging meteornt2 [10.0.1.6] with 32 bytes of data:

Reply from 10.0.1.6: bytes=32 time<10ms TTL=128
Reply from 10.0.1.6: bytes=32 time<10ms TTL=128
Reply from 10.0.1.6: bytes=32 time<10ms TTL=128
Reply from 10.0.1.6: bytes=32 time<10ms TTL=128


C:\WTSRV\Profiles\ADMINI~1>ping 10.0.1.6

Pinging 10.0.1.6 with 32 bytes of data:

Reply from 10.0.1.6: bytes=32 time<10ms TTL=128
Reply from 10.0.1.6: bytes=32 time<10ms TTL=128
Reply from 10.0.1.6: bytes=32 time<10ms TTL=128
Reply from 10.0.1.6: bytes=32 time<10ms TTL=128

C:\WTSRV\Profiles\ADMINI~1>net view \\meteornt2
System error 51 has occurred.

The remote computer is not available.

C:\WTSRV\Profiles\ADMINI~1>net view \\10.0.1.6
System error 53 has occurred.

The network path was not found.





Meteornt2

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

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : meteornt2
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Netelligent 10/100TX PCI
Embedded UT
P/AUI Controller
Physical Address. . . . . . . . . : 00-50-8B-55-2D-02
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.0.1.6
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 10.0.0.1
DNS Servers . . . . . . . . . . . : 216.24.175.3
216.24.175.2
Primary WINS Server . . . . . . . : 10.0.1.6


C:\Documents and Settings\Administrator>ping apprisent

Pinging apprisent [10.0.1.8] with 32 bytes of data:

Reply from 10.0.1.8: bytes=32 time<10ms TTL=128
Reply from 10.0.1.8: bytes=32 time<10ms TTL=128
Reply from 10.0.1.8: bytes=32 time<10ms TTL=128
Reply from 10.0.1.8: bytes=32 time<10ms TTL=128

Ping statistics for 10.0.1.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Documents and Settings\Administrator>ping 10.0.1.8

Pinging 10.0.1.8 with 32 bytes of data:

Reply from 10.0.1.8: bytes=32 time<10ms TTL=128
Reply from 10.0.1.8: bytes=32 time<10ms TTL=128
Reply from 10.0.1.8: bytes=32 time<10ms TTL=128
Reply from 10.0.1.8: bytes=32 time<10ms TTL=128

Ping statistics for 10.0.1.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Documents and Settings\Administrator>net view \\apprisent
System error 53 has occurred.

The network path was not found.

C:\Documents and Settings\Administrator>net view \\10.0.1.8
System error 53 has occurred.

The network path was not found.

Sorry about the change in direction.

Chris




:

If you can tell me how to capture from the dos prompt I will give
it a
go.

We will work with what is below, assuming you
made no significant typos (worst would be an
assumption about the subnet Mask where it read
on way and you unconsciously typed what you
expect -- I have done it and it is not that uncommon.)

But, for copying (if we or you need it in the future)
there are two ways:

1) Alt-space for the system menu (or click on the
left title bar box to get it.) Edit is down the
menu a bit (E), Mark and Copy but this is the
hard way even though it always works with
not setup.

2) Use that same system menu to bring up Properties,
and set the Options: Set QuickEdit mode and
likely Insert. While you are at it set your
scrollback screen buffer to >1000 lines on layout
and your colors to something decent in Colors,
e.g., bright yellow text on dark blue is most readable
for most people -- and it reminds you that you have
setup the command prompt.

Best is to perform actions #2 on the SHORTCUT or
save the settings for the "Shortcut that started this"
window. Nice thing about #1 is you can do it on
someone else's machine without prep.


XP Client
C:\Documents and Settings\meteor>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : marketlap6138
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 3Com 3C920 Integrated
Fast
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.0.1.30
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 10.0.0.1

C:\Documents and Settings\meteor>
ip address: 10.0.1.6
Subnet Mask 255.255.0.0
Gateway 10.0.0.1
primary wins 10.0.1.11
secondary Wins 10.0.1.8

I don't see you DNS server settings -- whether
they are set to Internal DNS servers (if you have
them) or to external -- note it is always wrong
to mix the two settings on a single client...

The node type on the XP client implies you have
a WINS server, but it doesn't show the address(es).

The WINS server addresses on the other machine,
show TWO WINS servers so we must wonder if
all of the machines are set as clients AND if these
two WINS servers are REPLICATING.

This is my current guess (not replicating and/or
not all are set to the same two or set at all) since
you seem to have a Name resolution error, BUT
if you truly only have one subnet the BROADCAST
should eventually take over and resolve the server
names.

Ok, we really need the exact symptoms from the
same machines. (and you might as well cut and
paste the settings while you are at it since that
eliminates mistyping and the omission of important
info.)

Perform these tests as well (and report results):

ping servername
ping IP.adress.Of.Server
e.g.,: ping 10.0.1.6

net view \\Servername
net view \\IP.adress.Of.Server
e.g.,: net view \\10.0.1.6

You might also try nslookup IF you are using an
internal DNS server:

nslookup ServerName

(you may get a bogus DNS server error immediately
after the command (first first lines) but down below
you will get the (good) results or the real error.

That early error is an NSLookup artifact. Ignore it
(or just report the whole thing by pasting so we can
show you where the important stuff is.)

--
Herb Martin




:

But are the servers (anything offering shares) all listed?

Yes there are servers and workstations with shares that can be
connected
to
from here (winnt4 server network neighborhood)

Ok, well are there any with shares that are missing...
(No server shows up in browsing unless at least one
non-hidden share is made available...)

There are no DC's All computers are in a single workgroup.
All pc's are in the same subnet.
All machines are wins clients, the WinNT 4 had an old wins
server
listed
as
2nd, I updated that to the current ones. This did not fix the
problem

WINS is irrelevant in a single subnet network unless
reducing broadcasts is extremely important. (Most
small networks it doesn't matter much.)

I can ping in both directions using the ip address.

How about name? If not we are experiencing at least
some kind of Name Resolution problem.

This may be a lead - I can ping by name from client to server.
I
cannot
ping
by name from the WinNT4 server to the clients. Ping returns
"bad
ip
address
clientname"

Ok, we have an IP range or subnet mask problem
probably (ok it might be routing too but unlikely).

Sounds like the machines (while on the same physical
segment) have IP addresses from different (sub)networks.

Check all your IP addresses and subnet masks. Make
sure no machine is set to automatic unless you have
DHCP and then make sure it is getting an address.

Post here you IPCONFIG from a CLIENT and a SERVER
which have the problem when talking to each other.

Don't edit it -- cut and paste the text directly from the
cmd prompt:

ipconfig /all
 
H

Herb Martin

Chris said:
Problem Solved!
Well I paid the $ and called Microsoft, it turns out that the original setup
had a Scope ID.

I should have seen that in the second round
of your IPConfig.

Had you posted the actual (unedited) version
the first time there is a pretty good chance we
could have saved you the money as that is trivial
error to pick up.

Unfortanately, I probably skimmed the second
posting focused on the connection problems you
definitely had that were NOT name resolution
(you used the IP and IT FAILED too.)

Odly enough the NT 4 server did not mind connecting with the
W2K server (which does not use a Scope ID) but the NT4 Terminal Server did
have a problem connecting to the W2K server.

Actually it will not resolve NetBIOS (but might resolve
DNS) with that scope ID in there.
Remove the Scope ID from all servers and clients and they all work together
just fine.

Scope IDs are archaic and should NEVER be filled
in, unless someone know precisely why they did that
and does it correctly on all machines.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top