Here is my scenario: I have just had a cable modem installed and it is attached to a Win 98 machine. Prior to the installation, this machine was a client on a Win2K Server network. Now that the cable modem is taking up the NIC card's connection and requires specific TCP/IP settings, I was wondering if it is possible to install a 2nd NIC card that also is bound to TCP/IP, but with different settings (in particular, a distinct DNS Configuration setting). I have attempted to install the 2nd card and set distinct settings for the TCP/IP protocol bound to the 2nd card, but whatever changes I make to the 2nd card also change the settings on the 1st card. Am I doing something wrong, or is TCP/IP limited to supporting one NIC card on a 98 machine?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Two NIC's/Two Separate TCP/IP config's on Win98?
- Thread starter FVTrainer
- Start date
- Thread starter
- #3
Well, I already have a hub. And I probably didn't give enough information:
1. My Win2K server is using TCP/IP as the protocol for the network. I have the client machines (except the one attached to cable modem which is now outside of the network) set to obtain an IP Address Automatically and DNS is enabled--the Win2K Server is running the DNS Service (so now, I would suspect, since the pc that is attached to the cable modem has DNS disabled, it will not be able to obtain an IP address for the internal Win2K network).
2. The Win2K server is running an intranet. I'd like the machine attached to the cable modem to be able to access the intranet, which I believe requires TCP/IP connectivity. But it appears to me that the TCP/IP settings affect all adapters on one machine and that the cable modem pc is (I think) configured in a manner that won't allow it to talk via TCP/IP to the Win2K server. Thus, I don't think I can attach to the intranet even if I reconfigured my Win2K server to use a different protocol(?).
Also, I've been doing some reading at various sites since I created this post and it appears that just using a hub would expose my entire network to the internet. Which doesn't sound like a great idea. My impression, based on what I've read so far, is that I should use a router (or a software solution) to provide firewall protection and make sure that features such as Microsoft file and print sharing are not bound to TCP/IP.
Please feel free to correct any erroneous statements I've made in the above reply, as this subject is definitely not in my field of expertise.
1. My Win2K server is using TCP/IP as the protocol for the network. I have the client machines (except the one attached to cable modem which is now outside of the network) set to obtain an IP Address Automatically and DNS is enabled--the Win2K Server is running the DNS Service (so now, I would suspect, since the pc that is attached to the cable modem has DNS disabled, it will not be able to obtain an IP address for the internal Win2K network).
2. The Win2K server is running an intranet. I'd like the machine attached to the cable modem to be able to access the intranet, which I believe requires TCP/IP connectivity. But it appears to me that the TCP/IP settings affect all adapters on one machine and that the cable modem pc is (I think) configured in a manner that won't allow it to talk via TCP/IP to the Win2K server. Thus, I don't think I can attach to the intranet even if I reconfigured my Win2K server to use a different protocol(?).
Also, I've been doing some reading at various sites since I created this post and it appears that just using a hub would expose my entire network to the internet. Which doesn't sound like a great idea. My impression, based on what I've read so far, is that I should use a router (or a software solution) to provide firewall protection and make sure that features such as Microsoft file and print sharing are not bound to TCP/IP.
Please feel free to correct any erroneous statements I've made in the above reply, as this subject is definitely not in my field of expertise.
I know that you can definitely use software, I have done it at my office, 1 nic is for the modem and 1 nic for the internal network, each having totally different settings. Proxy software handles the traffic and firewall between. A hardware router is another possibility, it all depends on where you want to spend money, what you are allowed to do on your network, etc, and what you have the ability to setup.
My only caveats with using software like I did, are:
a) The 2 different ISP's (cable then DSL) I used in my area really got 'defensive' about giving any tech support once they knew I had the software, and pretty much blamed all problems with connectivity on it.
b) The software can be really expensive depending on how many users are allowed simultaneously.
c) Its just one more thing on your to-do list keeping the software current and running right.
Many people I know have gone hardware, and seem to like it, especially now that you can get multiport hub/switches with built in firewall (or NAT) that are pretty simple to set up and are designed for xDSL and Cable users. You just have to find out if they support the protocol your ISP is using. I would likely go hardware myself in hindsight, but it wasn't available for the price when I bought the software, since the s/w ran on a PC I already had.
I'm no network expert either, but this is what I've found from hands on use.
BTW - you bet you can expose your network by using a hub and the modem in the Uplink port. Especially with the infrastructure Cable uses, groups of users being 'hubbed' in the first place. Whoever runs the W2K server would likely go ape if they saw a hub setup like that.
You may be restricted to software, since a h/w box will likely want to do DNS also, so you would have problems with server's DNS. Check the various Proxy software sites and see if they will take DNS on the "internal" side I'm sure they will.
Hope I was helpful
Ray
My only caveats with using software like I did, are:
a) The 2 different ISP's (cable then DSL) I used in my area really got 'defensive' about giving any tech support once they knew I had the software, and pretty much blamed all problems with connectivity on it.
b) The software can be really expensive depending on how many users are allowed simultaneously.
c) Its just one more thing on your to-do list keeping the software current and running right.
Many people I know have gone hardware, and seem to like it, especially now that you can get multiport hub/switches with built in firewall (or NAT) that are pretty simple to set up and are designed for xDSL and Cable users. You just have to find out if they support the protocol your ISP is using. I would likely go hardware myself in hindsight, but it wasn't available for the price when I bought the software, since the s/w ran on a PC I already had.
I'm no network expert either, but this is what I've found from hands on use.
BTW - you bet you can expose your network by using a hub and the modem in the Uplink port. Especially with the infrastructure Cable uses, groups of users being 'hubbed' in the first place. Whoever runs the W2K server would likely go ape if they saw a hub setup like that.
You may be restricted to software, since a h/w box will likely want to do DNS also, so you would have problems with server's DNS. Check the various Proxy software sites and see if they will take DNS on the "internal" side I'm sure they will.
Hope I was helpful
Ray
Re: 'My impression, based on what I've read so far, is that I should use a router (or a software solution) to provide firewall protection ...' After a trojan recent problem, I downloaded a free consumer version of zonealarm - works great, easy to setup and use - it's at - and I've had no problems since.
Have you considered connecting the cable modem to W2K and turning on Internet Connection Sharing to the other computers.
Then, download ZoneAlarm at ZoneAlarm is a free firewall thats easy to configure and effective for protecting you network.
If you do this, all computers on the network can have safe access to the internet and the intranet.
Hope this helps.
Then, download ZoneAlarm at ZoneAlarm is a free firewall thats easy to configure and effective for protecting you network.
If you do this, all computers on the network can have safe access to the internet and the intranet.
Hope this helps.
- Thread starter
- #7
Thanks, all, for your input. Your comments and suggestions have been very helpful.
The Internet Connection Sharing option in Win2K would indeed be the most cost effective way for me to go, and with the firewall software, sounds like it would work well. But I think I'm going to take the hardware router option. Using Win2K as the internet connection for my network has one drawback...that means the Win2K server has to be up anytime I want to be on the net. While that would be true in a normal office environment, my network runs at home in my office. It exists as a development platform and the server exists primarily to allow me to model sql server and web development environments for client projects. There are many times when I need to have the server up and have access to the net, but not 24x7. Keeping the server running just so I can have net access is less than desirable. (Besides, the server sits in my office and it sounds like a jet turbine even in 'quiet' mode, which kind of ruins the accoustics in my office when its running! And I need to do my part to help my fellow Californians deal with our impending electricity crisis.)
Thanks again!
The Internet Connection Sharing option in Win2K would indeed be the most cost effective way for me to go, and with the firewall software, sounds like it would work well. But I think I'm going to take the hardware router option. Using Win2K as the internet connection for my network has one drawback...that means the Win2K server has to be up anytime I want to be on the net. While that would be true in a normal office environment, my network runs at home in my office. It exists as a development platform and the server exists primarily to allow me to model sql server and web development environments for client projects. There are many times when I need to have the server up and have access to the net, but not 24x7. Keeping the server running just so I can have net access is less than desirable. (Besides, the server sits in my office and it sounds like a jet turbine even in 'quiet' mode, which kind of ruins the accoustics in my office when its running! And I need to do my part to help my fellow Californians deal with our impending electricity crisis.)
Thanks again!
Guest_imported
New member
- Jan 1, 1970
- 0
I did this same thing.I have a NIC card that I use to network to my wife's desktop. I also have a wireless nic card that I use to network my laptop.Each card has a different IP address and dns.Go to network neighbor hood properties and select the tcp/ip protocol pertaining to your adapter then enter what you want.For example on my machine the wirless card is set to 10.0.0.1 and I connect to the net with this machine and run a proxy(analog x proxy) to surf using my laptop.this proxy software just happpen to pick the wireless card.(this can also be changed you can remove one NIC and install proxy then add the other NIC)
But PCanywhere can use all IP's from all NIC cards.
Does any of this make sense?let me know if you want more details.Hope I helped.salakazam@hotmail.com
But PCanywhere can use all IP's from all NIC cards.
Does any of this make sense?let me know if you want more details.Hope I helped.salakazam@hotmail.com
I experienced a problem installing 2 NICs in the same Win98SE computer when I first got my cable modem. I called the cable company's tech support and they bumped me up several levels until I finally talked to a tech who said that this is not supported in Win98SE as it would eventually cause "Stack Bleed". If you want the best solution, I would invest in a hardware router. I just went through this after having my cable modem set up (three PCs) that worked flawlessly for 6 months start to have problems allowing the third PC to attach. Eventually replaced my simple hub with a LinkSys 4 Port Cable/DSL Router and once the configuration was finished everything is now working again.
- Status
Similar threads
- Locked
- Question