Re: No Connection on some xp clients
From: Eugene Taylor (ewtaylor2001_at_fake.com)
Date: 01/06/05
- Next message: Chris: "Re: No Connection on some xp clients"
- Previous message: Chris: "Re: No Connection on some xp clients"
- In reply to: Chris: "Re: No Connection on some xp clients"
- Next in thread: Chris: "Re: No Connection on some xp clients"
- Reply: Chris: "Re: No Connection on some xp clients"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 6 Jan 2005 13:54:02 -0500
What is the pysical layout are they on different switches? Are they on
different subnets?
"Chris" <Chris@discussions.microsoft.com> wrote in message
news:5CEC52DA-AFDF-4849-80F7-B5B6903441BC@microsoft.com...
>
>
> "Herb Martin" wrote:
>
> > > 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
> >
> >
> > "Chris" <Chris@discussions.microsoft.com> wrote in message
> > news:4653B233-1BCA-472E-A163-FD6836203BCB@microsoft.com...
> > > 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" wrote:
> > >
> > > > > 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
> > > >
> > > >
> > > > "Chris" <Chris@discussions.microsoft.com> wrote in message
> > > > news:CA8A2DDF-8A11-4BB1-B13E-866E5579C849@microsoft.com...
> > > > >
> > > > >
> > > > > "Herb Martin" wrote:
> > > > >
> > > > > > > > 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
> > > > >
> > > >
> > > >
> > > >
> >
> >
> >
- Next message: Chris: "Re: No Connection on some xp clients"
- Previous message: Chris: "Re: No Connection on some xp clients"
- In reply to: Chris: "Re: No Connection on some xp clients"
- Next in thread: Chris: "Re: No Connection on some xp clients"
- Reply: Chris: "Re: No Connection on some xp clients"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
