Re: LM98/2 Session refused
- From: Dave Symes <dave@xxxxxxxxxxxxx>
- Date: Tue, 06 Apr 2010 18:18:34 +0100
In article <7d5fc00351.Alan.Adams@xxxxxxxxxxxxxxxxxxxxxxx>,
Alan Adams <alan@xxxxxxxxxxxxxxxx> wrote:
In message <510392c099dave@xxxxxxxxxxxxx>
Dave Symes <dave@xxxxxxxxxxxxx> wrote:
<snip>
I have exactly the same problem. If however you turn NetBIOS off
rather than leave it to turn its self on under certain circumstances
as described under default, it still does not work.
LM98/2 now returns the error "Connection Failed (61)" what ever that
means.
Adrian Crafer
Yes on the RO side "Connection Failed (61) is what I get if on the Win 7
side "Default" is not used, and if I switch NetBios over TC.. Off then
there is no LAN connection at all. (Just eventually times out).
And on the Win side it take at least 10 minutes for the Network and
Sharing Centre window to display after clicking.
Some Net searching does seem to indicate there is a problem, but to be
honest, I've not quite fathomed out what.
Do a Google for LMHOSTS lookup.
Are you trying top connect LanMan98 to the Win7 machine by name or by
address?
Provided it has a fixed IP address, address is the most reliable way.
Next option, again requiring a fixed address, is to put an entry in
the hosts file defining the name-to-address conversion.
If the Win7 machine is using DHCP then it is a bit more fiddly:
best option is to add a reservation to the DHCP server so the Win7
machine always gets the same address, then use either option above.
Failing that, the remaining two choices are Dynamic DNS, or Netbios.
Dynamic DNS will only work if the DHCP server can supply information
to the DNS server. It works if both are a Windows server, and I
believe a small number of routers can also do it.
If you are left with NetBios, then obviously it has to be enabled on
the PCs - otherwise there no name advertiscements sent and received.
Fundamentally all connections are made by address: the question then
is simply how to get the address from a name.
Thanks for the input, it is apreciated.
Unfortunately this thread has gone on for so long now, the essence has
been lost.
It's not a LM98 problem as such, it's a Win 7 machine problem that holds
up LM98.
During the 10 minute(ish) period that the Win 7 is being uppity, neither
of the two SARPCs, or the two XP machine on the LAN can connect with the 7
machine.
Worth noting, during this hiatus period, the SARPCs LM98 and the XP
machines can connect over the LAN without a problem.
If I leave the 7 machine for the 10 or so minutes, then suddenly
everything else *can* connect with it, and it with them.
The Hosts file on this RPC contains an entry for the Win 7 machine of both
address 192.168.0.3 and the name of that computer.
The Win 7 computer itself has a name. (Yes it matches that in the Hosts
file).
I have changed the entry in the LM98 Disk file to contain either the 7s
name or fixed ip address, but that doesn't make any difference, as noted
above, until the LAN returns.
Final note.
When in uppity mode the 7 machine takes the same amount of time (10 mins)
to Open the Network and Sharing window.
Dave
Ps: With regard to DHCP everything on this network has a fixed address,
but as a last resort I am going to set the 7 machine to DHCP and see what
it does.
IIRC. I've set a range in the router for fixed addresses, so any DHCP
should occur outside that range and not trample on another machines
address.
--
Dave Triffid
.
- References:
- LM98/2 Session refused
- From: Dave Symes
- Re: LM98/2 Session refused
- From: Timothy Baldwin
- LM98/2 Session refused
- From: Dave Symes
- Re: LM98/2 Session refused
- From: Adrian Crafer
- LM98/2 Session refused
- From: Dave Symes
- Re: LM98/2 Session refused
- From: Alan Adams
- LM98/2 Session refused
- Prev by Date: Re: LM98/2 Session refused
- Next by Date: Re: LM98/2 Session refused
- Previous by thread: Re: LM98/2 Session refused
- Next by thread: Re: LM98/2 Session refused
- Index(es):
Relevant Pages
|