Workstation Crashed and now can not login to Server

[rowin]

The workstation is a Sony Vaio connected to the Novell 3.12 server using the MS networking not Novell's. THe connection is via a D-Link PC Card.

I attempted to install a USB modem today. It did not work but crashed the Sony. Now I can not log into the server through IPX although it is being seen via TCP/IP. No Login scripts are being loaded on the workstation.

I have tried removing the Netware client and the IPX protocol and reinstalling them. I still cannot login into the server. What should I do next?

Robin

 

[JockMullin]

Hi, Robin

I'm not sure I understand the configuration. You mean you have TCP/IP support on the 3.12 server? That is unusual, but I guess it is possible.

When you say you see it via tcp/ip, do you mean you see the server in Network Neighborhood? What version of Windows are you running?

IF you open the server in NN can you see the volumes? If you try to open them does it ask for a login?

- Have you made client for Novell networks the primary network client?
- I trust you are not trying to log into a tree but using a bindery connection.
- If so, have you set the preferred server?
- Have you predefined the speed (10/100) of the link? Sometimes auto-negotiation takes so long the login gets bypassed.
- Have you set the ethernet frame type to agree with the server (probably 802.3) or left it at auto. If you have predefined the frame type and it is not the same as the server then it won't see the server under IPX/NETX. Of course the server may be set up to handle both.

If you have access to the monitor on the server console it may be helpful - you may see the connection happening but no authentication happening. At least then you would know there is communication happening but something else is preventing the login from happening.

Unfortunately I rarely use the MS client, so I'm not sure about configuring it.

So many questions, so few answers ...

Jock

 

[rowin]

Thanks for your reply
* My comments
Hi, Robin

I'm not sure I understand the configuration. You mean you have TCP/IP support on the 3.12 server? That is unusual, but I guess it is possible.

* I have tcp/ip for other reasons on the network. TCP/IP is not being used as the login protocol

When you say you see it via tcp/ip, do you mean you see the server in Network Neighborhood? What version of Windows are you running?
* yes. Windows 2000 prof

IF you open the server in NN can you see the volumes?

If you try to open them does it ask for a login?

* No unable to log in to server though can access it via tcp/ip

- Have you made client for Novell networks the primary network client?
- I trust you are not trying to log into a tree but using a bindery connection.
- If so, have you set the preferred server?
- Have you predefined the speed (10/100) of the link? Sometimes auto-negotiation takes so long the login gets bypassed.
- Have you set the ethernet frame type to agree with the server (probably 802.3) or left it at auto. If you have predefined the frame type and it is not the same as the server then it won't see the server under IPX/NETX. Of course the server may be set up to handle both.

If you have access to the monitor on the server console it may be helpful - you may see the connection happening but no authentication happening. At least then you would know there is communication happening but something else is preventing the login from happening.

Unfortunately I rarely use the MS client, so I'm not sure about configuring it.
* Following this comment I have downloaded the Novell Client. I think the right one is the latest v4.83 SP2 for Win 2000. I assume this will work connecting to a 3.12 server.

So many questions, so few answers ...

* In essence the crash on the server has damaged the Win2000 netware drivers. I hope that using the Novell client will circumvent the effect of the crash.

Robin

 

[JockMullin]

Hi, Robin.

Yes, that is the correct Novell client.

I would recommend trying it, if the server is accessible that will likely solve the problem..

Jock