What am I missing.

[cb49747]

I had a network set up with a half dozen windows xp pro computers, and redhat 7.2 linux server with samba configured as wins and domain server.

everything was working fine.

I then installed a direcway router for my internet access. I can not configure anything on this router and the ip address is set to 192.168.0.1 and since my network used 192.168.1.xxx I had to go ahead and reset the ip address on my network. The router also has dhcp running automaticaly so I'm using that with the exception of the server which is set to 192.168.0.2.

After the changes were made, I have been unable to access other computers from the network.

It seems to log in allright, but then cannot find the profile. when I ping 192.168.0.2 it works I get I get on the internet ok, but can not seen to access the shared directories. When I ping server the netbios name for 192.168.0.2 it says it get no reply from 192.168.1.1 the old address for server. All host and lmhost files are empty as I do not use them (wins)

Help, what am I missing. Why is the netbios name not updating to the new ip address?

Chris Burger

 

[lullysing]

First of all, why use a router that you can't even modify anything on it?

Even my ADSL modem has some kind of web interface for changing the ip adress and also setting up the modem as a ghetto router with nat.



_____________________________
when someone asks for your username and password, and much *clickely clickely* is happening in the background, know enough that you should be worried.

 

[cb49747]

I agree with you, but direcway is the only way I can get high speed internet. no cable and dsl where I live. So I'm limited. The router I'm using is part of the direcway system. So I'm saying I have no choice here. There is a web interface to it, however no options for changing the features such as ip address.

 

[thedaver]

There is NOTHING preventing you from using static IP assignments in the 192.168.0. space that are not part of the DHCP pool.

The NetBIOS problems may arise from port blocking by that router. Have you contacted Direcway to ensure that their router is designed to support a local network instead of a local machine?

You could also fiddle with adding another NIC to a linux box or windows box and put the network behind that device in a form of IP forwarding or connection sharing. Not tremendously elegant, but since some providers require you to pay a premium for multiple PCs behind their connections, you may find that there are some artificial restrictions in their black box router.

Hosting Solutions for Home or Business.

http://www.surfinbox.com/hosting/

 

[fdalmoro]

If the network mask is set to 255.255.0.0 you should be able to use the 192.168.1.xxx addresses without any problems. Obviously it's not an answer to your problem but it is a solution.

Also, you can try running ipconfig /flushdns on the win boxes to see if that clears the problem.


Fernando

 

[CyberFan]

Check to make sure that the Directway device is really a router. It may be nothing more than special purpose switch (like a cable modem) that will communicate with only one device on the "private" side. If so, you'll need to install your own router behind the Direcway device.


Kent

 

[cb49747]

Ok,

Here is what I have found.

My wins.dat file is still listing server as 192.168.1.1 when it should be 192.168.0.2

Do not know much about this. Is there a way to empty this file. Can I just delete it?

Appreciate any help.

Chris

 

[cb49747]

I renamed the file and rebooted the server and it created a new win.dat file that exact same as the old one. How do I flush the wins information?

 

[CyberFan]

The 192.168.1.1 address sounds like the Windows default address that it uses when it can't obtain a real one. This suggests that DHCP is not running on your local network.

Kent

 

[fdalmoro]

The default IP is 168.xxx.xxx.xxx not 192.168.xxx.xxx.

Fernando

 

[fdalmoro]

sorry it's not 168 or 192.168 .... it's 169.254.x.x

Fernando

 

[cb49747]

Thanks everyone for your help. I deleted the win.dat file shut down the server and shut down the router. Restarted the router then restarted the server. It created a new wins.dat with the correct information. All is good. DO not know to much about wins, but untill I zeroed out the router it seemed to have been sending bad information to wins.

Chris

 

[thedaver]

Not surprising, WINS is evil anyhow, IMHO. Glad you're fixed up now.

Hosting Solutions for Home or Business.

http://www.surfinbox.com/hosting/