If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Windows 98 can't access windows NT 4.0 Server shares
I have a Windows NT 4.0 Server (SP6) that has a client application running on
it that is accessed by terminals with windows 98 and windows 95 on them. My windows 98 terminal can see the NT server and ping it, but when I try and connect to the share it asks for a password. I enter the proper password, but it tells me invalid password. I have matched up the logins and the passwords for the account that has access on the server. I have tried logging it into the domain (which is not required for the application) and I still get the message about the share drive password. I have also tried giving the 98 terminal a static IP address and I still cannot access the share drive. I have tried a lot of things, but I am just getting fed up and need a fresh perspective on this issue. Thanks, Kirk |
#2
|
|||
|
|||
Windows 98 can't access windows NT 4.0 Server shares
"Kirk Snustad" wrote in message
... I have a Windows NT 4.0 Server (SP6) that has a client application running on it that is accessed by terminals with windows 98 and windows 95 on them. My windows 98 terminal can see the NT server and ping it, but when I try and connect to the share it asks for a password. I enter the proper password, but it tells me invalid password. I have matched up the logins and the passwords for the account that has access on the server. I have tried logging it into the domain (which is not required for the application) and I still get the message about the share drive password. I have also tried giving the 98 terminal a static IP address and I still cannot access the share drive. I have tried a lot of things, but I am just getting fed up and need a fresh perspective on this issue. Thanks, Kirk the share name is 12 characters or less ? if not ...shorten it , it sometimes causes problems : |
#3
|
|||
|
|||
Windows 98 can't access windows NT 4.0 Server shares
"Kirk Snustad" wrote in message
... I have a Windows NT 4.0 Server (SP6) that has a client application running on it that is accessed by terminals with windows 98 and windows 95 on them. My windows 98 terminal can see the NT server and ping it, but when I try and connect to the share it asks for a password. I enter the proper password, but it tells me invalid password. I have matched up the logins and the passwords for the account that has access on the server. I have tried logging it into the domain (which is not required for the application) and I still get the message about the share drive password. I have also tried giving the 98 terminal a static IP address and I still cannot access the share drive. I have tried a lot of things, but I am just getting fed up and need a fresh perspective on this issue. Thanks, Kirk the share name is 12 characters or less ? if not ...shorten it , it sometimes causes problems : |
#4
|
|||
|
|||
Windows 98 can't access windows NT 4.0 Server shares
"Haggis" wrote: "Kirk Snustad" wrote in message ... I have a Windows NT 4.0 Server (SP6) that has a client application running on it that is accessed by terminals with windows 98 and windows 95 on them. My windows 98 terminal can see the NT server and ping it, but when I try and connect to the share it asks for a password. I enter the proper password, but it tells me invalid password. I have matched up the logins and the passwords for the account that has access on the server. I have tried logging it into the domain (which is not required for the application) and I still get the message about the share drive password. I have also tried giving the 98 terminal a static IP address and I still cannot access the share drive. I have tried a lot of things, but I am just getting fed up and need a fresh perspective on this issue. Thanks, Kirk the share name is 12 characters or less ? if not ...shorten it , it sometimes causes problems : The drive share is named BOOTDRV. no problem with the length of the share name...I can ping the server from the client windows 98 machine and I can see it in Network Neighborhood by climbing the tree, but when I try and access it. It asks me for a password. I am logged in to the local machine (windows login or Network login) to an account that is created on the server with full access to the share. I enter the password and it tells me invalid password. I have recreated the login on both the server and the client machine with no change. I have a windows 95 terminal that accesses the server fine. I have tried to reproduce the same settings, but with not luck on accessing the server share from the 98 terminal. |
#5
|
|||
|
|||
Windows 98 can't access windows NT 4.0 Server shares
"Haggis" wrote: "Kirk Snustad" wrote in message ... I have a Windows NT 4.0 Server (SP6) that has a client application running on it that is accessed by terminals with windows 98 and windows 95 on them. My windows 98 terminal can see the NT server and ping it, but when I try and connect to the share it asks for a password. I enter the proper password, but it tells me invalid password. I have matched up the logins and the passwords for the account that has access on the server. I have tried logging it into the domain (which is not required for the application) and I still get the message about the share drive password. I have also tried giving the 98 terminal a static IP address and I still cannot access the share drive. I have tried a lot of things, but I am just getting fed up and need a fresh perspective on this issue. Thanks, Kirk the share name is 12 characters or less ? if not ...shorten it , it sometimes causes problems : The drive share is named BOOTDRV. no problem with the length of the share name...I can ping the server from the client windows 98 machine and I can see it in Network Neighborhood by climbing the tree, but when I try and access it. It asks me for a password. I am logged in to the local machine (windows login or Network login) to an account that is created on the server with full access to the share. I enter the password and it tells me invalid password. I have recreated the login on both the server and the client machine with no change. I have a windows 95 terminal that accesses the server fine. I have tried to reproduce the same settings, but with not luck on accessing the server share from the 98 terminal. |
#6
|
|||
|
|||
Windows 98 can't access windows NT 4.0 Server shares
"Kirk Snustad" wrote in message ... "Haggis" wrote: "Kirk Snustad" wrote in message ... I have a Windows NT 4.0 Server (SP6) that has a client application running on it that is accessed by terminals with windows 98 and windows 95 on them. My windows 98 terminal can see the NT server and ping it, but when I try and connect to the share it asks for a password. I enter the proper password, but it tells me invalid password. I have matched up the logins and the passwords for the account that has access on the server. I have tried logging it into the domain (which is not required for the application) and I still get the message about the share drive password. I have also tried giving the 98 terminal a static IP address and I still cannot access the share drive. I have tried a lot of things, but I am just getting fed up and need a fresh perspective on this issue. Thanks, Kirk the share name is 12 characters or less ? if not ...shorten it , it sometimes causes problems : The drive share is named BOOTDRV. no problem with the length of the share name...I can ping the server from the client windows 98 machine and I can see it in Network Neighborhood by climbing the tree, but when I try and access it. It asks me for a password. I am logged in to the local machine (windows login or Network login) to an account that is created on the server with full access to the share. I enter the password and it tells me invalid password. I have recreated the login on both the server and the client machine with no change. I have a windows 95 terminal that accesses the server fine. I have tried to reproduce the same settings, but with not luck on accessing the server share from the 98 terminal. sounds like it should work if the the logon/password combo is the same on server and local machine... hmmm ...I did that to myself once by accidentally having the caps lock on while typing a password when creating an account. you've checked that the account on the server is not locked out ? (of course you have : ) have you tried deleting the share , reboot , and reshare the folder (for some reason I had to do that one once also) nothing else off the top of my head ... -- Please read http://dts-l.org/goodpost.htm on how to post messages to NG's Windows support http://www.aumha.org |
#7
|
|||
|
|||
Windows 98 can't access windows NT 4.0 Server shares
"Kirk Snustad" wrote in message ... "Haggis" wrote: "Kirk Snustad" wrote in message ... I have a Windows NT 4.0 Server (SP6) that has a client application running on it that is accessed by terminals with windows 98 and windows 95 on them. My windows 98 terminal can see the NT server and ping it, but when I try and connect to the share it asks for a password. I enter the proper password, but it tells me invalid password. I have matched up the logins and the passwords for the account that has access on the server. I have tried logging it into the domain (which is not required for the application) and I still get the message about the share drive password. I have also tried giving the 98 terminal a static IP address and I still cannot access the share drive. I have tried a lot of things, but I am just getting fed up and need a fresh perspective on this issue. Thanks, Kirk the share name is 12 characters or less ? if not ...shorten it , it sometimes causes problems : The drive share is named BOOTDRV. no problem with the length of the share name...I can ping the server from the client windows 98 machine and I can see it in Network Neighborhood by climbing the tree, but when I try and access it. It asks me for a password. I am logged in to the local machine (windows login or Network login) to an account that is created on the server with full access to the share. I enter the password and it tells me invalid password. I have recreated the login on both the server and the client machine with no change. I have a windows 95 terminal that accesses the server fine. I have tried to reproduce the same settings, but with not luck on accessing the server share from the 98 terminal. sounds like it should work if the the logon/password combo is the same on server and local machine... hmmm ...I did that to myself once by accidentally having the caps lock on while typing a password when creating an account. you've checked that the account on the server is not locked out ? (of course you have : ) have you tried deleting the share , reboot , and reshare the folder (for some reason I had to do that one once also) nothing else off the top of my head ... -- Please read http://dts-l.org/goodpost.htm on how to post messages to NG's Windows support http://www.aumha.org |
#8
|
|||
|
|||
Windows 98 can't access windows NT 4.0 Server shares
"Haggis" wrote: "Kirk Snustad" wrote in message ... "Haggis" wrote: "Kirk Snustad" wrote in message ... I have a Windows NT 4.0 Server (SP6) that has a client application running on it that is accessed by terminals with windows 98 and windows 95 on them. My windows 98 terminal can see the NT server and ping it, but when I try and connect to the share it asks for a password. I enter the proper password, but it tells me invalid password. I have matched up the logins and the passwords for the account that has access on the server. I have tried logging it into the domain (which is not required for the application) and I still get the message about the share drive password. I have also tried giving the 98 terminal a static IP address and I still cannot access the share drive. I have tried a lot of things, but I am just getting fed up and need a fresh perspective on this issue. Thanks, Kirk the share name is 12 characters or less ? if not ...shorten it , it sometimes causes problems : The drive share is named BOOTDRV. no problem with the length of the share name...I can ping the server from the client windows 98 machine and I can see it in Network Neighborhood by climbing the tree, but when I try and access it. It asks me for a password. I am logged in to the local machine (windows login or Network login) to an account that is created on the server with full access to the share. I enter the password and it tells me invalid password. I have recreated the login on both the server and the client machine with no change. I have a windows 95 terminal that accesses the server fine. I have tried to reproduce the same settings, but with not luck on accessing the server share from the 98 terminal. sounds like it should work if the the logon/password combo is the same on server and local machine... hmmm ...I did that to myself once by accidentally having the caps lock on while typing a password when creating an account. you've checked that the account on the server is not locked out ? (of course you have : ) have you tried deleting the share , reboot , and reshare the folder (for some reason I had to do that one once also) nothing else off the top of my head ... -- Please read http://dts-l.org/goodpost.htm on how to post messages to NG's Windows support http://www.aumha.org I did remove the share- reboot- and reshare with no luck. I also created a new user on the server and logged in on the cient with it....still no luck. It is really agrivating me. |
#9
|
|||
|
|||
Windows 98 can't access windows NT 4.0 Server shares
"Haggis" wrote: "Kirk Snustad" wrote in message ... "Haggis" wrote: "Kirk Snustad" wrote in message ... I have a Windows NT 4.0 Server (SP6) that has a client application running on it that is accessed by terminals with windows 98 and windows 95 on them. My windows 98 terminal can see the NT server and ping it, but when I try and connect to the share it asks for a password. I enter the proper password, but it tells me invalid password. I have matched up the logins and the passwords for the account that has access on the server. I have tried logging it into the domain (which is not required for the application) and I still get the message about the share drive password. I have also tried giving the 98 terminal a static IP address and I still cannot access the share drive. I have tried a lot of things, but I am just getting fed up and need a fresh perspective on this issue. Thanks, Kirk the share name is 12 characters or less ? if not ...shorten it , it sometimes causes problems : The drive share is named BOOTDRV. no problem with the length of the share name...I can ping the server from the client windows 98 machine and I can see it in Network Neighborhood by climbing the tree, but when I try and access it. It asks me for a password. I am logged in to the local machine (windows login or Network login) to an account that is created on the server with full access to the share. I enter the password and it tells me invalid password. I have recreated the login on both the server and the client machine with no change. I have a windows 95 terminal that accesses the server fine. I have tried to reproduce the same settings, but with not luck on accessing the server share from the 98 terminal. sounds like it should work if the the logon/password combo is the same on server and local machine... hmmm ...I did that to myself once by accidentally having the caps lock on while typing a password when creating an account. you've checked that the account on the server is not locked out ? (of course you have : ) have you tried deleting the share , reboot , and reshare the folder (for some reason I had to do that one once also) nothing else off the top of my head ... -- Please read http://dts-l.org/goodpost.htm on how to post messages to NG's Windows support http://www.aumha.org I did remove the share- reboot- and reshare with no luck. I also created a new user on the server and logged in on the cient with it....still no luck. It is really agrivating me. |
#10
|
|||
|
|||
Windows 98 can't access windows NT 4.0 Server shares
"Kirk Snustad" wrote in message ... "Haggis" wrote: "Kirk Snustad" wrote in message ... "Haggis" wrote: "Kirk Snustad" wrote in message ... I have a Windows NT 4.0 Server (SP6) that has a client application running on it that is accessed by terminals with windows 98 and windows 95 on them. My windows 98 terminal can see the NT server and ping it, but when I try and connect to the share it asks for a password. I enter the proper password, but it tells me invalid password. I have matched up the logins and the passwords for the account that has access on the server. I have tried logging it into the domain (which is not required for the application) and I still get the message about the share drive password. I have also tried giving the 98 terminal a static IP address and I still cannot access the share drive. I have tried a lot of things, but I am just getting fed up and need a fresh perspective on this issue. Thanks, Kirk the share name is 12 characters or less ? if not ...shorten it , it sometimes causes problems : The drive share is named BOOTDRV. no problem with the length of the share name...I can ping the server from the client windows 98 machine and I can see it in Network Neighborhood by climbing the tree, but when I try and access it. It asks me for a password. I am logged in to the local machine (windows login or Network login) to an account that is created on the server with full access to the share. I enter the password and it tells me invalid password. I have recreated the login on both the server and the client machine with no change. I have a windows 95 terminal that accesses the server fine. I have tried to reproduce the same settings, but with not luck on accessing the server share from the 98 terminal. sounds like it should work if the the logon/password combo is the same on server and local machine... hmmm ...I did that to myself once by accidentally having the caps lock on while typing a password when creating an account. you've checked that the account on the server is not locked out ? (of course you have : ) have you tried deleting the share , reboot , and reshare the folder (for some reason I had to do that one once also) nothing else off the top of my head ... -- Please read http://dts-l.org/goodpost.htm on how to post messages to NG's Windows support http://www.aumha.org I did remove the share- reboot- and reshare with no luck. I also created a new user on the server and logged in on the cient with it....still no luck. It is really agrivating me. doesn't it though! when everything looks ok but doesn't work ...welcome to microsoft : just a thought ...delete the .pwl file from the win98 box , and receate the user (possible corrupt pwl file ...hash not matching ?) |
|
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
windows 98 SEC join Windows 2003 domain | xiaomei | Networking | 0 | October 29th 05 06:14 PM |
windows 98 user can not access the shared folder on windows 2003 s | xiaomei | Networking | 0 | September 28th 05 03:37 AM |
I can't connect to my shared printer on my Windows 98 SE machine | Martin Healy | Printing | 2 | July 7th 05 07:55 PM |
Smart Portable Shortcuts | ForestSpirit | General | 5 | February 28th 05 03:50 AM |
FAQ: Win98 users: Upgrading to WinXP, IE6, etc. | JM | Setup & Installation | 6 | July 26th 04 01:44 PM |