ForumsHQ

currently i am using dsl, which is lanned from this computer to the other one that was having the problems

Originally posted by syntax53

-when you "connect it to your network," how is it supposed to get out to the internet? do you have a router setup? are you using internet connection sharing?



this computer dials out to the net, i do not have a router, just trying things out, I am not using internet sharing, don't want the other machine on the net.



Originally posted by syntax53

--how are the machines on the "network" getting their IP addresses? do you have something for a dhcp server? are you assigning them all manually?



window's is auto assigning ip adresses

Originally posted by Kain





this computer dials out to the net, i do not have a router, just trying things out, I am not using internet sharing, don't want the other machine on the net.



window's is auto assigning ip adresses



sounds to me like you dont have an ip address. windows doesn't "auto-assign" ip addresses. it will default to some wack like 68.x.x.x or 164.x.x.x numbers if it cant pull one, but 99/100 that wont do shit for you. if you want network computers to be able to talk to each other you'll have to manually assign addresses (unless you use a different protcol like IPX or NetBeui). you probably have netbeui or something similar installed already and thats why they can communicate with each other (just not via tcp/ip).



example tcp/ip config:



--PC1

IP: 192.168.1.10

SubNet: 255.255.255.0

Gateway: 192.168.1.1



--PC2

IP: 192.168.1.11

SubNet: 255.255.255.0

Gateway: 192.168.1.1



--PC3

IP: 192.168.1.12

SubNet: 255.255.255.0

Gateway: 192.168.1.1



etc



what is probably happening is when you connect to your network windows sees a link on the network card and that is taking priority over your dial-up. it is trying to get to the net through the network card and not the dialup.



in windows 2k/xp you can set the priority under network connections. open network connections and then goto "Advanced" --> "Advanced Settings." You can move up and down the adapters and protocols to set priority.



-syn

problem fixed, thanks to pantera....thanks for all the help guys

Originally posted by Kain

problem fixed, thanks to pantera....thanks for all the help guys



you should post what the solution was so people who search in the future with a similar problem will see the solution. plus i'm curious.

i had him use dhcp for his second computer instead of a static assigned ip.. it must be some crazy DUN limitation..

Originally posted by Panterra X

i had him use dhcp for his second computer instead of a static assigned ip.. it must be some crazy DUN limitation..



it's not really a limitation, it's how it works. you can't assign a static ip to a DUN. when you connect your IP is assigned to you. unless the ISP reserved an address for you and told you what it was you wouldn't be able to talk to their network. when i was talking about about the static IPs on the computer i was talking about the network card's tcp/ip config.

Originally posted by syntax53

when i was talking about about the static IPs on the computer i was talking about the network card's tcp/ip config.



thats what im talking about too.. we didnt mess with the dial up properties, just his NIC properties... set the main machine to 192.168.0.1 255.255.255.0, and second to obtain from dhcp... now he can be dialed in and networked to share files etc at the same time...



i just dont know why it would make a difference that the other lan machine was using a static ip.. cause it didnt work with static, only dhcp...

nod panterra, i'm honestly not sure what we did, but it works just fine now. it appears that dhcp was the problem

Ummmm is Kain running a board with Galahad? Get out while you can, Kain. You'd have better luck prying my dats away from me and running my board as your own than hooking up with him. (fyi the comptuter I am using now while working on mine sucks ass so if I took this in the wrong way, I am so sorry)