- Mar 25, 2002
- 81
- 0
- 0
Here's are my problems.....
1. Whenever I would copy\share file\s across my LAN [\\server\share], I would get this error:
-- "The [filename] cannot be copied. The specified network name is no longer available". --
2. Network is slow. [i.e. copying a 1 MB file takes a long time]
3. Internet Browsing is slow as well. The cable modem would restart every now and then.
This is the WAN\LAN setup.
I have a server [running 2000 AS, WINS, ICS [cable & lan config], no AD, just a member server]. The other machines are running XP and 2000 and are connected to an 8 port switch along with the LAN connection from the server.
All my machines are fairly new with new hardware [i.e. PIII, avg. 256-512 MB, 10/100 NICs] so the hardware on the nodes aren't the problem. I have an RCA cable modem and a Linksys 8 port switch.
I used to have a sonicwall soho 50+ that I had to lend out which worked well with my Cable \ Lan. I ran a full AD \ DC network and never had the problems I am describing.
Since then, I have decided to use ICS on my server to make Internet connection sharing much simpler and cheaper than buying another cable router. After making that decision and configuring my LAN, I've been having these problems for about a good 3 weeks now. here are the things that I have done to resolve the matter. [in order]
1. Check all connections [power and data].
2. Checked NICS.
3. Reinstalled drivers for hardware and networking protocls
4. Made sure DHCP & DNS was not installed on the server machine along with ICS.
At this point, I have performed a clean reinstall of server\AS and my other machine with 2000 to make sure I start from scratch and not make any mistakes. I can get lease address from the ICS server and browse but the connections are slow and whenever I would copy a file, it would give me the error message as stated above.
I went on the MS site for the same exact error message, but found an article which pertained mostly to a machine joining a domain. I know this is a networking issue and may have something to do with name resolution failures.
I need some help with one.
1. Whenever I would copy\share file\s across my LAN [\\server\share], I would get this error:
-- "The [filename] cannot be copied. The specified network name is no longer available". --
2. Network is slow. [i.e. copying a 1 MB file takes a long time]
3. Internet Browsing is slow as well. The cable modem would restart every now and then.
This is the WAN\LAN setup.
I have a server [running 2000 AS, WINS, ICS [cable & lan config], no AD, just a member server]. The other machines are running XP and 2000 and are connected to an 8 port switch along with the LAN connection from the server.
All my machines are fairly new with new hardware [i.e. PIII, avg. 256-512 MB, 10/100 NICs] so the hardware on the nodes aren't the problem. I have an RCA cable modem and a Linksys 8 port switch.
I used to have a sonicwall soho 50+ that I had to lend out which worked well with my Cable \ Lan. I ran a full AD \ DC network and never had the problems I am describing.
Since then, I have decided to use ICS on my server to make Internet connection sharing much simpler and cheaper than buying another cable router. After making that decision and configuring my LAN, I've been having these problems for about a good 3 weeks now. here are the things that I have done to resolve the matter. [in order]
1. Check all connections [power and data].
2. Checked NICS.
3. Reinstalled drivers for hardware and networking protocls
4. Made sure DHCP & DNS was not installed on the server machine along with ICS.
At this point, I have performed a clean reinstall of server\AS and my other machine with 2000 to make sure I start from scratch and not make any mistakes. I can get lease address from the ICS server and browse but the connections are slow and whenever I would copy a file, it would give me the error message as stated above.
I went on the MS site for the same exact error message, but found an article which pertained mostly to a machine joining a domain. I know this is a networking issue and may have something to do with name resolution failures.
I need some help with one.