cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
497
Views
0
Helpful
2
Replies

novell login

tomtechj
Level 1
Level 1

Problem is that I can't login into novell server via router. From console I can make ping ipx command to server but Novell client can see only local server. What is wrong? Config of local router:

!

service timestamps debug uptime

service timestamps log uptime

service password-encryption

no service tcp-small-servers

no service udp-small-servers

!

hostname AAA

!

enable password ******

!

no ip name-server

!

ip subnet-zero

no ip domain-lookup

ip routing

ipx routing 1897.909e.6a1e

!

interface FastEthernet 0/0

no shutdown

description connected to EthernetLAN

ip address 192.100.100.250 255.255.255.0

ipx network BB048102 encapsulation novell-ether

no keepalive

!

interface Serial 0/0

no shutdown

no description

no ip address

encapsulation frame-relay

frame-relay lmi-type ansi

!

interface Serial 0/0.1 point-to-point

no shutdown

description connected to BBB

ip unnumbered FastEthernet 0/0

ipx network 10000001

frame-relay interface-dlci 101

!

router rip

version 2

network 192.100.100.0

no auto-summary

!

!

ipx router rip

network BB048102

network 10000001

!

ip classless

no ip http server

snmp-server community public RO

no snmp-server location

no snmp-server contact

!

line console 0

exec-timeout 0 0

password ******

login

!

line vty 0 4

password *****

login

!

end

Second router config is similiar:

!

service timestamps debug uptime

service timestamps log uptime

service password-encryption

no service tcp-small-servers

no service udp-small-servers

!

hostname BBB

!

enable password *****

!

no ip name-server

!

ip subnet-zero

no ip domain-lookup

ip routing

ipx routing 1897.909e.6a20

!

interface FastEthernet 0/0

no shutdown

description connected to EthernetLAN_1

ip address 192.168.0.250 255.255.255.0

ipx network E52974BB encapsulation novell-ether

no keepalive

!

interface Serial 0/0

no shutdown

no description

no ip address

encapsulation frame-relay

frame-relay lmi-type ansi

!

interface Serial 0/0.1 point-to-point

no shutdown

description connected to AAA

ip unnumbered FastEthernet 0/0

ipx network 10000001

frame-relay interface-dlci 101

!

router rip

version 2

network 192.168.0.0

no auto-summary

!

!

ipx router rip

network E52974BB

network 10000001

!

ip classless

no ip http server

snmp-server community public RO

no snmp-server location

no snmp-server contact

!

line console 0

exec-timeout 0 0

password *****

login

!

line vty 0 4

password *****

login

!

end

When I execute sh ipx servers I can see server BBB, like i said ping ipx BBB also is OK - 100% succes rate.

Result of sh ipx traffic is :

System Traffic for 0.0000.0000.0001 System-Name: AAA

Time since last clear: never

Rcvd: 32 total, 20 format errors, 0 checksum errors, 0 bad hop count,

8 packets pitched, 19 local destination, 0 multicast

Bcast: 12 received, 19 sent

Sent: 25 generated, 5 forwarded

0 encapsulation failed, 0 no route

SAP: 0 Total SAP requests, 0 Total SAP replies, 10 servers

0 SAP general requests received, 2 sent, 0 ignored, 0 replies

0 SAP Get Nearest Server requests, 0 replies

0 SAP Nearest Name requests, 0 replies

0 SAP General Name requests, 0 replies

7 SAP advertisements received, 4 sent, 0 Throttled

2 SAP flash updates sent, 0 SAP format errors

RIP: 0 RIP requests, 0 ignored, 0 RIP replies, 15 routes

7 RIP advertisements received, 6 sent 0 Throttled

3 RIP flash updates sent, 0 atlr sent

2 RIP general requests sent

0 RIP format errors

Echo: Rcvd 0 requests, 5 replies

Sent 5 requests, 0 replies

0 unknown: 0 no socket, 0 filtered, 0 no helper

0 SAPs throttled, freed NDB len 0

So all look I think good. Hovewer Novell client can see only local server. Local server is ver 5.0. Server which I can't login is ver 4.11

What I should to do now?

1 Accepted Solution

Accepted Solutions

clawtonga
Level 1
Level 1

On occasion I've seen the Novell client cause this issue due to the changes of IP being the default protocol (if you are using one of the later ones). Trying changing the client to have IPX as the default and see if that works.

View solution in original post

2 Replies 2

clawtonga
Level 1
Level 1

On occasion I've seen the Novell client cause this issue due to the changes of IP being the default protocol (if you are using one of the later ones). Trying changing the client to have IPX as the default and see if that works.

I'll try this tomorow but I don't think that this is a reason, becouse I can login to local server and both servers run with ipx protocol only.