I am having problems running RCONSOLE (or any apps that use SPX) on an
NT 4.0 workstation with the Intranetware Client for NT on a NW 3.11
network. I don't "see" any servers in RCONSOLE. I can connect to the
network OK and am able to access files and printers.
--
|
|Doug Dockter
|e-mail:
|Phone: 217-241-6317 Fax: 217-241-6579
|
Rating: 0%, 0 votes
advanced options (or something like that - I'm at home and have
forgotten). One of the settings you can change is 'Minimum time to
net'. It defaults to '0'. I had the same RCONSOLE problem recently and
set that pram to 2500 and viola - problem solved. The text associated
with this param recommends a setting of 10000 for 2400 baud connections
and slow WAN links.
Bill
Ian Wood - Remove trailing 'x' from address to reply wrote:
Was this solution helpful? Show your Appreciation by rating it:
Rating: 0%, 0 votes
says...
So it did work on 4.10? or only on 4.11?
I am going to set up a test environment to see if the problem shows up
there as well. I'll post back my results.
--Ian.
Was this solution helpful? Show your Appreciation by rating it:
Rating: 0%, 0 votes
My network is fairly simple but does tend to go through various changes
(R&D etc..etc).
Here goes...
Server
Clone 486DX2/66
Previously Netware 4.10 (fully patched), now Netware 4.11 (fully patched)
10BaseT (frames 802.2, Ethernet_II)
IPX and IP protocol over single NE2000 compatible
Workstation
Clone P166
Windows NT Workstation 4 (patched with SRVPK2 and Kernal/RAS hotfixes)
Latest IntranetWare client for NT (recently added, previously using
NTENU_N2.EXE)
Single SMC100Mbit PCI Ethernet card, previously NE2000 compatible
IPX and IP protocol over single adapter.
Windows networking also installed.
That's it really. Most things are pretty standard, nothing fancy. RCONSOLE
currently works locally (and always has done!) but not over DUN.
Actually, I've just noticed a small funny...
Whilst experimenting I notice RCONSOLE *sometimes* reports an error between
the point where you select SPX and then get the server list. Can't see the
error though, flashes away too quickly. Blast !
Still get my servers though!
Don't know whether this info helps...
Kind regards
Elliot Paterson
DST Business Systems +44(0)1270 886111
Ian Wood - Remove trailing 'x' from address to reply
<> wrote in article
<MPG>...
Was this solution helpful? Show your Appreciation by rating it:
Rating: 0%, 0 votes
says...
As am I! But, if you din't mind, let me pick your brain for a minute and
see if there is a difference between your setup and mine. If you could
give me some details on your network. Here are mine.
Site A
Compaq ProLiant 1500 server with Netflex II NIC.
Novell 4.1 server 50 user (fully patched). Btrieve 6.15.
10BaseT Ethernet network (running 802.2,802.3,Ethernet_II).
IPX and IP protocols. RIP and SAP. No NLSP.
3Com Multiprotocol bridge/router connected to our 2Mbps WAN.
Compaq Deskpro NT Workstations with Netflex III NIC.
Both Intranetware client and MS CSNW. Both using NWLink.
Also Windows 95 and DOS/Win Clients.
Site B
Compaq ProSignia 300 server with Netflex II NIC.
Novell 4.1 server 20 user (fully patched). Btrieve 6.10c.
10BaseT Ethernet network (running 802.2,802.3,Ethernet_II).
IPX and IP protocols. RIP and SAP. No NLSP.
3Com Multiprotocol bridge/router connected to our 2Mbps WAN.
Windows 95 and DOS/Win Clients.
I am stumped by this problem as is Novell for the time being. Hoepfully
they will find something in the traces I have done.
--Ian.
Was this solution helpful? Show your Appreciation by rating it:
Rating: 0%, 0 votes
I've noticed the various messages from people concerning RCONSOLE on their
local networks ... I've always run it completely fine ! Netware 4.10/4.11,
current intranetware client for NTWK4, previous client, no problem at
all... no special tuning, just default everything - no problem locally !!!
HOWEVER ...
I have this problem accessing my customers sites via DUN where their
servers run Netware Connect. RCONSOLE brings up an empty list ... specifing
the network address doesn't help, neither does specific frame types etc
.etc .. can't get that working at all !! Works okay from Win95 DUN...
Weird ?
I'm confused !
Regards
Elliot Paterson
DST Business Systems
Ian Wood - Remove trailing 'x' from address to reply
<> wrote in article
<MPG>...
Was this solution helpful? Show your Appreciation by rating it:
Rating: 0%, 0 votes
same experience. SPX on the local network does not work from an NT
client. I have been working with Novell on this as an open issue and they
still have yet to come up with a solution.
It is a wierd situation however. The only thing that doesn't work is SPX
from any NT machine to the Netware server on the local net. A server on
the other end of our WAN is accessible. DOS workstations can SPX to the
server in question.
With Rconsole do you get a server list when you choose SPX? If you type
in the internal address using <INSERT> can you access the server? Or do
you get an SPXEstablishConnection Table Full error? That is what I get.
I have done traces with Lanalyzer and found that NWLink is not addressing
the local server properly. It is attempting to send SPX packets to the
server's internal address as opposed to the MAC address of the NIC. So
the packets go out but nothing recieves them. Whereas the server on the
other end of the WAN has its packets delivered properly by the routers
and that is why SPX works to it.
It is not just the Intranetware Client. It is the MS Client as well since
they both use NWLink. We have tried anything and everything. Servers are
completely patched up, set the frame types on client, increased SPX
timeouts, etc. etc.
Let me know if your experience is similar or not. I will post any other
findings on this that I come across.
--Ian.
In article <>, says...
Was this solution helpful? Show your Appreciation by rating it:
Rating: 0%, 0 votes
exactly the same. I cannot access the servers if I type in the internal
network address in RCONSOLE. No resolution on this end yet.
--
|
|Doug Dockter
|e-mail:
|Phone: 217-241-6317 Fax: 217-241-6579
|
Ian Wood - Remove trailing 'x' from address to reply wrote:
Was this solution helpful? Show your Appreciation by rating it:
Rating: 0%, 0 votes
I uninstalled, re-installed, etc but to no avail. On Sat. evening I
realized that since it only happens on the Novell IN client32 that I can
probably 'tune' it.
The changes I've made are; select a specific frame type and specify the
correct IPX net number in the properties area for the IntranetWare
client, I also set the 'minimum time to net' param at 2500. I rebooted
and can now go into RCONSOLE (either version) and get the server list.
My guess is that the 'minimum time to net' param has more to do with it
than specifying a frame type (not auto-detecting).
Bill
Was this solution helpful? Show your Appreciation by rating it:
Rating: 0%, 0 votes
or 3.75 ande no servers listed. I had it working a couple weeks ago then
had to do a re-install when a disk died. Thinking about it, I also had
several 'hot-fixes' installed (post SP2 fixes). I'll give that a try again
and report back. If anyone has any other ideas please post them. This is
a weird one...
Bill
EAJG Conijn <> wrote in article
<332DA>...
Was this solution helpful? Show your Appreciation by rating it:
Rating: 0%, 0 votes
I'm having the same problem as you, just installed the "new" v4.10
(02/14/97) Intranetware client for NT, and now can't "see" any servers in
RCONSOLE from a Netware 4.1 server.
This problem did not occur with the v4.00 (11/04/96) version of the
client. Must be somthing in the new Intranetware client software that is
messing up the SPX connections.
PS: You still can connect to your server via RCONSOLE if you type in the
IPXnet address.
Alan
In article <332DB95B>, Doug Dockter <> wrote:
--
"A programmer is a person who turns coffee into software."
Alan R. Vidmar Network Analyst/Administrator
Alan.Vid@Colorado.EDU University of Colorado
** This message printed with 100% recycled electrons **
Was this solution helpful? Show your Appreciation by rating it:
Rating: 0%, 0 votes
for NT and also have SP2 installed. I am using RCONSOLE 4.10. Is there
a later version?
--
|
|Doug Dockter
|e-mail:
|Phone: 217-241-6317 Fax: 217-241-6579
|
Was this solution helpful? Show your Appreciation by rating it:
Rating: 0%, 0 votes
Try a newer version of RCONSOLE.
I use the version which comes with Netware 4.10 and it works fine both
for 4.10 servers and for 3.12 servers.
Furthermore use the latest Client 32 for NT and use the Service Pack 2
for NT
Gijs
Was this solution helpful? Show your Appreciation by rating it:
Post a New problem for Compaq 2Mbps Wireless LAN PCI Card
Email this problem
Can you Help with these Wireless Adapters problems?
The microsoft wireless adapter...

