Tom's Guide | Tom's Hardware | Tom's Games
 |
 |
 |
I want to connect a win98 pc to a NT 4 server domain and can't get any (!) network connections. The win98 pc is a notebook with PCMCIA-network-card. It was running until I reinstalled the operating system...
I've tried tcp/ip, ipx and NetBEUI (all three are running on the server) but no connections. I use a fixed IP for both client and server and the same subnet mask. win95 clients connect without any difficulties to the server.please help, I really need the connection to the server!
Forget trying to work with IPX(Novell) and NetBeui. In TCP\IP you said you have the same IP address; I assume it is not the exact same address as the server IP.
The real consideration is the NetBios name of the laptop, after the OS reinstall. Whatever the name of the client is now, I would remove it from the Server Manager, then join the workgroup on the laptop, reboot, then join the Domain again and enter the Admin data of the Domain on the laptop to join the domain again, this should work. Whenever you modify the Security ID of the client, you must update that info in the Server Manager. By removing it and rejoining it, it saves a lot of work. Let me know how it goes-
0 
thany for the fast answer...
you're right, server and client have different IP's, of course.
The 'trick' with the server manager and reboot did not work. I wonder if there is any traffic coming out of the network adaptor. The traffic led seems to be 'on' all the time. Win reports no problems with the adaptor, but i can't get any connections.The win95 clients we are running here use (static) IP's that are totally different from the server's IP (even different subnet mask) and it works. Bevore reinstallin the OS I could get acces to the server _or_ to our router, not both at a time (depending on IP address!). Are there any rules for IP-addresses of win98 clients to enable this connection? Currently the server uses 172.16.1.1 and win98 uses 172.16.1.2 - the router would like to have 192.168.0.x ...
0
So the Default Gateway on the laptop is set to ? 172... or 192...?
The use of NetBeui can give conflicting responses, so I would remove it. It may give the appearence of a link, but then TCP/IP may not. It is best to use only one or the other based on your subnet.
By definition, NT should not work when a client on the same subnet is set to another gateway and subnet mask (in TCP\IP) but having netbuei will let it connect, making it hard to diagnose...
Also, try to ping these two from each other, by IP address and tell me what you see?
0
I've tried 172.. and 192.. as gateway, currently using 172.. because this seems the right one for me (win95 clients use 192.. only..).
I've removed everything but tcp/ip and still get a lot 'pseudo' traffic.
Ping-ing from win95 (subnet of router) to server (172..) gives 'requested time out', to router (192..) gives 'reply.... ' (but logon on NT works).
ping from win98 to server / router using both subnets and corresponding gateways returns 'requested time out'
0
Since you get success to the router it seems you are on the subnet and gateway needed for the router, leave the IP the same and change the subnet and gateway for the server and try again... (lots of reboots) back in an hour-
0
the succesfull connection was from a win95 client, not the 98...
I just managed to phone our hardware company, they say it could be some sort of hardware defect because of the traffic led that is really in a hurry. they will send someone to check this...
so, no more reboots totday, 150 reboots a day or so is more than enough...
thanx for your help, I might be back with my problem tomorrow morning (cet) again...
0
A quick lesson on IP might work here.
For the clients that are on the same network (cable) they have to have valid addresses for that network. So if you are using 172.16.1.1 for the server and 172.16.1.2 for a 9x client, that's fine. You don't say what the subnet mask is but that can be the key to the whole problem.. It is very important what the mask is set to. For that address, the default mask would be 255.255.0.0 but could be set to anything. If the default mask is used, then the network ID is 172.16. All clients on that network, or subnet, must have that mask and network ID. So make a 98 machine 172.16.1.3 with a mask of 255.255.0.0 and assuming that is the mask you are using and the .3 address is not already used, you should be fine. A client with the 192.x.x.x on that subnet will not work because it is by definition on a different network - different network ID.
As far as the router goes, it will have more than one IP address. It will have an IP address for each network it is attached to. Your default gateway would have to point to the address that is local to you. So sticking with the 172.16.x.x address, your default gateway would also have to be set to 172.16.?.? (whatever the actual address of the router is).
If you need to connect to a computer on a different subnet, 192.x.x.x then IP would send those packets to the router since it is a diffent subnet. The router is known because that is the default gateway. When IP sees that 192.x.x.x is on a diffent network than your 172.6.x.x, it will send those packets to the default gateway which will then 'route' them to the appropriate network. That is the job of the router.
Hope this helps.
0
Good job Glen!
One additional comment: 192.168.0.xx is the required network for win98 ICS (Internet Connection Sharing); I only bring it up since you said that is what the router 'wants' to use. ICS actually sets up a mini DHCP service that assigns 192.168.0.x addresses to the rest of your clients when they come online.
(The Server Manager solution didn't work because Win98 computers don't JOIN the domain.)
0
Thanks Liz. Good point about the ICS. I should have mentioned that but I was on a roll with the IP basics. :)
Most people don't understan the concept of 98 machines not 'joining' the domain. Technically they do not join the domain but simply have permission to use some of the resources. A distinction most users don't realize.
Do you work with W2k at all Liz?
0
Thanx for all the info!
I'm wondering why our win95 clients connect to the server / domain _and_ router without any difficulties...
You're right, the subnet of the server is 255.255.0.0, the one of the router in 255.255.255.0 . Win95 is set to the router's subnet / IP / Gateway / DNS and is able to access the NT-domain!!! It was set to the servers addresses before we got the router. Just changing the addresses to the one's the router wants worked with 95 not with 98...
0
You need to get your terms straight to get this worked out. The 'subnet' is the network ID of the IP address. It sounds like you have to subnets here. Let's call them the 172 and the 192 subnets. The mask is the 255.255.0.0 number. The mask should be the same for all clients on the same subnet. A few questions here:
1. What is the IP address(s) and mask of the router?
2. What are the IP addresses and masks of the client machines?Dont worry about DNS at this point until you get the IP stuff straight.
0
OK, I see where I was wrong on the Server Manager... (forgetting there is no security ID in Win9x) :(
Why don't you give us the IP, subnet mask, and Gateway of the working Win 95 client, and the same for the laptop you are working with, or at least list the differences between these machines.
0
The Win95 clients may be connecting to the server through a different protocol - if you can't ping the server from them, TCP/IP isn't configured properly (which can be difficult and why most people have a DHCP server).
I'd look at ip address, subnet mask, and gateway for both clients, both ports of the router (it has to have 2), AND the server.
I work with W2K a little - I'm just now starting to dig into the training kit that's been on my desk for 4 months.
0
Just curious Liz. I have used it since beta 2 and taught the MCSE classes for Win2k. If you like NT, you will fall in love with Win2k.
0  |
 |
 |
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |
